2015-09-25 9:29 GMT+02:00 Mark Thomas <ma...@apache.org>: > I'm not so sure. HTTP/2 explicitly doesn't support HTTP upgrade. The > HTTP/2 spec expects protocols like WebSocket to use ALPN. Despite this, > there has been work to try and layer WebSocket on top of HTTP/2. > > At this point in time proxying WebSocket is tricky. httpd's WebSocket > proxy support makes assumptions that aren't always valid. > > General support for proxying HTTP upgrade would be a good thing and > right now AJP looks like the simplest way for us to make this happen. > > Most likely a HTTP/2 proxy will still be a legacy HTTP/1.1 proxy as well. The main problem with the AJP.next plan is that by the time you release something many will be using HTTP/2. HTTP/2 is more important than the rest moving forward, and encapsulating in AJP it would likely be inefficient (basically, zillions of messages).
OTOH, reversing the problem, AJP.next can be a HTTP/2 transport where you specify encapsulation of HTTP/1.1 and its upgrade. That could be more transparent and make configuration much cooler: unless the Tomcat connector gets some encapsulated requests, it could still act as a normal HTTP/2 connector. Rémy
