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

WSS broken by frame masking #422

Closed
peaceful-james opened this issue Nov 18, 2024 · 10 comments · Fixed by #428
Closed

WSS broken by frame masking #422

peaceful-james opened this issue Nov 18, 2024 · 10 comments · Fixed by #428

Comments

@peaceful-james
Copy link

peaceful-james commented Nov 18, 2024

image

Maybe this is just happening for me. I am investigating.

@peaceful-james
Copy link
Author

I confirm problem goes away when I run on commit cd855ec.

@mtrudel
Copy link
Owner

mtrudel commented Nov 18, 2024

Thanks for the note. I'll back out that addition to give @alisinabh a chance to address it

@peaceful-james
Copy link
Author

Thanks for the note. I'll back out that addition to give @alisinabh a chance to address it

Wait, I am blaming the wrong PR. It works fine on commit 898afdc.

@peaceful-james
Copy link
Author

OK I confirm the problem is on commit f16b4c3 which is PR #421 which is yours @mtrudel

The call is coming from inside the house

@mtrudel
Copy link
Owner

mtrudel commented Nov 18, 2024

Can you provide a repro?

@alisinabh
Copy link
Collaborator

I took a quick look and it seems like we responding with compression enabled (content-encoding: gzip) on websocket which is not supported for websocket (it is but permessage-deflate must be used).

Working version

Screenshot 2024-11-18 at 11 32 07 AM

Not working version

Screenshot 2024-11-18 at 11 32 26 AM

@mtrudel
Copy link
Owner

mtrudel commented Nov 18, 2024

Got it! I backed that PR out of main/1.6.0 and re-released. I'll get this fixed directly.

Since this is no longer an issue on main I'll copy the relevant details from here over to #421 (which I'll also reopen).

Thanks for the quick bug @peaceful-james !

@peaceful-james
Copy link
Author

OK that explains why my repro was not working. 😆 Thanks for the swift response!

@mtrudel
Copy link
Owner

mtrudel commented Dec 6, 2024

All of the relevant fixes are in 1.6.1, just released. If you're able, I'd greatly appreciate confirmation that your concerns are still fixed in it!

@peaceful-james
Copy link
Author

@mtrudel I used 1.6.1. No issues! 👍🏻 I confirm that my "concerns are still fixed in it".

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 a pull request may close this issue.

3 participants