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

Fixed websocket path #68

Merged
merged 2 commits into from
Apr 29, 2024
Merged

Fixed websocket path #68

merged 2 commits into from
Apr 29, 2024

Conversation

mtmk
Copy link
Contributor

@mtmk mtmk commented Apr 28, 2024

Allow path to be passed into websocket connection so that if there is a proxy in between it can be setup with a path on the proxy server even though it doesn't matter for the server connection.

Also there is a future option we can introduce to pass HTTP headers in case application might use them to authenticate with the proxy for example.

Note: this feature was already present in the original websocket-kit code and I chose to simplify it at the time.

Allow path to be passed into websocket connection
so that if there is a proxy in between it can be
setup with a path on the proxy server even though
it doesn't matter for the server connection.

Also there is a future option we can introduce to
pass HTTP headers in case application might use them
to authenticate with the proxy for example.
@mtmk mtmk requested review from Jarema and piotrpio April 28, 2024 17:19
Copy link
Contributor

@piotrpio piotrpio left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@Jarema Jarema merged commit 64514c3 into main Apr 29, 2024
3 checks passed
@Jarema Jarema deleted the fix-websocket-path branch April 29, 2024 15:08
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.

3 participants