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

WebSocketClient.connect(): Ability to pass connection headers #1236

Closed
skc-j opened this issue Sep 10, 2023 · 1 comment · Fixed by #1299
Closed

WebSocketClient.connect(): Ability to pass connection headers #1236

skc-j opened this issue Sep 10, 2023 · 1 comment · Fixed by #1299
Assignees
Labels
enhancement New feature or request

Comments

@skc-j
Copy link

skc-j commented Sep 10, 2023

Feature Request for WebSocketClient.connect() with headers.

For some websockets, expect webscoket client to pass connection headers (such as "Origin", "Authorization", etc).

In the current version, WebSocketClient.connect() does not seem to accept headers (though tokio-tungstenite seems to have this ability to take header).

For websocket connections expecting such connection headers, I getting "Exception: Unable to make websocket connection because of error: HTTP error: 403 Forbidden".

@cjdsellers
Copy link
Member

Closed from #1299. Connection headers can now be specified with the WebSocketClientConfig.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Development

Successfully merging a pull request may close this issue.

3 participants