Add web socket custom headers support in nats py client #722
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.
This pull request introduces support for custom headers in WebSocket connections to the NATS server. The key changes include:
Provision for supplying custom WebSocket request headers — developers can now attach additional HTTP headers (e.g., authorization tokens or tracing metadata) when establishing a WebSocket connection via NATS py.
A reference to a related issue in the .NET client repository (nats-io/nats.net#305) highlights the broader context and motivation for this enhancement.
Usage:
You can pass headers as a nats connection option ws_connection_headers.