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
I have been working with web sockets in node-http-proxy and I didn't see any path that would allow one to modify the HTTP headers of the proxy request used to conduct the web socket handshake.
The web socket protocol allows the server to fail the connection and make application level decisions based on any other part(s) of the HTTP request (i.e. pre-handshake-response authentication that is not supplied from the incoming request in my case).
It would seem that emitting an event named 'proxyWsReq' with the proxyReq as arguments would be a valid use case. This could be done right before proxyReq.end() is called in the ws-incoming.js passes.
The text was updated successfully, but these errors were encountered:
I have been working with web sockets in node-http-proxy and I didn't see any path that would allow one to modify the HTTP headers of the proxy request used to conduct the web socket handshake.
The web socket protocol allows the server to fail the connection and make application level decisions based on any other part(s) of the HTTP request (i.e. pre-handshake-response authentication that is not supplied from the incoming request in my case).
It would seem that emitting an event named 'proxyWsReq' with the proxyReq as arguments would be a valid use case. This could be done right before proxyReq.end() is called in the ws-incoming.js passes.
The text was updated successfully, but these errors were encountered: