[EMAIL PROTECTED] wrote:
Justin Erenkrantz wrote:
--On Tuesday, June 7, 2005 11:42 PM +0200 [EMAIL PROTECTED] wrote:
Sorry, if this is a stupid quickshot, but what about something like:
Nope, it's not stupid as that's about the only sane place I can think of
sticking it as well. The only catch is that if a handler exits this
way, it probably means that r->status isn't correct either. So, perhaps
we also set r->status explicitly in this additional code path. -- justin
Yes you are right I forgot this. So I think this would be better:
--- config.c.orig 2005-05-26 10:35:57.000000000 +0200
+++ config.c 2005-06-07 23:54:17.000000000 +0200
@@ -375,6 +375,18 @@ AP_CORE_DECLARE(int) ap_invoke_handler(r
"handler \"%s\" not found for: %s", r->handler, r->filename);
}
+ if (!r->eos_sent && (result != DECLINED)) {
I'm pondering if we shouldn't just abort() right here (wrap it in debug defines
maybe) and fix all the core modules.
OTOH, we can decide the modules aren't broken at all. Whatever we do will
require some documenting on what a module should and should not do.
Sander
