Bug 42373

Summary: REPORT request fails over mod_proxy
Product: Apache httpd-2 Reporter: Marcin Mikolajczak <memfis>
Component: mod_proxyAssignee: Apache HTTPD Bugs Mailing List <bugs>
Severity: major Keywords: MassUpdate
Priority: P2    
Version: 2.2.3   
Target Milestone: ---   
Hardware: All   
OS: Linux   

Description Marcin Mikolajczak 2007-05-09 15:14:48 UTC
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/

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

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 -

The same problem is described here, only the setup is based on Apache 2.0 and 
involes SSL:
Comment 1 Nick Kew 2007-09-09 09:54:48 UTC
I just tried proxying a (dummy) REPORT request, and it worked fine for me.  Can
you retry with 2.2.6?  And did you try posting to users@httpd to see if you
might have a configuration problem?
Comment 2 Marcin Mikolajczak 2007-09-10 12:50:53 UTC
(In reply to comment #1)
> I just tried proxying a (dummy) REPORT request, and it worked fine for me.  
> you retry with 2.2.6?  And did you try posting to users@httpd to see if you
> might have a configuration problem?

How do I issue a dummy REPORT request? What tool can I use for that purpose? 
The problem still exists on 2.2.6. If there is no possible reason why this 
shouldn't work I can ask on the users list - which I haven't done yet since all 
other types of requests seem to work fine.
Comment 3 William A. Rowe Jr. 2018-11-07 21:08:52 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.