httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Spil Oss" <spil....@googlemail.com>
Subject [users@httpd] Handler for proxy-server returned invalid result code 730060
Date Wed, 11 Jun 2008 14:43:42 GMT
Hi All,

On our reverse-proxy setup (Client <-firewall-> DMZ1 Proxy
<-firewall-> DMZ2 Proxy <-firewall-> http-server) we are getting
spurious errors on
DMZ1 proxies. DMZ1 handles the ssl-termination, so only ssl between
client and DMZ1

in DMZ1 error.log
[Wed Jun 11 08:23:01 2008] [error] (OS 10060)A connection attempt
failed because the connected party did not properly respond after a
period of time, or established connection failed because connected
host has failed to respond.  : proxy: prefetch request body failed to
a.b.c.d:zzz (hostname) from e.f.g.h ()
[Wed Jun 11 08:23:01 2008] [error] [client 000.000.000.000] Handler
for proxy-server returned invalid result code 730060, referer:
https://hostname/somelongurl/Application.do?id=0
in DMZ2 access.log (from same originating IP)
e.f.g.h - - [11/Jun/2008:08:22:52 +0200] "POST
/somelongurl/Application.do?id=0 HTTP/1.1" 200 12709
e.f.g.h - - [11/Jun/2008:08:18:01 +0200] "POST
/somelongurl/Application.do?id=0 HTTP/1.1" 500 1091
e.f.g.h - - [11/Jun/2008:08:23:07 +0200] "POST
/somelongurl/Application.do?id=0 HTTP/1.1" 200 11765
the error seems to be the result of the second request in access.log
and has a delay of 5 minutes (ProxyTimeout and TimeIOut default to
300)

Since I saw numerous entries in the 2.2.8 changelog related to
mod_proxy* I upgraded DMZ1 from 2.2.6 to 2.2.8 and DMZ2 from 2.2.4 to
2.2.8 last weekend (running on Win2k3). There seem to be fewer errors,
but they still occur.
Searching the mailinglist and bug-database did not return anything
useful for me other than 31759. From where the error is logged (DMZ1)
my assumption is that this problem occurs in communication between 2
apache servers.
As both DMZ1 and DMZ2 are both Apache I did not wish to implement the
force-proxy-request-1.0 and proxy-nokeepalive protocol adjustments for
'/buggyappserver/' as listed in
http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#envsettings
Errors between DMZ2 and webserver probably fall under the
'buggyappserver' so I'll be implementing the force-proxy-request-1.0
and proxy-nokeepalive there.

Anybody have any suggestions?

Kind regards,

Spil.

---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org


Mime
View raw message