fix(proxy): block cookie header in WebSocket forwarding#894
Merged
Issac-Newton merged 1 commit intoApr 24, 2026
Merged
Conversation
Issac-Newton
force-pushed
the
fix/websocket-origin-proxy-spec
branch
3 times, most recently
from
d6c04bf to
54796e3
Compare
…switch - Add forward_ws_headers bool to websocket_proxy() — VNC route sets it to False to avoid exceeding QEMU's 4KB header buffer limit - Update proxy-enhancements spec docs to reflect current implementation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Issac-Newton
force-pushed
the
fix/websocket-origin-proxy-spec
branch
from
54796e3 to
f78a86b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cookie headers from upstream gateways contain SSO tokens and can be oversized, causing 502 when forwarded to downstream WebSocket services.
close #865