.noPrint {display: none;} td#mainBody {width: 100%;}

      The Apache Tomcat Servlet/JSP Container

Apache Tomcat 7

Version 7.0.70, Jun 15 2016
Apache Logo

Default Servlet Reference

The default servlet is the servlet which serves static resources as well as serves the directory listings (if directory listings are enabled).

It is declared globally in $CATALINA_BASE/conf/web.xml. By default here is it's declaration:



So by default, the default servlet is loaded at webapp startup and directory listings are disabled and debugging is turned off.

The DefaultServlet allows the following initParamters:

Debugging level. It is not very useful unless you are a tomcat developer. As of this writing, useful values are 0, 1, 11, 1000. [0]
If no welcome file is present, can a directory listing be shown? value may be true or false [false]
Welcome files are part of the servlet api.
WARNING: Listings of directories containing many entries are expensive. Multiple requests for large directory listings can consume significant proportions of server resources.
If a directory listing is presented, a readme file may also be presented with the listing. This file is inserted as is so it may contain HTML.
If you wish to customize your directory listing, you can use an XSL transformation. This value is a relative file name (to either $CATALINA_BASE/conf/ or $CATALINA_HOME/conf/) which will be used for all directory listings. This can be overridden per context and/or per directory. See contextXsltFile and localXsltFile below. The format of the xml is shown below.
You may also customize your directory listing by context by configuring contextXsltFile. This must be a context relative path (e.g.: /path/to/context.xslt) to a file with a .xsl or .xslt extension. This overrides globalXsltFile. If this value is present but a file does not exist, then globalXsltFile will be used. If globalXsltFile does not exist, then the default directory listing will be shown.
You may also customize your directory listing by directory by configuring localXsltFile. This must be a file in the directory where the listing will take place to with a .xsl or .xslt extension. This overrides globalXsltFile and contextXsltFile. If this value is present but a file does not exist, then contextXsltFile will be used. If contextXsltFile does not exist, then globalXsltFile will be used. If globalXsltFile does not exist, then the default directory listing will be shown.
Input buffer size (in bytes) when reading resources to be served. [2048]
Output buffer size (in bytes) when writing resources to be served. [2048]
Is this context "read only", so HTTP commands like PUT and DELETE are rejected? [true]
File encoding to be used when reading static resources. [platform default]
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]
If true, the Accept-Ranges header will be set when appropriate for the response. [true]
Should server information be presented in the response sent to clients when directory listing is enabled. [true]

You can override DefaultServlet with you own implementation and use that in your web.xml declaration. If you can understand what was just said, we will assume you can read the code to DefaultServlet servlet and make the appropriate adjustments. (If not, then that method isn't for you)

You can use either localXsltFile or globalXsltFile and DefaultServlet will create an xml document and run it through an xsl transformation based on the values provided in localXsltFile and globalXsltFile. localXsltFile is first checked, followed by globalXsltFile, then default behaviors takes place.


      <entry type='file|dir' urlPath='aPath' size='###' date='gmt date'>
      <entry type='file|dir' urlPath='aPath' size='###' date='gmt date'>
  • size will be missing if type='dir'
  • Readme is a CDATA entry
  • The following is a sample xsl file which mimics the default tomcat behavior:

    <?xml version="1.0" encoding="UTF-8"?>
    <xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
      <xsl:output method="html" html-version="5.0"
        encoding="UTF-8" indent="no"
      <xsl:template match="listing">
            Sample Directory Listing For
            <xsl:value-of select="@directory"/>
            h1 {color : white;background-color : #0086b2;}
            h3 {color : white;background-color : #0086b2;}
            body {font-family : sans-serif,Arial,Tahoma;
                 color : black;background-color : white;}
            b {color : white;background-color : #0086b2;}
            a {color : black;} HR{color : #0086b2;}
            table td { padding: 5px; }
          <h1>Sample Directory Listing For
                <xsl:value-of select="@directory"/>
          <hr style="height: 1px;" />
          <table style="width: 100%;">
              <th style="text-align: left;">Filename</th>
              <th style="text-align: center;">Size</th>
              <th style="text-align: right;">Last Modified</th>
            <xsl:apply-templates select="entries"/>
          <xsl:apply-templates select="readme"/>
          <hr style="height: 1px;" />
          <h3>Apache Tomcat/8.0</h3>
      <xsl:template match="entries">
        <xsl:apply-templates select="entry"/>
      <xsl:template match="readme">
        <hr style="height: 1px;" />
      <xsl:template match="entry">
          <td style="text-align: left;">
            <xsl:variable name="urlPath" select="@urlPath"/>
            <a href="|$vsmQbui}">
          <td style="text-align: right;">
            <pre><xsl:value-of select="@size"/></pre>
          <td style="text-align: right;">
            <pre><xsl:value-of select="@date"/></pre>
    Use web.xml in each individual webapp. See the security section of the Servlet specification.

    Notice: This comments section collects your suggestions on improving documentation for Apache Tomcat.

    If you have trouble and need help, read Find Help page and ask your question on the tomcat-users mailing list. Do not ask such questions here. This is not a Q&A section.

    The Apache Comments System is explained here. Comments may be removed by our moderators if they are either implemented or considered invalid/off-topic.

    Copyright © 1999-2016, Apache Software Foundation