Closed chge closed 9 years ago
Feel free to pullreq ;)
Otherwise it'll be added eventually, but it's currently in the back of the line.
Hi,
I see the issue was posted almost three years ago, is the feature supported now? If so, is it documented anywhere?
Thanks,
This issue has already been resolved in a previously merged commit which solved several related issues. Includes a passing test "Custom headers" in the test/WebSocket.test.js
commit 43a0b2b0277d64ffbb58e074b69cb9341923a3d2
I have been using this custom headers feature in my WS clients without issue, though before realizing this open issue.
Thanks for the heads up, seems like I missed this issue when closing a bunch of things.
It would be very helpful if ws.WebSocket implementation would allow to override/append HTTP request headers for handshake. For example, client may want to set custom headers with implementation-specific values, instead of sending them after handshake.
The RFC-6455 doesn't restrict this.