httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 27542] New: - multiple-homed Web hosts - con refused to first IP doesn't fall through to second
Date Tue, 09 Mar 2004 15:29:54 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=27542>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=27542

multiple-homed Web hosts - con refused to first IP doesn't fall through to second

           Summary: multiple-homed Web hosts - con refused to first IP
                    doesn't fall through to second
           Product: Apache httpd-1.3
           Version: 1.3.29
          Platform: PC
               URL: http://archive.apache.org/gnats/304
        OS/Version: FreeBSD
            Status: NEW
          Severity: Major
          Priority: Other
         Component: mod_rewrite
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: white@extrasy.net


This bug pretty much interconnects with the following one 
http://archive.apache.org/gnats/304, although, it's dated 1997 and marked as 
fixed.

There is a problem with mod_proxy when it tries to connect (forward, internal 
proxy) to the domain name, which points to several IP addresses.  Technically, 
it appears when I'm trying to use mod_rewrite RewriteRule with the internal 
proxying facility.  I am still not very sure who's an originator of the 
problem, mod_rewrite or mod_proxy.

Eg. I'm using the mod_rewrite with [proxy|P] directive to have the internal 
proxying for the specific address to http://www.domain.com/. But the domain 
http://www.domain.com/ points to several IP addresses, which is used for fail-
over and (or?) some kind of load-balancing, eg.:

www.domain.com. IN A 10.0.10.1
                IN A 10.0.10.2
                IN A 10.0.10.3

Some of IPs generate connection reset, and supposedly mod_proxy should try 
another IP address to connect. Unfortunetly, it does not this, and if it 
recieves connection reset before the correct answer (eg. it tried broken 
address before the working one) mod_proxy just hangs up with the nasty 502 
error like this one:

Proxy Error
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /test/1231.

Reason: Could not connect to remote machine: Invalid argument

and the log file says:

[Tue Mar 9 06:30:25 2004] [error] [client 1.2.59.190] (22)Invalid argument: 
proxy connect to 10.0.10.1 port 80 failed

Likely, IE, Squid and a lot of different browsers and proxies handle this 
situation just fine, but not mod_proxy. Yes, I am aware that this is not RFC-
documented way of handling such situation, but looks pretty reasonable.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message