Moreover if you look at mod_cgi.c:818, if the script's name starts with 'nph-' it'll cheat at internally remove all the protocol filters which mess with headers letting the script do its own thing.
ugh
If assbackwards is the designed solution for non-parsed headers, I wonder why mod_cgi doesn't use it. May be to optimize things?
The problem is that this doesn't work for registry scripts striving to be compatible with mod_cgi, i.e. run unmodified.
Therefore I thought of two posible solutions:
1) Introduce a new option:
PerlOptions +NonParseHeaders
which will do just that, call: $r->assbackwards(1) at the beginning of the response phase.
sure. just remember that that only supresses outgoing headers - it doesn't do anything to incoming headers or make the outgoing ones invisible. I'm never sure exactly what nph scripts do, but if there is more to the mod_cgi implementation than supressing outgoing headers we probably need to evaluate exactly what it is first.
It looks that's what mod_cgi does. We could do the same as mod_cgi instead of setting assbackwards. May be we should ask at httpd-dev?
__________________________________________________________________ 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]
