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.

Sign up for GitHub

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

Jump to bottom

Browser connections fail with "A server must not mask any frames that it sends to the client" #213

Closed
paoloambrosio opened this issue Aug 12, 2022 · 3 comments
Closed

Browser connections fail with "A server must not mask any frames that it sends to the client" #213

paoloambrosio opened this issue Aug 12, 2022 · 3 comments

Comments

@paoloambrosio
Copy link

Since upgrading from 6.2.0 to 6.4.0, WebSockets connections from the Web browser (Chrome 104.0.5112.81) stopped working. The error is A server must not mask any frames that it sends to the client.

It can be reproduced in the WsChatServer example.

6.2.0:
image

6.4.0:
image
@chronoxor
Copy link
Owner

Will look...

chronoxor added a commit that referenced this issue Aug 12, 2022
@chronoxor
Browser connections fail with "A server must not mask any frames that…
e2f8d14 
… it sends to the client" #213
@chronoxor
Copy link
Owner

Fixed. Please check version 6.5.0

@paoloambrosio
Copy link
Author

Upgrading to 6.5.0 fixed the issue both in the example and my software. Thanks!

@paoloambrosio paoloambrosio mentioned this issue Aug 12, 2022
Merged
lukebakken pushed a commit to lukebakken/NetCoreServer that referenced this issue Feb 8, 2024
@chronoxor @lukebakken
Browser connections fail with "A server must not mask any frames that…
0f21b0a 
… it sends to the client" chronoxor#213
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@paoloambrosio @chronoxor