WSDL on SQL Server gives HTTP status 505 Version Not Supported

Today, years after I posted this question, we finally found the answer to this question. It was not a Squid proxy server as we had come to believe. We continued experiencing issues like this with various web services/sites. The last straw was when we finally needed to deploy an SVN server that was used by multinational software engineering teams. Every single member of the different Ops teams we spoke to swore to us there was nothing between the sites that could break our services.

By a stroke of luck the company's Chief Information Security Officer was visiting our site and a colleague happened to run into him and asked about the issues we were having and what might be the cause of it. He said immediately that there were Riverbed appliances doing caching and layer 7 inspection on all WAN traffic. We finally managed to catch these devices in the act of attempting to "normalize" HTML and XML and we were able to perform a capture of data coming from a machine in New Zealand. We performed a diff on HTML pages that were served as well as XML coming from a web service to compare how it looked on the local network vs. across the WAN. In the pages/XML that were being served across the WAN the closing tags were inserted that were not needed or that actually made the XML malformed. Some tags were even commented out entirely if the appliance didn't know what to do with them. And the smoking gun? A custom header...

X-RBT-Optimized-By: cch-riverbed-1 (RiOS 6.5.6a) SC

"Optimized" You keep using that word, but I do not think that it means what you think that it means.

I'm not a pro of SOAP with VS but it may be that version of SOAP is incompatible with sql server 2005?

If I recall correctly, there is two versions of SOAP: 1.1 and 1.2.

Check the HTTP GET command format is correct?

HTTP GET http:// mydomain.com HTTP/1.1\

note there is a SPACE between 'http://' and 'mydomain.com'. The server can not match this format. The result is 505