You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WebSockets are established through an HTTP handshake but the browser's WebSockets API doesn't allow me to put an authorization header into that handshake. I want to use the same authentication on my websocket endpoint as I do for all other endpoints on my server not be forced to use cookies. Adding the ability to set custom headers (or even just an authrorization header) as part of the WebSocket constructor would address this.
This discussion was converted from issue #189 on December 04, 2020 22:39.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
WebSockets are established through an HTTP handshake but the browser's WebSockets API doesn't allow me to put an authorization header into that handshake. I want to use the same authentication on my websocket endpoint as I do for all other endpoints on my server not be forced to use cookies. Adding the ability to set custom headers (or even just an authrorization header) as part of the WebSocket constructor would address this.
https://webwewant.fyi/wants/27/
Beta Was this translation helpful? Give feedback.
All reactions