I was unaware that browsers do not support additional headers such as Authorization. This was problematic for me as the authorization header sending a bearer token is the method of authorization used in the application I was adding SignalR hub to.
So how are you supposed to send a token?
The immediate answer and for the most part, the only answer I found was too pass via the query string. Meaning specifying the toke in the query string when defining your connection in the
I wasn’t in love with this solution but I was able to make it work. I decide to tweet about it had David Fowler provide a really interesting GitHub issue that I’d recommend reading.
— David Fowler 🇧🇧 (@davidfowl) June 7, 2018
If you you are using SignalR/WebSockets client from the browser, how are you passing additional information such as Authorization data to the server? Let me know in the comments or on Twitter.