I agree entirely, as the documentation says, rewrite rules are "voodoo" and often very hard to understand what's going on and why a given ruleset isn't working as expected (which is not the same as an error in the errorlog, more of a user error). The inability to trace through what it's doing in the rewritelog would have made many of my past interesting rulesets impossible to create. Taking it out of production sites is a great optimization, but definitely not a good thing for site development.
Dave On Fri, 1 Aug 2003 22:55:31 +0100 Thom May <[EMAIL PROTECTED]> wrote: > * Justin Erenkrantz ([EMAIL PROTECTED]) wrote : > > I'd support removing RewriteLog entirely in 2.1. > > > -1 ; As Mads says, RewriteLog is used for debugging only, > not for day-to-day > logging. This is why Andre proposed the patch, on the > basis that production > sites can remove the functionality entirely, but dev > sites that need to know > what the hell the module is doing can still work it out. > Removing RewriteLog entirely would make life a living > hell. > -Thom
