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
Sometimes a proxy server that doesn't mange websockets correctly will be used (sometimes on the client's network somewhere also), and when this happens the request can be forever in a state of pending, saying the "connection is established" on my server but the client will never reach the onOpen callback.
This is kind of tricky because there's no clear way to test for it.
AutobahnJS can't to anything about broken proxies. Establishing the WebSocket connection is browser business. You might try to use TLS (secure WebSocket aka WSS) to prohibit proxy inteference (this will work unless you have a MITM proxy).
Sometimes a proxy server that doesn't mange websockets correctly will be used (sometimes on the client's network somewhere also), and when this happens the request can be forever in a state of pending, saying the "connection is established" on my server but the client will never reach the onOpen callback.
This is kind of tricky because there's no clear way to test for it.
One such proxy that has this behavior is pound: http://www.apsis.ch/pound/
To be more clear here's what happens step-by-step:
The text was updated successfully, but these errors were encountered: