This project is read-only.

Connecting through proxy

Jul 17, 2012 at 3:12 PM

Hello,

thanks for your great project, it has eased my work.

Connecting without a proxy works great, no problems, but unfortunately I have to connect through a (corporate) one.

After handshaking successfully it doesn't establish the connection.

Is there any way to specify some proxy data so that the client knows about them?

Coordinator
Jul 17, 2012 at 5:25 PM
Edited Jul 17, 2012 at 5:27 PM

If the initial handshake (http request portion) is making it outbound - it sounds like the corporate proxy is blocking the upgrade (to websocket).  

From a browser behind your corporate proxy - can you try : http://www.websocket.org/echo.html

Try both ws and wss (use secure WebSocket TLS) options & send the echo message, do both connections work?  

Jul 18, 2012 at 9:28 AM

I forgot to mention some (maybe important) facts:

- I also use TLS

- The server expects the connection at a specified port, not some default port

 

Connecting with the ws-option at the echo-test doesn't work. The secure wss-option on the other hand can establish the connection.

Coordinator
Jul 18, 2012 at 12:15 PM

"Connecting with the ws-option at the echo-test doesn't work. The secure wss-option on the other hand can establish the connection."
Tells me that your corporate proxy is affecting your connections - but does allow (bypasses) ssl/wss connections.

"The server expects the connection at a specified port, not some default port"
So you are using TLS (but not on port 443), your corporate proxy is again stepping in, blocking the http upgrade on the non-standard TLS port. You'll need to work that out with your corp. IT folks, there isn't any setting via the client app that will bypass that restriction.

Jul 18, 2012 at 1:46 PM

Okay, I was afraid you would say that. ;-)

Now, being certain of the circumstances causing the problem, I have to find a solution on my end.

 

Anyway, thanks a lot for your quick responses. :-)

Mar 17, 2014 at 2:18 PM
Hello,

I have been using this project in an application and it has simplified things a lot. I really appreciate all the effort that has been put into this.

Coming back to the discussion here, I am wondering and hoping whether by now we have some way of getting the sockets to work from behind a proxy. That is the only thing that I am stuck with now, I hope there is some help regarding Proxies and Socket Usability :)

Thank You
Coordinator
Mar 17, 2014 at 5:44 PM
I can sympathize with you, but from a websocket library perspective, about the only other option (without external intervention) is fallback support that circumvents the connection/upgrade issue. For now you can head over to the develop branch and maybe try out the xhr-polling support. Any help & suggestions from there moving forward are very much welcomed!

Thanks for the feedback, I'm glad to hear the project has simplified things for you.

Jim