-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Server can't upgrade from h1 to h2c #3235
Comments
Figured out that |
Narrowing scope of issue got that upgade from h1.1 to h2c goes well for GET requests but fails for POST |
https://tools.ietf.org/html/rfc7540#section-3.2 Looks like the HTTP/2 spec would support methods other then GET. |
The HTTP/2 spec delegates to the HTTP/1.1 spec for the upgrade, which does not mandate the use of the GET method. |
Sorry to do a drive-by on a closed issue, but it looks like the JDK will attempt an upgrade by default on a PUT and with plain text and chunked request body this blows up. This test illustrates this: Not sure whether this is a Jetty or JDK client issue, but since there are many clients that wrap it it'd be good to know if there's a way forward other than disabling HTTP/2 completely on the server. |
@tomakehurst can you please open a new issue? |
Sure: #11588 |
While running testFeignJava11H2cWithPayload test using Java 11 http client
get
GOAWAY
frame withDebugdata: invalid_preface
Here is how Jetty server configured: Jetty H2c
The text was updated successfully, but these errors were encountered: