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
Issue #6642 - WebSocket handling of Connection: upgrade,close. #6657
Issue #6642 - WebSocket handling of Connection: upgrade,close. #6657
Conversation
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Here's one websocket lib making the same discovery we just did with the "close" token. |
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Should we offer a configuration for websocket to satisfy behaviors of bad websocket clients? What if the naive websocket client sends a normal I wonder if we should have a configuration that can force a |
Looks like |
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
jetty-http/src/main/java/org/eclipse/jetty/http/HttpGenerator.java
Outdated
Show resolved
Hide resolved
jetty-http/src/main/java/org/eclipse/jetty/http/HttpGenerator.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
…nnection Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
jetty-server/src/main/java/org/eclipse/jetty/server/HttpConnection.java
Outdated
Show resolved
Hide resolved
… response. Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Closes #6642
add tests for WebSocket Connection Headers.