Skip to content
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

Merged
merged 1 commit into from Jul 12, 2019

Conversation

amizurov
Copy link
Sponsor Contributor

@amizurov amizurov commented Jul 1, 2019

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 .

@netty-bot
Copy link

Can one of the admins verify this patch?

@normanmaurer
Copy link
Member

@netty-bot test this please

@normanmaurer
Copy link
Member

/cc @vietj

@normanmaurer
Copy link
Member

@slandelle ping...

@slandelle
Copy link
Contributor

LGTM

@normanmaurer normanmaurer merged commit be26f4e into netty:4.1 Jul 12, 2019
@normanmaurer
Copy link
Member

@amizurov thanks a lot!

@normanmaurer normanmaurer added this to the 4.1.38.Final milestone Jul 12, 2019
normanmaurer pushed a commit that referenced this pull request Jul 12, 2019
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 .
@marci74
Copy link

marci74 commented Aug 6, 2019

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

@normanmaurer
Copy link
Member

normanmaurer commented Aug 6, 2019 via email

@amizurov
Copy link
Sponsor Contributor Author

amizurov commented Aug 7, 2019

Hi guys, could you please check the #9435

@marci74
Copy link

marci74 commented Aug 8, 2019

@amizurov Looks good. Thank you very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

WebSocketClientHandshaker13 Invalid Handshake
5 participants