-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Error handling on ee9 / ee8 with HTTP/1.0 can result in an empty Connection:
response header.
#12104
Labels
Bug
For general bugs on Jetty side
Comments
joakime
added a commit
that referenced
this issue
Jul 29, 2024
+ Fix empty `Connection:` response header issue seen on HTTP/1.0
joakime
added a commit
that referenced
this issue
Aug 1, 2024
gregw
added a commit
that referenced
this issue
Aug 2, 2024
Fix #12104 by better handling of `close` and `keep-alive` values in the HttpGenerator, so that we never add an empty field.
gregw
added a commit
that referenced
this issue
Aug 2, 2024
Fix #12104 by returning a CombinedResource for a ClassLoader resource that has multiple directory matches.
joakime
added a commit
that referenced
this issue
Aug 2, 2024
…nHeader Fix #12104 Empty Connection Header
gregw
added a commit
that referenced
this issue
Aug 5, 2024
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Jetty version(s)
12.0.11 (possibly older)
Jetty Environment
ee9 / ee8
Java version/vendor
(use: java -version)
Any
OS type/version
Any
Description
If an error response is produced in ee9 / ee8 from an HTTP/1.0 request then the resulting
Connection:
header can be empty/blank.Example request: This is a POST request to an endpoint that doesn't exist (expected to return 404), and it doesn't send all of the request content.
The response seen:
Notice the missing
Connection
response header value.The text was updated successfully, but these errors were encountered: