Stas Bekman wrote:
Geoffrey Young wrote:
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?
perhaps. or perhaps assbackwards isn't really all that designed (as in a designed public API :)
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?
well, I haven't looked at the mod_cgi code yet, but if the end result for nph scripts is the same as merely setting r->assbackwards = 1, then yes, I'd be interested in hearing what httpd-dev has so say about the different approaches.
maybe you'll even get an answer ;)
--Geoff
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
