httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 12356] - [mod_rewrite] does not work in server-context (httpd.conf)
Date Mon, 09 Sep 2002 21:43:17 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12356>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12356

[mod_rewrite] does not work in server-context (httpd.conf)

slive@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From slive@apache.org  2002-09-09 21:43 -------
I'm not sure why you never followed-up on the thread in the mailing list.

If you had, I would have told you that, although I haven't looked in detail
at the related code, it is very likely that this is caused by the fact that
mod_setenvif does not actually set the environment variable until after
the RewriteRules have been applied.   Config file order is irrelevant.

In addition, it is rather silly to use SetEnvIf in combination with mod_rewrite
this way, because mod_rewrite can handle the whole thing itself.  Just replace
RewriteCond %{ENV... with
RewriteCond %{REMOTE_ADDR} ....
or, if you really want to set the env variable, RewriteRule can do that
with an [E=...] clause.

So, I think I will declare the configuration you are looking for "unsupported"
unless anyone wants to disagree with me.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message