Skip to content

fix(guard): allow path-based WebSocket requests without sec-websocket-protocol header - #5664

Open
Tyagiquamar wants to merge 1 commit into
rivet-dev:mainfrom
Tyagiquamar:fix/guard-websocket-header-optional
Open

fix(guard): allow path-based WebSocket requests without sec-websocket-protocol header#5664
Tyagiquamar wants to merge 1 commit into
rivet-dev:mainfrom
Tyagiquamar:fix/guard-websocket-header-optional

Conversation

@Tyagiquamar

Copy link
Copy Markdown

In path-based WebSocket routing (
ead_gateway_token_for_path_based), if \sec-websocket-protocol\ header is absent, return \Ok(None)\ instead of failing with a \MissingHeader\ error.

This allows path-based WebSocket connections (such as the Hub UI inspector console) to connect without requiring a token header when unauthenticated or when the token is omitted.

Fixes #5481.

…-protocol header

In path-based WebSocket routing (read_gateway_token_for_path_based), if sec-websocket-protocol header is absent, return Ok(None) instead of failing with MissingHeader error. This allows path-based WebSocket connections (e.g. Hub UI inspector console) to connect without requiring a token header.

Signed-off-by: Tyagiquamar <mohdquamartyagi@gmail.com>
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.

bug(hub): Inspector Console WebSocket fails — Hub UI does not send Sec-WebSocket-Protocol header

1 participant