Hmm, when I remove index.jsp then I get just a directory listing.
Concerning the mining, how should the structure be then? Where should DocumentRoot normaly point to?
I thought it works that way: 1) Take the pages from DocumentRoot 2) If it is *.jsp pass it to TC and TC will execute them 3) Otherwise Apache sends them directly
But it seams that Apache sends all directly, and if I dont have the DirectoryIndex with index.jsp it starts with a listing.
Thanks SB
Lutz Zetzsche wrote:
Hi Stanislav,
Stanislav Bauer schrieb:
In apaches httpd.conf I also added index.jsp to the DirectoryIndex.
oh, bad idea!
As Apache shouldn't serve jsp pages itself, you shouldn't instruct Apache to look for an index.jsp in case of a request like http://www.domain.com/dir/.
Remove index.jsp from the DirectoryIndex, reload Apache and have a look if your problem is solved then.
However, you should re-think your server configuration completely. I don't think that it is a good idea to mix Apache and Tomcat too much. There are several security implications. I.e. mis-configurations will allow the servers to access each other's sensitive configuration files. Tomcat may be able to read Apache's htaccess files, Apache may be able to read Tomcat's web.xml etc.
I don't know why you have pointed Apache's DocumentRoot to your Tomcat web application directory but if this is not necessary, you shouldn't do it.
Best wishes
Lutz
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
