You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That is the mechanism and syntax for upgrading to h2 within an HTTP/1.1 connection, so I see no reason to change it. Whether it is h2 or h2c depends on TLS being underneath (and a twisted view of history). This is the kind of thing one might do over a local socket or localhost connection.
Personally, since you guys don't seem to understand that it is both a real world example and the correct token to use (in HTTP/1.1), I think it is useful as is. But if it really makes the h2 bubble happier, go ahead and change it to websocket. It is just an example.
Activity
MikeBishop commentedon Jun 29, 2018
Make it
h2c. 😉royfielding commentedon Jun 30, 2018
That is the mechanism and syntax for upgrading to h2 within an HTTP/1.1 connection, so I see no reason to change it. Whether it is h2 or h2c depends on TLS being underneath (and a twisted view of history). This is the kind of thing one might do over a local socket or localhost connection.
MikeBishop commentedon Jun 30, 2018
But the example as it stands is invalid (that isn't the token for HTTP/2), and 7540 doesn't define using Upgrade to reach
h2, onlyh2c.mnot commentedon Jul 1, 2018
Yes, this should be changed; it will confuse some.
Suggest
websocketsince that's actually in use.mcmanus commentedon Jul 1, 2018
royfielding commentedon Jul 2, 2018
Personally, since you guys don't seem to understand that it is both a real world example and the correct token to use (in HTTP/1.1), I think it is useful as is. But if it really makes the h2 bubble happier, go ahead and change it to websocket. It is just an example.
Use 'websocket' instead of 'HTTP/2.0' in examples