-
Notifications
You must be signed in to change notification settings - Fork 70
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
Incorrect scheme specified within Origin header during WebSocket Handshake #2215
Comments
The attached diff contains a fix for the issue along with the associated tests. |
cgdrake
added a commit
to cgdrake/grizzly
that referenced
this issue
Oct 30, 2024
…non-SSL WebSocket connections
cgdrake
added a commit
to cgdrake/grizzly
that referenced
this issue
Oct 30, 2024
…non-SSL WebSocket connections
cgdrake
added a commit
to cgdrake/grizzly
that referenced
this issue
Oct 30, 2024
…non-SSL WebSocket connections
cgdrake
added a commit
to cgdrake/grizzly
that referenced
this issue
Oct 30, 2024
…non-SSL WebSocket connections
It seems like a bug. I'll take a look and review your PR. |
cgdrake
added a commit
to cgdrake/grizzly
that referenced
this issue
Jan 7, 2025
…non-SSL WebSocket connections
cgdrake
added a commit
to cgdrake/grizzly
that referenced
this issue
Jan 7, 2025
…non-SSL WebSocket connections
carryel
added a commit
that referenced
this issue
Jan 8, 2025
Issue #2215 Fix invalid Origin header sent by client for non-SSL WebSocket connections
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Establishing a non-SSL WebSocket connection results in an Origin header being sent by the client which erroneously specifies the scheme as
wss
. In addition, a call toHandshake.isSecure()
reports true when in fact the connection is insecure.The following test demonstrates the issue when run again all current versions of Grizzly:
Result:
The text was updated successfully, but these errors were encountered: