SQL Server 上的 WSDL 给出 HTTP 状态 505 版本不受支持
我是一名 DBA，而不是开发人员，所以如果这是一个愚蠢的问题，请原谅我。但我们在使用 SQL Server 2005 Web 服务端点时遇到了问题。在本地网络上，我可以在 Visual Studio 2010 中添加引用，没有任何问题。它使用摘要作为身份验证方案。
但是，当任何人尝试在另一个网络上添加 Web 引用时，例如新西兰的开发人员（我们位于美国俄亥俄州代顿），他会收到以下错误：
下载时出错 'http://server.domain.net:1280/release-single-address?wsdl'。这 请求失败，HTTP 状态 505：HTTP 版本不受支持。 元数据包含无法解析的引用： 'http://server.domain.net:1280/release-single-address?wsdl'。这 远程服务器返回意外响应：(505) HTTP 版本不正确 支持。远程服务器返回错误：(505) Http 版本不正确 支持。如果当前解决方案中定义了该服务，请尝试 构建解决方案并再次添加服务引用。
同样，这在 Visual Studio 中可以作为右键单击添加引用 ->高级->在本地子网上作为服务器完成后添加 Web 引用。
在任何其他网络上完成时，该服务不会导入。我们已经尝试过没有任何代理。涉及跨域信任，但这似乎不是问题，因为使用来自任一域的帐户都会发生错误。当我将原始 XML 下载到硬盘时，我可以使用它来创建 Web 引用。我坚信这是某种传输层问题，例如代理，但禁用代理服务器设置时的捕获并不是结论性的。
I am a DBA, not a developer, so forgive me if this is a silly question. But we are having issues with a SQL Server 2005 Web Service end point. On the local network I am able to add the reference in Visual Studio 2010 with out any issues. It uses digest as the authentication scheme.
However, when anyone tries to add the web reference on another network, such as a developer in New Zealand (we are in Dayton, OH USA) he receives this error:
There was an error downloading
'http://server.domain.net:1280/release-single-address?wsdl'. The
request failed with HTTP status 505: HTTP Version not supported.
Metadata contains a reference that cannot be resolved:
'http://server.domain.net:1280/release-single-address?wsdl'. The
remote server returned an unexpected response: (505) HTTP Version not
supported. The remote server returned an error: (505) Http Version Not
Supported. If the service is defined in the current solution, try
building the solution and adding the service reference again.
Again, this works in Visual Studio as Right Click add Reference -> Advanced -> Add Web Reference when done on the local subnet as the server.
When done on any other network the service does not import. We have tried it w/o any proxy. There is a cross domain trust involved but that does not seem to be the issue as the error occurs using accounts from either domain. When I download the raw XML to my hdd I can use that to create the web reference. I believe firmly this is some sort of transport layer issue, such as a proxy, but captures when the proxy server settings are disabled are not conclusive.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
今天，在我发布这个问题多年后，我们终于找到了这个问题的答案。它并不是我们所认为的 Squid 代理服务器。我们在各种网络服务/网站上不断遇到此类问题。最后一根稻草是当我们最终需要部署一个供跨国软件工程团队使用的 SVN 服务器时。我们采访过的不同运营团队的每一位成员都向我们发誓，站点之间没有任何东西可能会破坏我们的服务。
幸运的是，该公司的首席信息安全官正在访问我们的网站，一位同事碰巧遇到了他，并询问了我们遇到的问题以及可能的原因。他立即表示，Riverbed 设备对所有 WAN 流量进行缓存和第 7 层检查。我们最终设法在尝试“规范化”HTML 和 XML 的过程中捕获这些设备，并且能够捕获来自新西兰机器的数据。我们对所提供的 HTML 页面以及来自 Web 服务的 XML 进行了比较，以比较它在本地网络上与在 WAN 上的外观。在通过 WAN 提供的页面/XML 中，插入了不需要的结束标记或实际上导致 XML 格式错误的结束标记。如果设备不知道如何处理某些标签，甚至会完全注释掉它们。那么确凿的证据呢？自定义标头...
X-RBT-Optimized-By: cch-riverbed-1 (RiOS 6.5.6a) SC“优化”您继续使用这个词，但我不认为这意味着你认为这意味着什么。
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.
我不是 VS 的 SOAP 专业人士，但 SOAP 的版本可能与 sql server 2005 不兼容？
如果我没记错的话，SOAP 有两个版本：1.1 和 1.2。
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.
检查HTTP GET命令格式是否正确？
HTTP GET http:// mydomain.com HTTP/1.1\
注意“http://”和“mydomain.com”之间有一个空格。服务器无法匹配此格式。结果是505
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
我不确定，但我认为您应该检查您的防火墙或 IIS 配置。
I am not sure but, I think you should check your firewall or your IIS configuration.