www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Ramirez <jrami...@securesystems.org>
Subject mod_proxy/5544: invalid argument or connection refused errors with mod_proxy
Date Thu, 06 Jan 2000 19:38:09 GMT

>Number:         5544
>Category:       mod_proxy
>Synopsis:       invalid argument or connection refused errors with mod_proxy
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jan  6 11:40:00 PST 2000
>Last-Modified:
>Originator:     jramirez@securesystems.org
>Organization:
apache
>Release:        1.3.9
>Environment:
FreeBSD 3.4-RELEASE i386
>Description:
We are using Apache for a proxy only server with nothing else running on the mentioned machine.
 Examples of the client screen and configs are as follows:

Client Sees:
Proxy Error

The proxy server received an invalid response from an upstream server.

The proxy server could not handle the request
GET
http://adforce.ads.imgis.com/?addyn|2.0|202|104164|1|1|KEY=key1+key2+key3+key4;loc=700;.

Reason: Could not connect to remote machine: Connection refused

Apache/1.3.9 Server at proxy.company.com Port 80

***** If you hit reload a couple of times, it will finally load.

The error log looks like this...
proxy connect to 206.58.83.100 port 80 failed
[Wed Jan  5 16:32:33 2000] [error] [client 200.8.8.122] (61)Connection
refused:proxy connect to 209.67.245.75 port 80 failed
[Wed Jan  5 16:32:56 2000] [error] [client 200.8.8.122] (61)Connection
refused:proxy connect to 209.67.228.57 port 80 failed
[Wed Jan  5 16:32:56 2000] [error] [client 200.8.8.122] (22)Invalid
argument: proxy connect to 206.79.171.51 port 80 failed
[Wed Jan  5 16:32:56 2000] [error] [client 200.8.8.122] (22)Invalid
argument: proxy connect to 206.79.171.54 port 80 failed

****** For your reference, our proxy directives are as follows:

<IfModule mod_proxy.c>
ProxyRequests On
#
<Directory proxy:*>
        Order deny,allow
    Deny from all
    Allow from .company.com
</Directory>

#
# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via:
headers)
# Set to one of: Off | On | Full | Block
#
ProxyVia Block

#
# To enable the cache as well, edit and uncomment the following lines:
# (no cacheing without CacheRoot)
#
CacheRoot "/some/local/directory/proxy"
CacheSize 10000
CacheGcInterval 4
CacheMaxExpire 24
CacheLastModifiedFactor 0.1
CacheDefaultExpire 1
#NoCache a_domain.com another_domain.edu joes.garage_sale.com

</IfModule>
# End of proxy directives.
>How-To-Repeat:
Any website that uses multiple IPs for load balancing.  Ie. weather.com, yahoo.com, etc. 
It looks like it will not try a second, third, etc. address if the first one fails.
>Fix:
This looks exactly like PR#3217 though there was no resolution visible and it was running
under a different rev.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]




Mime
View raw message