Websocket headers are not transparently proxied

2 days ago

https://station.railway.com/questions/websocket-headers-are-not-transparently-f1e1d98e

Discord thread that is still relevant.

The Sec-Websocket-Key is intercepted and regenerated between the HTTP ingress and my deployed service, causing issues when relying on the header on either side.

Under Review

0 Threads mention this feature

0 Replies

Welcome!

Sign in to your Railway account to join the conversation.

Loading...