-
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
HTTP2 Jetty Server does not send back content-length #4764
Labels
Comments
You are correct that currently we don't add the Can you expand on how this header will be useful to a HTTP/2 client? |
Few examples
|
sbordet
added a commit
that referenced
this issue
Apr 14, 2020
Updates after review. Now the Content-Length header is generated by HpackEncoder based on MetaData.contentLength, so that the MetaData.HttpFields are not modified. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Apr 14, 2020
Fixed InterleavingTest that was using the wrong MetaData.Response constructor. Fixed handling of HEAD methods in HttpTransportOverHTTP2. Signed-off-by: Simone Bordet <simone.bordet@gmail.com>
sbordet
added a commit
that referenced
this issue
Apr 14, 2020
…length Fixes #4764 - HTTP2 Jetty Server does not send back content-length.
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jetty version 9.4.24.v20191120
Java version Java 11
Question On requesting to a plain text HTTP2 (h2c) Jetty Server, the response doesn't include content-length in the header. But with that same server on requesting using HTTP/1.1, the server does return content-legth.
I understand that content-length is not required for HTTP2 protocol. But it will be very helpful for client for handling the response if content-length is available. So do Jetty have any configuration to enforce server to return content-length in the header?
The text was updated successfully, but these errors were encountered: