Closed ChasLui closed 3 years ago
I like this. But the last time I checked not all browsers supported headers in Websocket connections. Some just ignore the headers option. Can you please check whether this works in Chrome, Firefox, and Safari?
I like this. But the last time I checked not all browsers supported headers in Websocket connections. Some just ignore the headers option. Can you please check whether this works in Chrome, Firefox, and Safari?
Unfortunately, the websocket headers cannot be set in Chrome, Firefox, and Safari browsers
I'm a bit confused. So what does this PR achieve?
I think he wants support in Node.js (see initial comment).
I'm a bit confused. So what does this PR achieve?
When using require('ws') as WebSocketPolyfill in nodejs, it is necessary to set the cookie. For more details, see https://github.com/websockets/ws/issues/1411
Setting a cookie is optional. But since this would only enable cookies in Websocket
provided by ws
, and because it is incompatible with the Websocket
constructor provided by the browser, I'm hesitant to merge this.
use provider in nodejs, should set cookie to auth
Huly®: YJS-769