配置Tomcat直接显示目录结构和文件列表

Tomcat是直接显示目录结构和文件列表，只是在配置里面给关闭了。 
关键在这里：confweb.xml 

这个文件有一段配置直接控制Tomcat是允许显示目录结构和文件列表。 

<servlet>
    <servlet-name>default</servlet-name>
    <servlet-class>org.apache.catalina.servlets.DefaultServlet</servlet-class>
    <init-param>
        <param-name>debug</param-name>
        <param-value>0</param-value>
    </init-param>
    <init-param>
        <param-name>listings</param-name>
        <param-value>false</param-value>
    </init-param>
    <load-on-startup>1</load-on-startup>
</servlet>

把listings选项改为true就可以了。 另外把<welcome-file>的配置去掉

例子

org.apache.catalina.servlets.DefaultServlet支持许多配置选项，在这个web.xml文件里面都有注释。 

<!-- The default servlet for all web applications, that serves static     -->
 <!-- resources.  It processes all requests that are not mapped to other   -->
 <!-- servlets with servlet mappings (defined either here or in your own   -->
 <!-- web.xml file.  This servlet supports the following initialization    -->
 <!-- parameters (default values are in square brackets):                  -->
 <!--                                                                      -->
 <!--   debug               Debugging detail level for messages logged     -->
 <!--                       by this servlet.  [0]                          -->
 <!--                                                                      -->
 <!--   fileEncoding        Encoding to be used to read static resources   -->
 <!--                       [platform default]                             -->
 <!--                                                                      -->
 <!--   input               Input buffer size (in bytes) when reading      -->
 <!--                       resources to be served.  [2048]                -->
 <!--                                                                      -->
 <!--   listings            Should directory listings be produced if there -->
 <!--                       is no welcome file in this directory?  [false] -->
 <!--                       WARNING: Listings for directories with many    -->
 <!--                       entries can be slow and may consume            -->
 <!--                       significant proportions of server resources.   -->
 <!--                                                                      -->
 <!--   output              Output buffer size (in bytes) when writing     -->
 <!--                       resources to be served.  [2048]                -->
 <!--                                                                      -->
 <!--   readonly            Is this context "read only", so HTTP           -->
 <!--                       commands like PUT and DELETE are               -->
 <!--                       rejected?  [true]                              -->
 <!--                                                                      -->
 <!--   readmeFile          File name to display with the directory        -->
 <!--                       contents. [null]                               -->
 <!--                                                                      -->
 <!--   sendfileSize        If the connector used supports sendfile, this  -->
 <!--                       represents the minimal file size in KB for     -->
 <!--                       which sendfile will be used. Use a negative    -->
 <!--                       value to always disable sendfile.  [48]        -->
 <!--                                                                      -->
 <!--   useAcceptRanges     Should the Accept-Ranges header be included    -->
 <!--                       in responses where appropriate? [true]         -->
 <!--                                                                      -->
 <!--  For directory listing customization. Checks localXsltFile, then     -->
 <!--  globalXsltFile, then defaults to original behavior.                 -->
 <!--                                                                      -->
 <!--   localXsltFile       Make directory listings an XML doc and         -->
 <!--                       pass the result to this style sheet residing   -->
 <!--                       in that directory. This overrides              -->
 <!--                        globalXsltFile[null]                          -->
 <!--                                                                      -->
 <!--   globalXsltFile      Site wide configuration version of             -->
 <!--                       localXsltFile This argument is expected        -->
 <!--                       to be a physical file. [null]                  -->
 <!--                                                                      -->
 <!--