In 1.3 mod_dir was a handler. Now it happens as an early internal_fast_redirect
in the fixup (?) phase.
What happens if nobody redirects [mod_dir failed]? Probably is falling
on the default handler.
This is fine if the default handler croaks [would that be NOT AUTHORIZED
or NOT FOUND?] The only way to get here is
. mod_dir finds nothing
. mod_autoindex isn't enabled/loaded.
If nobody cares until we hit the core handler, I suggest it must be NOT FOUND.
So your patch in the last post is right.
----- Original Message -----
From: "Jeff Trawick" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, January 28, 2002 7:54 PM
Subject: Re: [PATCH] default_handler tries to serve directories :)
> Jeff Trawick <[EMAIL PROTECTED]> writes:
>
> > I have a very minimal config file with no mod_autoindex that reacts
> > strangely to an HTTP 0.9 GET for /.
>
> For reasons I don't understand, a request from IE (configured for
> HTTP/1.1) to GET / is attempting to use all available paging space :)
> I'll try to understand that soon-ish.
>
> (That's without the patch posted previously.)
>
> > Here is a silly patch. For now I'm filtering out APR_DIR files.
> > WW1D? ("1" == "1.3")
>
> I don't see any code to filter out directories, but I must admit that
> I didn't try it with 1.3 to see what would happen.
>
> --
> Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
> http://www.geocities.com/SiliconValley/Park/9289/
> Born in Roswell... married an alien...
>
