Opened 3 years ago
Last modified 3 months ago
#1992 new enhancement
Websocket over HTTP/2 support
|Reported by:||Owned by:|
Will NGINX ever support Websocket over HTTP/2?
Change History (2)
comment:1 by , 3 years ago
comment:2 by , 3 months ago
Now that HTTP/3 usage is exceeding HTTP/1.1 usage it looks like there is practical demand. Look at YARP:
NGINX and Apache web servers making HTTP/2 the default would practically eliminate the remaining HTTP/1.1 usage on the Internet and with it all corresponding compatibility issues.
Note: See TracTickets for help on using tickets.
First of all, two basic things to understand:
Support for Websockets over HTTP/2 basically means that nginx will have to translate these CONNECT requests to HTTP/1.1 Upgrade requests somehow when proxying. While this might work, this doesn't look like a good solution.
Alternatively, we may consider passing such CONNECT requests as is to HTTP/2 backends (for example, when using
grpc_pass), but this approach also have problems. In particular, this doesn't look compatible with HTTP/1.1 backends, which makes it hardly useful.
Overall, this is unlikely to happen unless there is a practical demand. For now it looks like there is no such demand.
For there record, it RFC 8441 currently seems to work somehow in Firefox (https://bugzilla.mozilla.org/show_bug.cgi?id=1434137) and under a flag in Chrome (https://www.chromestatus.com/feature/6251293127475200).