mod_rewrite/9147: DB conflict between mod_auth_db and mod_rewrite

[Ethan Joffe <et...@toolfoundry.com>]

>Number:         9147
>Category:       mod_rewrite
>Synopsis:       DB conflict between mod_auth_db and mod_rewrite
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Dec 16 08:30:01 PST 2001
>Closed-Date:
>Last-Modified:
>Originator:     ethan@toolfoundry.com
>Release:        1.3.22
>Organization:
apache
>Environment:
Redhat 7.1 fresh install with all dev rpms.
>Description:

>From a fresh Linux install (or non fresh if you like), if you compile apache 
with mod_auth_db, you can create a Berkeley DB3 .db file with some username/password (I use
Perl compiled with Berkeley DB3), and have a .htaccess file point to it
and everything works fine. However if you compile apache with mod_auth_db and 
mod_rewrite, apache no longer authorizes the same users.
>How-To-Repeat:
With Berkeley DB3 installed (this is default with dev rpms on redhat 7.1), create
a .db access file (I use a perl script to do this) with a username/password.
Compile apache with mod_auth_db and create a .htaccess file that points to the
.db file, and confirm that you can correctly access the protected directory.
Now recompile apache with both mod_auth_db and mod_rewrite, and try to access
the same directory, and it will deny access.
>Fix:
no
>Release-Note:
>Audit-Trail:
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <ap...@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]