https://bz.apache.org/bugzilla/show_bug.cgi?id=60458

            Bug ID: 60458
           Summary: ProxyPass in a Location block loops on local
                    ErrorDocument
           Product: Apache httpd-2
           Version: 2.4.23
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Hello,
(Finally :o) Upgrading from 2.2, I have either a regression or the same
"behavior change" as commented in
https://bz.apache.org/bugzilla/show_bug.cgi?id=54319.

Please update based on following details.

This conf is added to fresh 2.4.23 build with minimal set of modules ( mpm
worker )
# =======BEGIN
ErrorDocument 400 /error/unavailable
ErrorDocument 401 /error/empty
ErrorDocument 403 /error/forbidden
ErrorDocument 404 /error/unavailable

ProxyErrorOverride On
Alias /error "/tmp/error"
ProxyPass /error !

<Directory "/tmp/error">
 AllowOverride None
 Require all granted
</Directory>

ProxyPass / http://127.0.0.1:1234/
ProxyPassReverse / http://127.0.0.1:1234/
# ========= END

"Server" on 127.0.0.1:1234 responds with status 403, no body.
The configuration above works as expected.

If ProxyPass(Reverse) directives are in a Location block : (rest of
configuration unchanged)....
# =======BEGIN
 <Location />
     Require all granted
     ProxyPass http://127.0.0.1:1234/
     ProxyPassReverse http://127.0.0.1:1234/
 </Location>
# ========= END

... then an internal requests loop starts until LimitInternalRecursion (10) is
reached. Client receives latest 403 response, a status 500 is recorded in
access_log.

note : the same configuration (using Order+Allow instead of Require ) on a
fresh minimal build of 2.2.31 works as expected.

++
N'Alex.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to