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

Send any headers already queued in the plug when upgrading websocket #458

Merged
merged 1 commit into from
Jan 15, 2025

Conversation

mtrudel
Copy link
Owner

@mtrudel mtrudel commented Jan 14, 2025

Fixes #457, which was introduced in #428

@peaceful-james is it possible for you to re-test that the original issue from #422 is still fixed with this branch?

Also improve the forever-tedious WebSocket upgrade test to read by
line instead of by byte count
@peaceful-james
Copy link

@mtrudel I gave it a quick "test" just now.
By "test", I mean that I simply run an app locally in https (with SSL) and do something with LiveView (handle a phx-click event, in particular).
When I reported the original issue, the problem was abundantly manifest (everything was broken).

What I'm saying is, it looks 100% good on my end, but I am not doing any kind of comprehensive testing.

@mtrudel
Copy link
Owner Author

mtrudel commented Jan 15, 2025

Good enough for me @peaceful-james !

@mtrudel mtrudel merged commit 41bb3d8 into main Jan 15, 2025
27 checks passed
@mtrudel mtrudel deleted the fix_upgrade_headers branch January 15, 2025 16:14
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.

Bandit does not send Sec-Websocket-Protocol header in Upgrade response
2 participants