Hi!
It's a little hard for us to make sense of what's going on, because if it was a connectivity issue, then you wouldn't be able to access the ASMX from browser.
Could you please try a couple of things to help us troubleshoot this:
- Comment out "service.Proxy = new Proxy(..." line and set the HTTP Proxy settings in Internet Explorer Properties on the client machine. This will make your windows application pick default system HTTP Proxy settings from the WinInet. In this case if your browser is able to reach ASMX, then chances are your WS client will too. If you get the same result as before this will eliminate your client as a culprit.
- If that does not help, we'd recommend using
Fiddler to trace requests/response sessions between client and the service without HTTP Proxy in place. Fiddler when it runs, inserts itself as a default system HTTP proxy into WinInet (your can verify that in IE Connection Properties when Fiddler runs) and therefore would be helpful as both tracing tool and HTTP Proxy emulator. Fiddler will show you what's exactly is being sent over the wire. If it works with Fiddler but not qith Squid, then we'll need to go do more tracing to find out who's the bad guy.
- Third, to ensure that nothing is wrong with the service itself causing it to close the connection, please create a client for the web service provided by Cassini Explorer, which can be found at http://server:7756/CassiniConfigurationService.asmx where "server" is the host name of the machine running UltiDev Cassini. If you experience the same issue with our service as with yours, it will eliminate the service as a culprit.
Please let us know about the results.
Best regards,
UltiDev Team.
Please donate at
http://www.ultidev.com/products/Donate.aspx to help us improve our products.