简体繁体 English

Apache Http服务器POST 400

[英]Apache Http Server POST 400

原文 2013-11-07 18:16:48 5 1 web-services/ apache/ http

that's my first question here. 这是我的第一个问题。 After long research, I decided to ask for help... 经过长时间的研究，我决定寻求帮助...

So first I'll explain my scenario. 首先，我将解释我的情况。 I have some SOAP web services here. 我这里有一些SOAP Web服务。 They're consumed by an .Net website. 它们由.Net网站使用。 The .Net framework used is in version 4.0. 使用的.Net框架在版本4.0中。

So my web services are configured to accept HTTP/1.0 protocol, due to .Net limitations. 因此，由于.Net的限制，我的Web服务被配置为接受HTTP / 1.0协议。 In spite of that, everything works fine if I access the service directly to Jboss AS(4.2.2 GA). 尽管如此，如果我直接访问Jboss AS（4.2.2 GA），则一切正常。

But, I have to make it work with Apache web server as the receptor of the request. 但是，我必须使其与Apache Web服务器一起作为请求的接受者。 Apache do a inverse proxy redirection to my service, so the site send requests to port 8080 (that Apache is listening) and send it to jboss that is expecting the request at port 18080. Apache对我的服务执行了反向代理重定向，因此该站点将请求发送到端口8080（Apache正在侦听），然后将其发送到期望在18080端口请求的jboss。

In many tests, I confirmed that almost every service worked almost fine, sometimes they have the same failure. 在许多测试中，我确认几乎每个服务都可以正常工作，有时它们也有相同的故障。 But one in particular don't work anyway, the request stopped at Apache with status 400 and empty value (the - after the 400) like that: 但尤其是其中一个始终无法正常工作，该请求在Apache处停止，状态为400，空值（在-400之后为-），如下所示：

POST /xxxx/xxxx/xxxxx/MyService HTTP/1.1" 400 - "-" "Mozilla/4.0 (compatible; MSIE 6.0; MS Web Service Client Protocol 4.0.30319.296) POST / xxxx / xxxx / xxxxx / MyService HTTP / 1.1“ 400-”-“” Mozilla / 4.0（兼容； MSIE 6.0； MS Web服务客户端协议4.0.30319.296）

The other requests that are processed have this value filled. 处理的其他请求将填充此值。 I guess is the response size. 我猜是响应大小。

Please consider my regards. 请考虑我的问候。 thanks 谢谢

1 个解决方案

After great efforts at my company we discovered using an Sniffer(Wireshark) that we had two problems that let us to had the situation described in this problem. 经过我公司的巨大努力，我们发现使用Sniffer（Wireshark）遇到了两个问题，使我们不得不对此问题进行描述。

First problem solved: .Net platform is configured to send by default an empty request. 解决的第一个问题： .Net平台默认配置为发送空请求。 The first attempt failed so .Net was forced to automatically send a second request with authentication. 第一次尝试失败，因此.Net被迫自动发送带有身份验证的第二个请求。 So i figured out 2 requests before the Jboss response formed an http 400 error. 因此，在Jboss响应形成http 400错误之前，我找出了2个请求。

Second Problem solved: After the other side solved thise previous problem configuring .Net properly, we tested again and the results were conclusive that no more requests was hitting Apache Http Server. 解决了第二个问题： 在另一端解决了先前配置.Net的先前问题之后，我们再次进行了测试，结果是没有更多的请求到达Apache Http Server。 - So there was a strong signal that we had something blocking this specific service. -因此，有一个强烈的信号表明我们有某些东西阻止了这项特定服务。 With the rocks in my hand, infrastructure people started to move their asses and somehow solved the problem. 有了我手中的石头，基础设施人员开始移动驴子，并以某种方式解决了问题。 Mine frustration in the end is that they didn't said nothing about the possible correction. 最终，我的挫败感是他们没有对可能的纠正说任何话。 So "suddenly" the communication was restored.. 因此“突然”恢复了通讯。

So after all we made it! 所以毕竟我们做到了！ but with a bitter taste of defeat. 但带着失败的痛苦。 Thank you all that supported me in this problem. 谢谢所有支持我解决这个问题的人。 []s []中