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=42373>.
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=42373

           Summary: REPORT request fails over mod_proxy
           Product: Apache httpd-2
           Version: 2.2.3
          Platform: Other
        OS/Version: Linux
            Status: NEW
          Severity: major
          Priority: P2
         Component: mod_proxy
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


Something is wrong in the way REPORT requests are handled when issued against 
locations being proxied through mod_proxy. Such requests end up with 403 and 
the message "client denied by server configuration" in error_log. DebugLevel 
debug shows nothing of interest.

My test setup consists of a 2 Apache 2.2 servers:

a) "firewall server" with a few virtual hosts, each redirecting requests to a 
backend server through mod_proxy like this:

<VirtualHost *>
    ServerName svn.mydomain.com
    ProxyPreserveHost on
    ProxyPass / http://svn.internal.mydomain.com/
</VirtualHost>

<Proxy http://svn.internal.mydomain.com/>
    Allow from all
</Proxy>

b) svn server, running Apache 2.2 with mod_dav_svn

The second server works fine when queried directly.

The command used to issue REPORT requests against a repository is "svn status -
u".

The same problem is described here, only the setup is based on Apache 2.0 and 
involes SSL:
http://www.svnforum.org/2017/
viewtopic.php?t=3579&sid=4cdff59d87e67dc7926e6dec29d76041

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to