This project is read-only.

How does the client work with the proxy server?

Apr 6, 2012 at 1:15 PM

I tried to run the client in the company's network and connect to a server hosted outside. The company requires a proxy server and only allows port 80 and 443 connections going out. As the test failed, I tried to check the external hosted server's log and did not see any incoming request log. I am wondering if the company's proxy server blocked the websocket connection. Or is there a way to configure the websocket client to use the proxy settings similar to the settings in the browser?

Apr 6, 2012 at 1:28 PM

WebSocket4Net doesn't support proxy yet. Anyway it is good requirement, I'll think about how to support it.

Jun 29, 2012 at 7:19 AM

Oh, sorry, I didn't remember updating with you.

I have implemented the proxy.


The websocket class have a Proxy attribute, you should set it before you start the connection.

You can find some proxy implementations in the assembly SuperSocket.ClientEngine.Proxy.dll (in Reference/SuperSocket.ClientEngine), like HttpConnectProxy, Socks4Proxy and Socks5Proxy.