I think we agree, that DirectoryIndex should not replace the
welcome-file list on the Tomcat side.
This means at least: if non of the entries in the DirectoryIndex list is
visible by Apache, it should not try to prepend any of them to the URL
and send to Tomcat, even if this would match a JkMount. OK? For any of
the entries in the welcome-list it would suffice to send a directory
request forward.
Now a few cases are left over:
1) If Apache can see a file from DirectoryIndex, should it serve it
locally, or send it to Tomcat? The easy answer would be: serve it
locally in any case. As a consequence, when mixing dynamic and static
content one would need to use a different file name to distinguish the
two (or use a more elaborate per directory or location Apache config).
This doesn't sound too unreasonable.
The other option would be: send it to Tomcat, if it matches a JkMount.
In that case Apache manipulates a browser request and sends the
manipulated request to Tomcat. I tend to disagree with this option
2) If Apache can not see any file from DirectoryIndex. How should the
forwarding behaviour depend on JkMount and ForwardDirectories? If the
request matches a JkMount, it should definitely be forwarded. If it
doesn't match a JkMount, it doesn't sound very convincing to forward at
all. So I don't see a good use case for an option "ForwardDirectories".
Regards,
Rainer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
