On 22 Jul 2002, Bojan Smojver wrote: > If there is no physical file, then nothing will get done by the patch at > all (since r->finfo.filetype is 0). It won't affect mod_dir's old > behaviour at all. I'm not sure how that changes things...
My question was: if you have a precompiled index.jsp, there will be no file - only a <servlet-map> with uri=/index.jsp and the servlet name. DirectoryIndex will not find index.jsp, and will assume there is no index - and serve the dir. Which is wrong. The indexes as defined by the servlet spec may be real files or virtual (mapped) resources. > I guess I was aiming at this: > > - if all files are physical and local, then mod_dir and DirectoryIndex > are fine and make sense If you can make sure that all paths are checked for both static and mapped resources - yes, you can use mod_dir. > - if all files are not physical and local, mod_dir and DirectoryIndex > don't make sense and should not be used I don't think this is an issue we should discuss - this case is already solved, if no files on the apache machine there is nothing we can do but forward. The lb case is also not an issue - if there are local static files, apache can serve them - and dynamic resources are handled by tomcat lb. Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
