On Fri, 12 Mar 2010, Graham Leggett wrote:
I am currently having a torrid time trying to debug a mod_rewrite problem,
and my efforts have been thwarted by:
- mod_rewrite for some reason has it's own logging subsystem, instead of
using the standard httpd logging.
- mod_rewrite doesn't seem to support the concept of directive inheritance,
so the moment you specify "RewriteEngine on", any inherited config -
including your RewriteLog directive - gets blown out the window.
Someone suggested to make "RewriteEngine on" the default in 2.4. Would
that already help a bit? I would support that change. That is, if it has
not been done in trunk already.
What I propose is that we deprecate the RewriteLog directive, and replace all
logging functionality in mod_rewrite with standard httpd logging.
Would v2.4 be an acceptable time to introduce something like this?
+1, and in fact I wanted to do that by introducing additional log levels
that the rewrite log levels can be mapped to [1], and by allowing per
module log level configuration.
That change I have already working and I would really like to have it in
2.4. I will try to clean up the lastest version and post it here next
week.
Two additional nice to have features would be per dirctory log level
configuration and additional, per module log files that can have higher
log levels than the normal error log (i.e. dedicated debug log files). But
I didn't have much time to work on this so far and I am not sure at
all that it will get finished in time for 2.4.
[1]
http://mail-archives.apache.org/mod_mbox/httpd-dev/201002.mbox/<[email protected]>
