+1 I think Apache uses a 301 too.
The main reason for 301 was the problem of relative hrefs - if you have a request for /examples and you do an internal redirect to index.html, then <a href="foo"> will go to /foo instead of /examples/foo. AFAIK there is no good reason to not do an internal redirect for /examples/. Except beeing extra-safe about jsps who may use pathInfo or have strange bugs - but that's their problem, since the spec doesn't say anything. As long as you leave it off by default, and you deal with /examples and href - I think it's ok. Costin On Mon, 6 May 2002, Bill Barker wrote: > I've finally managed to patch StaticInterceptor to be able to process > Welcome Files via an internal sub-request rather than the current 301 > external redirect. > > I'm proposing to add this as an option to StaticInterceptor (off by default, > since the 2.2 spec is so vague on what it should do [but it should pass > 2.3]). It passes all but 3 Watchdog tests (all of which are expecting a 301 > redirect). > > Opinions, Comments, Flames, welcome. > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
