We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Jetty version(s) 12.0.14
Jetty Environment ee8
Java version/vendor (use: java -version) 17.0.12
(use: java -version)
OS type/version Ubuntu 24.04.1 LTS
Description In JsrHandshakeRequest the method getHeaders() is case sensitive.
In JavaEE8 and JakartaEE9/10 https://javaee.github.io/javaee-spec/javadocs/javax/websocket/server/HandshakeRequest.html#getHeaders-- Return the read only Map of Http Headers that came with the handshake request. The header names are case insensitive.
How to reproduce?
The text was updated successfully, but these errors were encountered:
Issue #12429 - case-insensitive headers for websocket
8ff6828
Signed-off-by: Lachlan Roberts <lachlan.p.roberts@gmail.com>
Issue #12429 - optimize implementation of HttpFields.asMap
0487815
Merge pull request #12441 from jetty/jetty-12.0.x-12429-caseInsensiti…
b57b8e6
…veHeadersWebSocket Issue #12429 - case-insensitive headers for websocket
@laurentriviere thanks for the report, this has been fixed in #12441 and will be available in the next release 12.0.16.
12.0.16
Sorry, something went wrong.
lachlan-roberts
Successfully merging a pull request may close this issue.
Jetty version(s)
12.0.14
Jetty Environment
ee8
Java version/vendor
(use: java -version)
17.0.12
OS type/version
Ubuntu 24.04.1 LTS
Description
In JsrHandshakeRequest the method getHeaders() is case sensitive.
In JavaEE8 and JakartaEE9/10
https://javaee.github.io/javaee-spec/javadocs/javax/websocket/server/HandshakeRequest.html#getHeaders--
Return the read only Map of Http Headers that came with the handshake request. The header names are case insensitive.
How to reproduce?
The text was updated successfully, but these errors were encountered: