|Re: [jetty-users] HTTP/2 transparancy (longish)|
On 11/21/2015 12:55 PM, Simone Bordet wrote:
It's difficult to tell what went wrong without further details on the errors that happened.
Yes, I know. I was just hoping there might be some probable suspects I could check or someone might have experienced similar problems and could point me in the right direction.
If this is reproducible for this user, it would be a good starting point to investigate. Did you have server-side errors ? Where and how you offload TLS ? Like you say, HTTP/2 should be (and actually is) completely transparent. Gmail and all Google applications (YouTube, etc.) work on HTTP/2 without the users knowing. Make sure you are on the latest Jetty (9.3.6). You may want to consider commercial support, perhaps ? That would save you a lot of time/investigation. Or, give us something more detailed to analyze.
All the errors are server-side. The server side code misbehaves because it receives different HTTP messages when using HTTP2 versus HTTP/1.1. This seems to be tied to the way a users environment is setup.
We run Jetty 9.3.6 on OpenJDK 8 on mostly Ubuntu servers. We do not offload TLS ad rely heavily on the SNI facility in Jetty.
I will try to collect some more details by adding more detailed logging and have some users test with HTTP/2 enabled. Perhaps that will allow me to come back with more details.
Thanks for your comments so far. Cheers, Silvio
Back to the top