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
Fixed incorrect Sec-WebSocket-Origin header for v13, see #9134 #9312
Fixed incorrect Sec-WebSocket-Origin header for v13, see #9134 #9312
Conversation
Can one of the admins verify this patch? |
@netty-bot test this please |
/cc @vietj |
@slandelle ping... |
LGTM |
@amizurov thanks a lot! |
Motivation: Based on https://tools.ietf.org/html/rfc6455#section-1.3 - for non-browser clients, Origin header field may be sent if it makes sense in the context of those clients. Modification: Replace Sec-WebSocket-Origin to Origin Result: Fixes #9134 .
Hi, |
Can you open a PR for this ?
… Am 06.08.2019 um 17:29 schrieb marci74 ***@***.***>:
Hi,
we are using netty as a web socket client (through vert.x). In our tests we fake the "origin" header. This does not work anymore with version 4.1.38 since you always overwrite our custom the "origin" header. Could you please set the header conditionally (only if it does not already exist in the custom headers)?
Thanks.
Marc
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hi guys, could you please check the #9435 |
@amizurov Looks good. Thank you very much! |
Motivation:
Based on https://tools.ietf.org/html/rfc6455#section-1.3 - for non-browser
clients,
Origin
header field may be sent if it makes sense in the context of those clients.Modification:
Replace
Sec-WebSocket-Origin
toOrigin
Result:
Fixes #9134 .