>Number: 2422
>Category: mod_proxy
>Synopsis: ProxyPassReverse causes endless loop when Proxying "/"
>directory
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: apache
>State: open
>Class: sw-bug
>Submitter-Id: apache
>Arrival-Date: Thu Jun 11 14:20:00 PDT 1998
>Last-Modified:
>Originator: [EMAIL PROTECTED]
>Organization:
apache
>Release: 1.3.0
>Environment:
Running Linux 2.0.33 with gcc 2.7.2.1
>Description:
I'm using apache as a fancy http firewall proxy. Outside world accesses my
site via www.listworks.com and gets to firewall. Apache redirects all accesses
to my internal NT Server 4.0 IIS server (not accessible from outside the
firewall). I use the following configuration:
ProxyPass / http://<internal server>.listworks.com/postoffice
ProxyPassReverse / http://<internal server>.listworks.com/postoffice
The first part, ProxyPass, works properly. However, when I use it by itself,
the user can't follow any links within the site (they all reference <internal
server>, which as I said, isn't accessible outside the firewall). When I
include the ProxyPassReverse directive, the apache server goes into an endless
loop, and I receive the following over and over in the access_log file until I
kill apache:
ehrpc.listworks.com - - [11/Jun/1998:17:08:19 -0400] "GET / HTTP/1.1" 302 154
ehrpc.listworks.com - - [11/Jun/1998:17:08:19 -0400] "GET // HTTP/1.1" 302 154
ehrpc.listworks.com - - [11/Jun/1998:17:08:19 -0400] "GET // HTTP/1.1" 302 154
ehrpc.listworks.com - - [11/Jun/1998:17:08:19 -0400] "GET // HTTP/1.1" 302 154
ehrpc.listworks.com - - [11/Jun/1998:17:08:19 -0400] "GET // HTTP/1.1" 302 154
ehrpc.listworks.com - - [11/Jun/1998:17:08:19 -0400] "GET // HTTP/1.1" 302 154
<etc>
Notice that the first item is slightly different -- "/" vs. "//".
Also note that it works perfectly as long as the directory being proxied is not
"/". I tried it with a sub-directory and it worked fine.
My web site can't get out until this is fixed... Please help!! TIA
>How-To-Repeat:
Just set up a ProxyPass / ... and a ProxyPassReverse / ...
>Fix:
No -- sorry.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED. This is not done]
[automatically because of the potential for mail loops. ]
