libapache2-mod-rpaf 0.6.9 doesn't work well in combination with deny/allow operators

Bug #1191076 reported by Dmitry Sherman
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
libapache2-mod-rpaf (Ubuntu)
Confirmed
Undecided
Sergey B Kirpichev

Bug Description

On Ubuntu release 13.04 which comes with libapache2-mod-rpaf 0.6-9 there is an unexpected behavior of the combination of libapache2-mod-rpaf and the order allow/deny operators.

How to reproduce:
create .htaccess file with the following set:
<Limit GET POST PUT>
order deny,allow
deny from all
allow from 5.5.5.5
</Limit>

Enable mod_rpaf and set your proxies ips.
Put the apache behind a reverse proxy and surf the protected url from 5.5.5.5,
you will receive the following error in the error log:

[error] [client 5.5.5.5] client denied by server configuration: /path/to/protected/file/or/folder

Although the correct client IP shown in the error log, seems like Apaches initiates the access list policy check before mod_rpaf fires.

Makes the system unusable.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in libapache2-mod-rpaf (Ubuntu):
status: New → Confirmed
Revision history for this message
Sergey B Kirpichev (skirpichev) wrote :

See this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726529

Does this solve your problem?

Changed in libapache2-mod-rpaf (Ubuntu):
assignee: nobody → Sergey B Kirpichev (skirpichev)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.