在HTTP HOST标头中包含端口号会导致服务不可用错误 [英] Including Port number in HTTP HOST header causes Service Unavailable error

查看:870
本文介绍了在HTTP HOST标头中包含端口号会导致服务不可用错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我们在HTTPS上运行WebService。如果我使用SOAPUI并发出请求: https://testservice.mydomain.com/WcfService.svc,它工作正常。但是,客户端报告他们收到了503 Service Unavailable错误。

We have a WebService running on HTTPS. If I use SOAPUI and make request at: https://testservice.mydomain.com/WcfService.svc, it works fine. However the client reported they are getting 503 Service Unavailable error.

在他们的HTTP HOST 标题中,我看到 - > testservice.mydomain.com: 443。
为了复制我创建了一个测试C#客户端并手动设置HOST头以包含请求中的443端口。我得到相同的错误,IIS网站日志中没有记录任何内容。类似地,在SOAPUI中,如果我点击URL: https://testservice.mydomain.com:443/WcfService.svc (必须执行此操作,因为无法手动更改SOAPUI中的HOST标头)返回相同的服务不可用错误。

In their HTTP HOST header I see --> testservice.mydomain.com:443. To replicate that I created a test C# client and manually set the HOST header to include 443 port in request. I get the same error and nothing gets logged in IIS Website logs. Similarly in SOAPUI if I hit URL: https://testservice.mydomain.com:443/WcfService.svc (have to do this as can't manually change HOST header in SOAPUI) same Service Unavailable error is returned.

如果我通过浏览器访问服务,然后我甚至可以在URL中包含端口号后访问。我尝试访问在线可用的Web服务,我可以使用或不使用显式端口号正确访问它们。

If I access the service through browser, then I'm able to access even after including port number in URL.I tried accessing online available WebServices and I can access them correctly with or without the explicit port number.

这是IIS配置问题吗?我们使用IIS 7.5并使用HOST标头来托管多个站点。实际上我对IIS不太了解,所以只是推测。

Is this an IIS configuration issue? We use IIS 7.5 and use HOST headers to host multiple sites. Actually I don't know much about IIS so just speculating.

推荐答案

我们的网络团队解决了这个问题。 Netscaler的配置方式存在问题;不知怎的,它没有传递请求 - 它在头文件中有端口号,以纠正IP(托管WebService的地方)。

抱歉,我无法详细解释NetScaler解析。我两次问网络人员,他们的解释超出了我的想法。但无论如何,如果有人遇到类似问题,请查看您的Loadbalancer,DNS和防火墙。

Our network team resolved the issue. It was a problem with how the Netscaler was configured; somehow it was not passing on the requests -which had port number in header, to correct IP (where the WebService was hosted).
Sorry I can't explain NetScaler resolution in detail. I twice asked the network people and their explanation went way over my head. But in any case, if anyone has similar problem, check out your Loadbalancer, DNS and Firewall.

这篇关于在HTTP HOST标头中包含端口号会导致服务不可用错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆