On 04/10/2024 20:32, Anurag Sharma wrote:
HI Mark And Christopher,
Apologies for the late response,
Tomcat act as a reverse proxy to 3rd party legacy system. We have recently
upgraded Tomcat to use HTTP/2 protocol; this causes the legacy system not to
render and get an error message when rendering. Tomcat application war acts as
a reverse proxy (which means all requests hit the web app then we have Camel
Proxy to proxy to the endpoint).
Browser-->HTT2-->Tomcat Web App (Reverse Proxy) -->HTT1.1 --> 3rd Party UI
Since Tomcat is configured with HTTP protocol, the browser automatically
negotiates the http2 protocol. Is there any way to configure some path (
/context-path/XXX) would still needs to be HTTP 1.1.
No.
Currently, the only option is for us to open different connector ports strictly
with HTTP 1.1 and have traffic land here. Is there any better approach for
this ?
The reverse proxy should work equally well whether the client uses
HTTP/1.1, HTTP/2 or AJP. My recommendation would be to fix the bug(s) in
the reverse proxy code that cause it to break with HTTP/2.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
