>Number: 974 >Category: mod_proxy >Synopsis: ProxyRemote: "Could not connect to remote machine" >Confidential: no >Severity: critical >Priority: medium >Responsible: apache (Apache HTTP Project) >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Aug 7 05:40:02 1997 >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.a1 >Environment: Solaris 2.5.0 with gcc Apache 1.3.a1 >Description: Accessing a URL from an intranet via a ProxyRemote *sometimes* results in:
>>Proxy Error >> >>The proxy server could not handle this request. >> >>Reason: Could not connect to remote machine Errorlog shows [because of the firewall/remote Proxy]: >>[Fri Aug 1 16:52:11 1997] connect: Network is unreachable A trace of the local network traffic [snoop] shows, that the apache server wants to connect to the requested host **directly** and not via the remote proxy (firewall). The requested URLs can be accessed [?], after killing and restarting the httpd. Could this problem related to #PR510? One word to our configuration - it looks like: >ProxyRequests On >ProxyDomain .rexroth.de >NoProxy [some full qualified intranet ip-adresses, no netmasks] >NoProxy .rexroth.de >NoProxy mpoint.mannesmann.de # Firewall >ProxyRemote * http://proxy1.mannesmann.de:8080 Full DNS name resolution is on the apache server available. >How-To-Repeat: www.sun.com www.altavista.telia.com >Fix: >Audit-Trail: >Unformatted:
