How to disable the Directory Listings in Jboss/Tomcat bunndle.usualy this can be done in web.xml .
Isany specific setting is available in jboss/Tomcat bundle?
In Jetty and Tomcat bundled with JBoss, the respective configuration files still apply. These are server/instance/deploy/jbossweb-jetty.sar/webdefault.xml and server/instance/deploy/jbossweb-jetty.sar/web.xml respectively.
In the Jetty configuration (webdefault.xml), look at the line:
If true, and index.jsp, index.html or index.htm do not exist in the directory, the listing will be shown.
In the Tomcat configuration (web.xml), look for the line:
Set it according to your needs.
I have been using JBoss 2.4.4 bundled with Tomcat 4.0.1 and have been able to browse directories that are symbolic links. I am now migrating to JBoss 3.2.1 with Tomcat 4.1.24 and have found that I can no longer access the symbolic linked directories. Is there a configuration parameter to allow this like the Apache FollowSymLinks option?
Thanks for any help.
After some investigation I have found the following details on how to enable following of symbolic links in tomcat:
The problem is that it refers to settings in the server.xml file which is not present in the Jboss - Tomcat bundle. Where can I set these properties?
Have a look at the server/instance/deploy/jbossweb-tomcat.sar/META-INF/jboss-service.xml. It may also be located in a SAR called jbossweb-tomcat41.sar apparently.
Normally, this would be implemented like this.
<!-- Default context parameters -->
However, I do not think that JBoss currently provides rules to support these elements - I don't remember seeing them in the relevant parts of the source. They are also not contained in the DTD.
The SAX parser will check the XML elements and report that there are no rules to support Context or Resources in server.log if you have DEBUG as your log limit. There may be issues of managing deployment as JBoss is in control of part of this process at least, and this would probably be the reason it is not implemented. Perhaps this might change in the future.
The other thing to note is that this feature was disabled by default in Tomcat because of security concerns.
Thanks for the prompt reply!
I have tried your recommendation, and like you said, it does not look to be supported in the current version. Do you have any idea when this feature would be supported?
I'm not sure there are any plans to support this. There may be plumbing issues that prevent it. I suppose you could log a request at the JBoss SourceForge site.