Skip to content
This repository has been archived by the owner on May 5, 2020. It is now read-only.

Support Authorization header #21

Open
benjamin-bergia opened this issue May 8, 2017 · 2 comments
Open

Support Authorization header #21

benjamin-bergia opened this issue May 8, 2017 · 2 comments

Comments

@benjamin-bergia
Copy link

I am trying to pass my user credentials to my websocket server using the url ws://username:password@mysite.com. Unfortunately on the server side I don't see any Authorization header.

I initially thought about an old chromium issue but I have the exact same issue on FIrefox.

It would be very nice to support HTTP basic auth during upgrade request or even better, allow us to pass additional headers (maybe in the low level API).

@process-bot
Copy link

Thanks for the issue! Make sure it satisfies this checklist. My human colleagues will appreciate it!

Here is what to expect next, and if anyone wants to comment, keep these things in mind.

@phile314-fh
Copy link

This seems to be unsolvable, as the JS API itself doesn't support setting any headers:

https://stackoverflow.com/questions/22383089/is-it-possible-to-use-bearer-authentication-for-websocket-upgrade-requests/26123316#26123316

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants