* [EMAIL PROTECTED] wrote: > yep. too bad there are so many places in the code where this problem > appears. i feel like we ought to take the opposite approach and guarantee > that r->filename is never NULL, but oh well. we've gone down this path > instead, so this is clearly a correct fix.
Note that this happens, because mod_include is a filter, added by type text/html in global server context. The error condition is very specific, say, 400 Response for malformed Host header, which appears to be a text/html response. What would r->filename be in this case? IMHO this is totally besides the r->filename should not be NULL problem, isn't it? nd
