httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Ionescu <>
Subject Re: [users@httpd] Semantics of "RewriteOptions inherit" in htaccess files needs improvement
Date Sun, 01 Feb 2009 22:19:48 GMT
2009/1/31 Matt McCutchen <>:
> #1. Currently, "RewriteOptions inherit" works as if the parent's rules
> were copied and pasted into the child (after any other rules).  This
> means that requests in the child directory are tested against the
> parent's rules after stripping the /child's/ RewriteBase.  Thus, the
> parent's rules have a different effect when inherited by "RewriteOptions
> inherit" compared to when the child has no mod_rewrite configuration at
> all, in which case they are tested after stripping the /parent's/
> RewriteBase.  I found this behavior surprising.

Mhmmm; actually, that's exactly what I'm using in environments where I
don't have access to the main server configuration. :-)
E.g. domain1 points to /var/www, domain2 to /var/www/sub and
/var/www/sub/.htaccess inherits (i.e. 1:1 copy) /var/www/.htaccess. A
regEx of ^foo$ in /var/www/sub/.htaccess would match against a
filename /var/www/foo and against /var/www/sub/foo in
/var/www/sub/.htaccess caused by inheriting, which is intended (the
per-dir prefix is striped prior matching, of course). The URL-path
(which doesn't matter in per-dir context for matching) would be in
both cases /foo while the domain is different.

Two different setups - two different intentions about overriding the
parent configuration and the inheritage of the rules.


The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:> for more info.
To unsubscribe, e-mail:
   "   from the digest:
For additional commands, e-mail:

View raw message