Skip to content

feat: add hashHeadersWhitelist configuration for selective header hashing#803

Closed
glower wants to merge 1 commit intowundergraph:mainfrom
glower:feature/ws-header-whitelist
Closed

feat: add hashHeadersWhitelist configuration for selective header hashing#803
glower wants to merge 1 commit intowundergraph:mainfrom
glower:feature/ws-header-whitelist

Conversation

@glower
Copy link
Copy Markdown

@glower glower commented May 18, 2024

Added support for a new configuration option hashHeadersWhitelist in the WebSocket configuration. This allows specifying a whitelist of headers that should be hashed and forwarded during WebSocket connections.

The implementation includes updates to the schema and handling of the new configuration option in the WebSocketConnectionHandler

Motivation and Context

Implement an allow-list to have fine-grained control over which headers are hashed in the initial subscription upgrade request.

TODO

… header hashing

Added support for a new configuration option `hashHeadersWhitelist` in the WebSocket configuration. This allows specifying a whitelist of headers that should be hashed and forwarded during WebSocket connections. The implementation includes updates to the schema and handling of the new configuration option in the `WebSocketConnectionHandler`.\n\nEnsured that the existing `ignoreHeader` method remains intact for backward compatibility. Users can use `hashHeadersWhitelist` to specify headers to be hashed in addition to those already managed by `ignoreHeader`.
Comment thread router/core/websocket_test.go
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants