For websocket requests, the onProxyReq hook is not executed and thus the original Origin is sent to the target server. The target server will likely reject the request because Host and Origin mismatch (Gorilla websockts in my case). To also patch Origin for websocket requests, the onProxyReqWs hook has to be specified additionally.
Steps to reproduce
Add a breakpoint or console.log in the onProxyReq callback mentioned above.
yarn start any created project with a configured proxy
Open a websocket connection
See nothing getting logged because only onProxyReqWs is called for websocket connections.
Expected behavior
Origin and Host are equal for proxied websocket requests (e.g. http://localhost:8080).
Actual behavior
Origin is the original header sent by the browser (e.g. http://localhost:3000) while Host is changed (e.g. http://localhost:8080).
--
Note: I'd have sent a patch, but I refuse to sign the CLA.
dedo1911
commented
2 years ago
Describe the bug
Setting the
proxyfield inpackage.jsonproxies normal HTTP requests and WebSocket requests.For normal requests, the
Originheader is patched to equal the target host (added in #1212).For websocket requests, the
onProxyReqhook is not executed and thus the originalOriginis sent to the target server. The target server will likely reject the request becauseHostandOriginmismatch (Gorilla websockts in my case). To also patchOriginfor websocket requests, theonProxyReqWshook has to be specified additionally.Steps to reproduce
console.login theonProxyReqcallback mentioned above.yarn startany created project with a configured proxyonProxyReqWsis called for websocket connections.Expected behavior
OriginandHostare equal for proxied websocket requests (e.g.http://localhost:8080).Actual behavior
Originis the original header sent by the browser (e.g.http://localhost:3000) whileHostis changed (e.g.http://localhost:8080).--
Note: I'd have sent a patch, but I refuse to sign the CLA.