in apache-1.3 it was possible to emulate nph (non-parsed headers) handlers by
simply disabling the headers parsing in the sent response. It no longer works
in httpd-2.0 that way.

Looking at mod_cgi.c, it plays it dirty and shortcuts the filters chain to
bypass any output filters that deal with response headers, letting nph-
scripts emit their own headers by printing them out.

Though there is r->assbackwards = 1, which is when set also allows handlers to
send their own headers by printing them out.

My question is: does using r->assbackwards is the right way to allow nph-
handlers in third party modules (mod_perl/mod_php/etc) or should we use the
mod_cgi.c's approach and rewire the filter chain.

In short, what's the approach is endorsed by httpd-dev.

Am I correct to understand that mod_cgi doesn't set r->assbackwards = 1, but
messes up with the filter chain in order to optimize things? Is it safe for us
to do the same and not be afraid that filter chains internals will change in
the future? (I think they must change in 2.1 at least because of the bug I've
reported long time ago, which makes it impossible to remove the connection
filter that links to the request filter chain, and the only way to fix it is
to change the way chains are linked to each other)

__________________________________________________________________
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



Reply via email to