Bug#272799: marked as done (RewriteRules in Server Config Context)
Your message dated Thu, 27 Sep 2007 21:01:00 +0200
with message-id <200709272101.00784.sf@sfritsch.de>
and subject line bug #272799: RewriteRules in Server Config Context
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: apache2
Version: 2.0.51-2
The Apache 2 mod_rewrite reference claims RewriteEngine
(http://httpd.apache.org/docs-2.0/mod/mod_rewrite.html#rewriteengine) &
RewriteRule
(http://httpd.apache.org/docs-2.0/mod/mod_rewrite.html#rewriterule)
directives work in server config, virtual host, directory, & .htaccess
contexts; however, I observe they don't seem to work in the server
config context.
I'm running apache2-mpm-prefork 2.0.51-2.
These two lines have an effect from in a virtual host or .htaccess
context:
RewriteEngine on
RewriteRule foo /bar
but no effect from in a server config context.
My goal is to get cgiwrap working by including this file in the server
configuration: http://www.sfu.ca/~jdbates/cgiwrap/httpd.conf This file
is from the Debian cgiwrap package.
Thanks!
Jack
--- End Message ---
--- Begin Message ---
Version: 2.2.3-4
> The Apache 2 mod_rewrite reference claims RewriteEngine
> & RewriteRule
> directives work in server config, virtual host, directory,
> & .htaccess contexts; however, I observe they don't seem to work in
> the server config context.
This is the intended behaviour. Virtual hosts will not inherit the
rewrite config from the main server context unless you specify
RewriteEngine On
RewriteOptions Inherit
in every virtual host. In 2.2, this is documented (but it is not so
obvious in the 2.0 documentation).
--- End Message ---
Reply to: