Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No handling of connections suspended by a proxy #40

Closed
Incognito opened this issue Dec 6, 2013 · 1 comment
Closed

No handling of connections suspended by a proxy #40

Incognito opened this issue Dec 6, 2013 · 1 comment

Comments

@Incognito
Copy link

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:

  1. Client requests upgrade connection via ab
  2. Request is passed through proxy to WebSocketServer
  3. Upgrade response is sent back to proxy
  4. Proxy suspends all socket traffic because it can't deal with it.
  5. connection.onOpen is never called while pending
@oberstet
Copy link
Contributor

oberstet commented Dec 6, 2013

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).

@oberstet oberstet closed this as completed Dec 6, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants