Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebSockets #386

Closed
mnot opened this issue Feb 15, 2014 · 11 comments
Closed

WebSockets #386

mnot opened this issue Feb 15, 2014 · 11 comments

Comments

@mnot
Copy link
Member

mnot commented Feb 15, 2014

This issue is a placeholder / tracking issue for anything related to WebSockets support in HTTP/2.

@mnot
Copy link
Member Author

mnot commented Feb 15, 2014

Note that our charter says we need to "will coordinate this item with...[t]he HYBI Working Group, regarding the possible future extension of HTTP/2.0 to carry WebSockets semantics."

@mnot
Copy link
Member Author

mnot commented Mar 1, 2014

@mnot
Copy link
Member Author

mnot commented Mar 1, 2014

@mnot
Copy link
Member Author

mnot commented Jun 5, 2014

Discussed in NYC; we believe this could be done with extensibility (e.g,. with a new ALPN token, maybe new frame types + settings) - but we're not going to explicitly design it.

@mnot mnot closed this as completed Jun 5, 2014
@thedrow
Copy link

thedrow commented Jun 5, 2014

Why not? WebSockets are here to stay. If it won't be designed later implementations with HTTP 2.0 will be a mess (think JavaScript in the 90s).

@martinthomson
Copy link
Collaborator

@thedrow we haven't decided not to do websockets, we've only decided not to block HTTP/2 until a design for websockets over HTTP/2 is done.

@lenovouser
Copy link

Are there any updates on this? It has been a whole year now since someone commented on this, are WebSockets still going to be implemented in HTTP/2?

Also see caddyserver/caddy#189

@MartinKei
Copy link

What's the status on this one?

@martinthomson
Copy link
Collaborator

Awaiting someone to do some work: implement it, convince others to implement it, etc...

@AlanQuatermain
Copy link

I'm looking into this for the HTTP/2 upgrade across our systems at LinkedIn. I'm given to understand that the lack of WebSockets makes this upgrade more arduous for us (i.e. minimal benefit unless we roll out these changes across a very wide number of micro services across a large number of colocation locations, etc.) I've found Yutaka Hirano's draft spec at the IETF and it looks like I can take that & run with it fairly simply.

My question here is: who else is interested in this? Has there been any other work in this direction since Hirano's last draft nearly three years ago?

@bagder
Copy link

bagder commented Nov 13, 2017

@AlanQuatermain: there's now a new draft being discussed and worked on in the HTTPbis WG: https://datatracker.ietf.org/doc/draft-mcmanus-httpbis-h2-websockets/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants