hi all
this escaped error_log is making it impossible to debug anything within the mod_perl test suite. I'd like to do something like the attached patch to make our lives (as well as the lives of our users) a bit easier. it may not be ideal, but it seems to make things better for me for the moment, and it doesn't involve pipes so it should be platform safe.
other approaches or ways to make it better are welcome.
I still want to see it solved on the Apache side. Any workarounds suck, because you unescape just a few things at the moment. Later you will want to extend this list. And it doesn't help non A-T users. And this practice is very questionable in terms of circumventing the security this change has been made for.
The particular problem with your patch is the slurp mode. Quite often I have enormous, up to 100MB error_log files. You don't want to slurp and rewrite them in memory. Even w/o the slurp issue it's also going to be quite slow.
I'm very unhappy about this change in Apache, but besides me everybody keeps quiet and doesn't complain/looking for solutions in the core of the problem, I won't be surprised that it'll stay that way.
If Apache doesn't remove this change, I'm thinking that we will provide an alternative implementation in mod_perl and have a compile time option which will choose Apache's implementation vs. ours (ours will be just a copy of Apache's core implementation before this change). How does this sound? Of course users should be aware of the potential risks if they choose ours.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
