httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 53963] New: RewriteBase inherited now?
Date Thu, 04 Oct 2012 11:07:52 GMT

          Priority: P2
            Bug ID: 53963
           Summary: RewriteBase inherited now?
          Severity: normal
    Classification: Unclassified
                OS: All
          Hardware: PC
            Status: NEW
           Version: 2.2.23
         Component: mod_rewrite
           Product: Apache httpd-2

Created attachment 29445
necessary files to reproduce the problem in zip arch

I have a site with gzipped css files. They are given to the client, depending
on Accept-encoding header. 

> cat .htaccess    
RewriteEngine On
RewriteBase /

> cat css/.htaccess 
RewriteEngine On
### RewriteBase /css/
RewriteCond %{HTTP:Accept-encoding} gzip
RewriteCond %{REQUEST_FILENAME}.gz -f
RewriteRule ^(.*)$ $1.gz [QSA,L]

> ls -a css/
.htaccess site.css site.css.gz

After update from 2.2.22 to 2.2.23 this mechanism has broken.

Test case in attachment. Test URL:
I got error "The requested URL /site.css.gz was not found on this server."
instead of  css/site.css.gz file content. Note the string "URL /site.css.gz" -
looks like apache missing directory "css" from the path.

If I remove "RewriteBase /" from parent .htaccess, I get gzipped css file. Or,
if I add string "RewriteBase /css/" into ./css/.htaccess, I get gzipped css
file. So it looks like "RewriteBase /" is inherited now from top .htaccess.

When I did rollback to 2.2.22 everything became ok.

Is it bug or is it feature?

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message