D
Dave A
I recently posted about the lack of support for SOCKS proxy in WebServices.
It is possible to write a low level class that will tunnel through a SOCKS
proxy and return an open TcpSocket (www.componentspace.com has one) but a
WebRequest (that WebServices are based on) does not allow access to the
underlying TcpSocket unfortunately and nor does it allow you to configure a
proxy other than HTTP.
I started thinking that SOCKS proxies must be a thing of the past, totally
dead and no longer support by any Microsoft technology. Only tonight I
discovered that the latest version MSN Messenger supports SOCKS proxies! IE
does too.
What is the status of SOCKS proxies? Are they dead? Who uses them? Should a
widely distributed WinForms application that needs to make SOAP calls
support a SOCKS proxy server? And most importantly, if so then how?
Regards
Dave A
It is possible to write a low level class that will tunnel through a SOCKS
proxy and return an open TcpSocket (www.componentspace.com has one) but a
WebRequest (that WebServices are based on) does not allow access to the
underlying TcpSocket unfortunately and nor does it allow you to configure a
proxy other than HTTP.
I started thinking that SOCKS proxies must be a thing of the past, totally
dead and no longer support by any Microsoft technology. Only tonight I
discovered that the latest version MSN Messenger supports SOCKS proxies! IE
does too.
What is the status of SOCKS proxies? Are they dead? Who uses them? Should a
widely distributed WinForms application that needs to make SOAP calls
support a SOCKS proxy server? And most importantly, if so then how?
Regards
Dave A