<body>
<div id="page-header">
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
-<p class="apache">Apache HTTP Server Version 2.1</p>
+<p class="apache">Apache HTTP Server Version 2.3</p>
<img alt="" src="../images/feather.gif" /></div>
<div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
<div id="path">
-<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs
-project/">Documentation</a> > <a href="../">Version 2.1</a> > <a href="./">Modules</a></div>
+<a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs
/">Documentation</a> > <a href="../">Version 2.3</a> > <a href="./">Modules</a></div>
<div id="page-content">
<div id="preamble"><h1>Apache Module mod_mime</h1>
<div class="toplang">
<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_mime.c</td></tr></table>
<h3>Summary</h3>
- <p>This module is used to associate various bits of "meta
- information" with files by their filename extensions. This
- information relates the filename of the document to it's
- mime-type, language, character set and encoding. This
- information is sent to the browser, and participates in content
- negotiation, so the user's preferences are respected when
- choosing one of several possible files to serve. See
+ <p>This module is used to assign content metadata to the content
+ selected for an HTTP response by mapping patterns in the
+ URI or filenames to the metadata values. For example, the filename
+ extensions of content files often define the content's Internet
+ media type, language, character set, and content-encoding. This
+ information is sent in HTTP messages containing that content and
+ used in content negotiation when selecting alternatives, such that
+ the user's preferences are respected when choosing one of several
+ possible contents to serve. See
<code class="module"><a href="../mod/mod_negotiation.html">mod_negotiation</a></code> for more information
about <a href="../content-negotiation.html">content negotiation</a>.</p>
<p>The directives <code class="directive"><a href="#addcharset">AddCharset</a></code>, <code class="directive"><a href="#addencoding">AddEncoding</a></code>, <code class="directive"><a href="#addlanguage">AddLanguage</a></code> and <code class="directive"><a href="#addtype">AddType</a></code> are all used to map file
- extensions onto the meta-information for that file. Respectively
+ extensions onto the metadata for that file. Respectively
they set the character set, content-encoding, content-language,
- and
MIME-type (content-type) of documents. The directive <code class="directive"><a href="#typesconfig">TypesConfig</a></code> is used to specify a
- file which also maps extensions onto MIME types. </p>
+ and
<a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media-type</a> (content-type) of documents. The directive <code class="directive"><a href="#typesconfig">TypesConfig</a></code> is used to specify a
+ file which also maps extensions onto media types. </p>
<p>In addition, <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> may define the <a href="../handler.html">handler</a> and <a href="../filter.html">filters</a> that originate and process
content. The directives <code class="directive"><a href="#addhandler">AddHandler</a></code>, <code class="directive"><a href="#addoutputfilter">AddOutputFilter</a></code>, and <code class="directive"><a href="#addinputfilter">AddInputFilter</a></code> control the modules
<code class="module"><a href="../mod/mod_negotiation.html">mod_negotiation</a></code> to consider these file extensions
to be included when testing Multiviews matches.</p>
- <p>While <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> associates meta-information
+ <p>While <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> associates metadata
with filename extensions, the <code class="module"><a href="../mod/core.html">core</a></code> server
provides directives that are used to associate all the files in a
given container (<em>e.g.</em>, <code class="directive"><a href="../mod/core.html#location"><Location></a></code>, <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code>, or <code class="directive"><a href="../mod/core.html#files"><Files></a></code>) with particular
- meta
-information. These directives include <code class="directive"><a href="../mod/core.html#forcetype">ForceType</a></code>, <code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code>, <code class="directive"><a href="../mod/core.html#setinputfilter">SetInputFilter</a></code>, and <code class="directive"><a href="../mod/core.html#setoutputfilter">SetOutputFilter</a></code>. The core directives
+ meta
data. These directives include <code class="directive"><a href="../mod/core.html#forcetype">ForceType</a></code>, <code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code>, <code class="directive"><a href="../mod/core.html#setinputfilter">SetInputFilter</a></code>, and <code class="directive"><a href="../mod/core.html#setoutputfilter">SetOutputFilter</a></code>. The core directives
override any filename extension mappings defined in
<code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code>.</p>
- <p>Note that changing the meta-information for a file does not
+ <p>Note that changing the metadata for a file does not
change the value of the <code>Last-Modified</code> header.
Thus, previously cached copies may still be used by a client or
proxy, with the previous headers. If you change the
- meta-information (language, content type, character set or
+ metadata (language, content type, character set or
encoding) you may need to 'touch' affected files (updating
their last modified date) to ensure that all visitors are
receive the corrected content headers.</p>
<li><code class="directive"><a href="../mod/mod_mime_magic.html#mimemagicfile">MimeMagicFile</a></code></li>
<li><code class="directive"><a href="../mod/core.html#adddefaultcharset">AddDefaultCharset</a></code></li>
<li><code class="directive"><a href="../mod/core.html#forcetype">ForceType</a></code></li>
-<li><code class="directive"><a href="../mod/core.html#defaulttype">DefaultType</a></code></li>
<li><code class="directive"><a href="../mod/core.html#sethandler">SetHandler</a></code></li>
<li><code class="directive"><a href="../mod/core.html#setinputfilter">SetInputFilter</a></code></li>
<li><code class="directive"><a href="../mod/core.html#setoutputfilter">SetOutputFilter</a></code></li>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="multipleext" id="multipleext">Files with Multiple Extensions</a></h2>
- <p>Files can have more than one extension, and the order of the
+ <p>Files can have more than one extension; the order of the
extensions is <em>normally</em> irrelevant. For example, if the
file <code>welcome.html.fr</code> maps onto content type
<code>text/html</code> and language French then the file
- <code>welcome.fr.html</code> will map onto exactly the same information.
- If more than one extension is given which maps onto the same
- type of meta-information, then the one to the right will be
- used, except for languages and content encodings. For example, if
- <code>.gif</code> maps to the MIME-type <code>image/gif</code> and
- <code>.html</code> maps to the MIME-type <code>text/html</code>, then the
- file <code>welcome.gif.html</code> will be associated with the MIME-type
- <code>text/html</code>.</p>
+ <code>welcome.fr.html</code> will map onto exactly the same
+ information. If more than one extension is given that maps onto
+ the same type of metadata, then the one to the right will
+ be used, except for languages and content encodings. For example,
+ if <code>.gif</code> maps to the <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media-type</a>
+ <code>image/gif</code> and <code>.html</code> maps to the
+ media-type <code>text/html</code>, then the file
+ <code>welcome.gif.html</code> will be associated with the
+ media-type <code>text/html</code>.</p>
<p><a href="#charset-lang">Languages</a> and <a href="#contentencoding">content encodings</a> are treated accumulative, because one can assign
- more than one language or encoding to a particular ressource. For example,
+ more than one language or encoding to a particular resource. For example,
the file <code>welcome.html.en.de</code> will be delivered with
<code>Content-Language: en, de</code> and <code>Content-Type:
text/html</code>.</p>
<p>Care should be taken when a file with multiple extensions
- gets associated with both a MIME-type and a handler. This will
- usually result in the request being by the module associated
+ gets associated with both a <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media-type</a>
+ and a handler. This will
+ usually result in the request being handled by the module associated
with the handler. For example, if the <code>.imap</code>
extension is mapped to the handler <code>imap-file</code> (from
- <code class="module"><a href="../mod/mod_imap.html">mod_imap</a></code>) and the <code>.html</code> extension is
- mapped to the MIME-type <code>text/html</code>, then the file
+ <code class="module"><a href="../mod/mod_imagemap.html">mod_imagemap</a></code>) and the <code>.html</code> extension is
+ mapped to the media-type <code>text/html</code>, then the file
<code>world.imap.html</code> will be associated with both the
- <code>imap-file</code> handler and <code>text/html</code> MIME-type.
+ <code>imap-file</code> handler and <code>text/html</code> media-type.
When it is processed, the <code>imap-file</code> handler will be used,
- and so it will be treated as a <code class="module"><a href="../mod/mod_imap.html">mod_imap</a></code> imagemap
+ and so it will be treated as a <code class="module"><a href="../mod/mod_imagemap.html">mod_imagemap</a></code> imagemap
file.</p>
+
+ <p>If you would prefer only the last dot-separated part of the
+ filename to be mapped to a particular piece of meta-data, then do
+ not use the <code>Add*</code> directives. For example, if you wish
+ to have the file <code>foo.html.cgi</code> processed as a CGI
+ script, but not the file <code>bar.cgi.html</code>, then instead
+ of using <code>AddHandler cgi-script .cgi</code>, use</p>
+
+ <div class="example"><h3>Configure handler based on final extension only</h3><p><code>
+ <FilesMatch \.cgi$>
+ <span class="indent">
+ SetHandler cgi-script
+ </span>
+ </FilesMatch>
+ </code></p></div>
+
</div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="section">
<h2><a name="contentencoding" id="contentencoding">Content encoding</a></h2>
- <p>A file of a particular MIME type can additionally be encoded a
+ <p>A file of a particular <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media-type</a> can additionally be encoded a
particular way to simplify transmission over the Internet.
While this usually will refer to compression, such as
<code>gzip</code>, it can also refer to encryption, such a
<div class="example"><p><code>
Content-Language: en, fr<br />
- Content-Type: text/plain; charset=ISO-8859-1
+ Content-Type: text/plain; charset=ISO-8859-1
</code></p></div>
<p>The language specification is the two-letter abbreviation
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
<p>The <code class="directive">AddCharset</code> directive maps the given
- filename extensions to the specified content charset. <var>charset</var>
- is the MIME charset parameter of filenames containing
+ filename extensions to the specified content charset (the Internet
+ registered name for a given character encoding). <var>charset</var>
+ is the <a href="http://www.iana.org/assignments/character-sets">media
+ type's charset parameter</a> for resources with filenames containing
<var>extension</var>. This mapping is added to any already in force,
overriding any mappings that already exist for the same
<var>extension</var>.</p>
where the server returns one from several documents based on
the client's charset preference.</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
- be specified with or without a leading dot.</p>
+ <p>The <var>extension</var> argument is case-insensitive and can
+ be specified with or without a leading dot. Filenames may have <a href="#multipleext">multiple extensions</a> and the
+ <var>extension</var> argument will be compared against each of
+ them.</p>
+
<h3>See also</h3>
<ul>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Maps the given filename extensions to the specified encoding
type</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>AddEncoding <var>MIME-enc</var> <var>extension</var>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>AddEncoding <var>encoding</var> <var>extension</var>
[<var>extension</var>] ...</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
<p>The <code class="directive">AddEncoding</code> directive maps the given
- filename extensions to the specified encoding type. <var>MIME-enc</var>
- is the MIME encoding to use for documents containing the
+ filename extensions to the specified HTTP content-encoding.
+ <var>encoding</var> is the HTTP content coding to append to the
+ value of the Content-Encoding header field for documents named with the
<var>extension</var>. This mapping is added to any already in force,
overriding any mappings that already exist for the same
<var>extension</var>.</p>
<code>AddEncoding</code> directive. To make this long story
short, you should always use <code>x-gzip</code> and
<code>x-compress</code> for these two specific encodings. More
- recent encodings, such as <code>deflate</code> should be
+ recent encodings, such as <code>deflate</code>, should be
specified without the <code>x-</code>.</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
- be specified with or without a leading dot.</p>
+ <p>The <var>extension</var> argument is case-insensitive and can
+ be specified with or without a leading dot. Filenames may have <a href="#multipleext">multiple extensions</a> and the
+ <var>extension</var> argument will be compared against each of
+ them.</p>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<p>Once that has been put into your httpd.conf file, any file containing
the <code>.cgi</code> extension will be treated as a CGI program.</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
- be specified with or without a leading dot.</p>
+ <p>The <var>extension</var> argument is case-insensitive and can
+ be specified with or without a leading dot. Filenames may have <a href="#multipleext">multiple extensions</a> and the
+ <var>extension</var> argument will be compared against each of
+ them.</p>
<h3>See also</h3>
<ul>
directive. This mapping is merged over any already in force, overriding
any mappings that already exist for the same <var>extension</var>.</p>
- <p>If more than one filter is specified, they must be separated
+ <p>If more than one <var>filter</var> is specified, they must be separated
by semicolons in the order in which they should process the
- content. Both the filter and <var>extension</var> arguments are
- case-insensitive, and the extension may be specified with or
- without a leading dot.</p>
+ content. The <var>filter</var> is case-insensitive.</p>
+
+ <p>The <var>extension</var> argument is case-insensitive and can
+ be specified with or without a leading dot. Filenames may have <a href="#multipleext">multiple extensions</a> and the
+ <var>extension</var> argument will be compared against each of
+ them.</p>
+
<h3>See also</h3>
<ul>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Maps the given filename extension to the specified content
language</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>AddLanguage <var>MIME-lang</var> <var>extension</var>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>AddLanguage <var>language-tag</var> <var>extension</var>
[<var>extension</var>] ...</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
<p>The <code class="directive">AddLanguage</code> directive maps the given
- filename extension to the specified content language.
- <var>MIME-lang</var> is the MIME language of filenames containing
- <var>extension</var>. This mapping is added to any already in force,
- overriding any mappings that already exist for the same
+ filename extension to the specified content language. Files with the
+ filename <var>extension</var> are assigned an HTTP Content-Language
+ value of <var>language-tag</var> corresponding to the language
+ identifiers defined by RFC 3066.
+ This directive overrides any mappings that already exist for the same
<var>extension</var>.</p>
<div class="example"><h3>Example</h3><p><code>
<div class="example"><p><code>
AddLanguage en .en<br />
- AddLanguage en-uk .en<br />
+ AddLanguage en-gb .en<br />
AddLanguage en-us .en
</code></p></div>
<p>documents with the extension <code>.en</code> would be treated as
being <code>en-us</code>.</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
- be specified with or without a leading dot.</p>
+ <p>The <var>extension</var> argument is case-insensitive and can
+ be specified with or without a leading dot. Filenames may have <a href="#multipleext">multiple extensions</a> and the
+ <var>extension</var> argument will be compared against each of
+ them.</p>
<h3>See also</h3>
<ul>
<p>The <code class="directive">AddOutputFilter</code> directive maps the
filename extension <var>extension</var> to the <a href="../filter.html">filters</a> which will process responses
from the server before they are sent to the client. This is in
- addition to any filters defined elsewhere, including <code class="directive"><a href="../mod/core.html#setoutputfilter">SetOutputFilter</a></code> and <code class="directive"><a href="../mod/core.html#addoutputfilterbytype">AddOutputFilterByType</a></code> directive. This mapping is merged
+ addition to any filters defined elsewhere, including <code class="directive"><a href="../mod/core.html#setoutputfilter">SetOutputFilter</a></code> and <code class="directive"><a href="../mod/mod_filter.html#addoutputfilterbytype">AddOutputFilterByType</a></code> directive. This mapping is merged
over any already in force, overriding any mappings that already exist
for the same <var>extension</var>.</p>
<p>If more than one filter is specified, they must be separated
by semicolons in the order in which they should process the
- content. Both the <var>filter</var> and <var>extension</var> arguments
- are case-insensitive, and the extension may be specified with or
- without a leading dot.</p>
+ content. The <var>filter</var> argument is case-insensitive.</p>
+
+ <p>The <var>extension</var> argument is case-insensitive and can
+ be specified with or without a leading dot. Filenames may have <a href="#multipleext">multiple extensions</a> and the
+ <var>extension</var> argument will be compared against each of
+ them.</p>
<h3>See also</h3>
<ul>
<table class="directive">
<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Maps the given filename extensions onto the specified content
type</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>AddType <var>MIME-type</var> <var>extension</var>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>AddType <var>media-type</var> <var>extension</var>
[<var>extension</var>] ...</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
- <p>The <code class="directive">AddType</code> directive maps the given filename
- extensions onto the specified content type. <var>MIME-type</var> is the
- MIME type to use for filenames containing <var>extension</var>. This
- mapping is added to any already in force, overriding any mappings that
- already exist for the same <var>extension</var>. This directive can
- be used to add mappings not listed in the MIME types file (see the
- <code class="directive"><a href="#typesconfig">TypesConfig</a></code> directive).</p>
+ <p>The <code class="directive">AddType</code> directive maps the given
+ filename extensions onto the specified content
+ type. <var>media-type</var> is the <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media
+ type</a> to use for filenames containing
+ <var>extension</var>. This mapping is added to any already in
+ force, overriding any mappings that already exist for the same
+ <var>extension</var>. This directive can be used to add mappings
+ not listed in the media types file (see the <code class="directive"><a href="#typesconfig">TypesConfig</a></code> directive).</p>
<div class="example"><h3>Example</h3><p><code>
AddType image/gif .gif
</code></p></div>
+ <p>Or, to specify multiple file extensions in one directive:</p>
+
+ <div class="example"><h3>Example</h3><p><code>
+ AddType image/jpeg jpeg jpg jpe
+ </code></p></div>
+
<div class="note">
- It is recommended that new MIME types be added using the
+ It is recommended that new media types be added using the
<code class="directive">AddType</code> directive rather than changing the
<code class="directive"><a href="#typesconfig">TypesConfig</a></code> file.
</div>
- <p>The <var>extension</var> argument is case-insensitive, and can
- be specified with or without a leading dot.</p>
+ <p>The <var>extension</var> argument is case-insensitive and can
+ be specified with or without a leading dot. Filenames may have <a href="#multipleext">multiple extensions</a> and the
+ <var>extension</var> argument will be compared against each of
+ them.</p>
<h3>See also</h3>
<ul>
-<li><code class="directive"><a href="../mod/core.html#defaulttype">DefaultType</a></code></li>
<li><code class="directive"><a href="../mod/core.html#forcetype">ForceType</a></code></li>
</ul>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="DefaultLanguage" id="DefaultLanguage">DefaultLanguage</a> <a name="defaultlanguage" id="defaultlanguage">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Sets all files in the given scope to the specified
-language</td></tr>
-<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>DefaultLanguage <var>MIME-lang</var></code></td></tr>
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Defines a default language-tag to be sent in the Content-Language
+header field for all resources in the current context that have not been
+assigned a language-tag by some other means.</td></tr>
+<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>DefaultLanguage <var>language-tag</var></code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config, virtual host, directory, .htaccess</td></tr>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
<p>The <code class="directive">DefaultLanguage</code> directive tells Apache
- that all files in the directive's scope (<em>e.g.</em>, all files
+ that all resources in the directive's scope (<em>e.g.</em>, all resources
covered by the current <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> container) that don't have an explicit language
extension (such as <code>.fr</code> or <code>.de</code> as configured
by <code class="directive"><a href="#addlanguage">AddLanguage</a></code>) should be
- considered to be in the specified <var>MIME-lang</var> language. This
- allows entire directories to be marked as containing Dutch content, for
+ assigned a Content-Language of <var>language-tag</var>. This allows
+ entire directory trees to be marked as containing Dutch content, for
instance, without having to rename each file. Note that unlike using
extensions to specify languages, <code class="directive">DefaultLanguage</code>
can only specify a single language.</p>
- <p>If no <code class="directive">DefaultLanguage</code> directive is in force,
+ <p>If no <code class="directive">DefaultLanguage</code> directive is in force
and a file does not have any language extensions as configured
- by <code class="directive"><a href="#addlanguage">AddLanguage</a></code>, then that file
- will be considered to have no language attribute.</p>
+ by <code class="directive"><a href="#addlanguage">AddLanguage</a></code>, then no
+ Content-Language header field will be generated.</p>
<div class="example"><h3>Example</h3><p><code>
DefaultLanguage en
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="ModMimeUsePathInfo" id="ModMimeUsePathInfo">ModMimeUsePathInfo</a> <a name="modmimeusepathinfo" id="modmimeusepathinfo">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Tells mod_mime to treat path_info
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>Tells <code class="module"><a href="../mod/mod_mime.html">mod_mime</a></code> to treat <code>path_info</code>
components as part of the filename</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>ModMimeUsePathInfo On|Off</code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>ModMimeUsePathInfo Off</code></td></tr>
MultiviewsMatch Handlers Filters
</code></p></div>
+ <p><code class="directive">MultiviewsMatch</code> is not allowed in a
+ <code class="directive"><a href="../mod/core.html#location"><Location></a></code> or <code class="directive"><a href="../mod/core.html#locationmatch"><LocationMatch></a></code> section.</p>
+
+
<h3>See also</h3>
<ul>
<li><code class="directive"><a href="../mod/core.html#options">Options</a></code></li>
undo any associations inherited from parent directories or the
server config files.</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
+ <p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
<div class="example"><h3>Example</h3><p><code>
if both occur within the same directory configuration.</p>
</div>
- <p>The <var>extension</var> argument is case-insensitive, and can
+ <p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
</div>
the <code>/foo/bar</code> directory to being treated as normal
files, rather than as candidates for parsing (see the <code class="module"><a href="../mod/mod_include.html">mod_include</a></code> module).</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
+ <p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
</div>
later.</td></tr>
</table>
<p>The <code class="directive">RemoveInputFilter</code> directive removes any
- input filter associations for files with the given extensions.
+ input <a href="../filter.html">filter</a> associations for files with
+ the given extensions.
This allows <code>.htaccess</code> files in subdirectories to
undo any associations inherited from parent directories or the
server config files.</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
+ <p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
<h3>See also</h3>
any associations inherited from parent directories or the
server config files.</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
+ <p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
</div>
later.</td></tr>
</table>
<p>The <code class="directive">RemoveOutputFilter</code> directive removes any
- output filter associations for files with the given extensions.
+ output <a href="../filter.html">filter</a> associations for files with
+ the given extensions.
This allows <code>.htaccess</code> files in subdirectories to
undo any associations inherited from parent directories or the
server config files.</p>
- <p>The <var>extension</var> argument is case-insensitive, and can
+ <p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
<div class="example"><h3>Example</h3><p><code>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
- <p>The <code class="directive">RemoveType</code> directive removes any MIME
- type associations for files with the given extensions. This allows
- <code>.htaccess</code> files in subdirectories to undo any
- associations inherited from parent directories or the server
- config files. An example of its use might be:</p>
+ <p>The <code class="directive">RemoveType</code> directive removes any
+ <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media type</a> associations for files with
+ the given extensions. This allows <code>.htaccess</code> files in
+ subdirectories to undo any associations inherited from parent
+ directories or the server config files. An example of its use
+ might be:</p>
<div class="example"><h3>/foo/.htaccess:</h3><p><code>
RemoveType .cgi
<p>This will remove any special handling of <code>.cgi</code>
files in the <code>/foo/</code> directory and any beneath it,
- causing the files to be treated as being of the <code class="directive"><a href="../mod/core.html#defaulttype">DefaultType</a></code>.</p>
+ causing responses containing those files to omit the HTTP
+ Content-Type header field.</p>
<div class="note"><h3>Note</h3>
<p><code class="directive">RemoveType</code> directives are processed
latter if both occur within the same directory configuration.</p>
</div>
- <p>The <var>extension</var> argument is case-insensitive, and can
+ <p>The <var>extension</var> argument is case-insensitive and can
be specified with or without a leading dot.</p>
</div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<div class="directive-section"><h2><a name="TypesConfig" id="TypesConfig">TypesConfig</a> <a name="typesconfig" id="typesconfig">Directive</a></h2>
<table class="directive">
-<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>The location of the mime.types file</td></tr>
+<tr><th><a href="directive-dict.html#Description">Description:</a></th><td>The location of the <code>mime.types</code> file</td></tr>
<tr><th><a href="directive-dict.html#Syntax">Syntax:</a></th><td><code>TypesConfig <var>file-path</var></code></td></tr>
<tr><th><a href="directive-dict.html#Default">Default:</a></th><td><code>TypesConfig conf/mime.types</code></td></tr>
<tr><th><a href="directive-dict.html#Context">Context:</a></th><td>server config</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_mime</td></tr>
</table>
- <p>The <code class="directive">TypesConfig</code> directive sets the location
- of the MIME types configuration file. <var>File-path</var> is relative
- to the <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>. This file sets
+ <p>The <code class="directive">TypesConfig</code> directive sets the
+ location of the <a class="glossarylink" href="../glossary.html#media-type" title="see glossary">media types</a>
+ configuration file. <var>File-path</var> is relative to the
+ <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>. This file sets
the default list of mappings from filename extensions to content
- types. Most administrators use the provided <code>mime.types</code>
- file, which associates common filename extensions with IANA registered
- content types. The current list is maintained at <a href="http://www.isi.edu/in-notes/iana/assignments/media-types/media-types">http://www.isi.edu/in-notes/iana/assignments/media-types/media-types</a>.
- This simplifies the <code>httpd.conf</code> file by providing the
+ types. Most administrators use the provided
+ <code>mime.types</code> file, which associates common filename
+ extensions with the official list of IANA registered media types
+ maintained at <a href="http://www.iana.org/assignments/media-types/index.html">http://www.iana.org/assignments/media-types/index.html</a>
+ as well as a large number of unofficial types. This
+ simplifies the <code>httpd.conf</code> file by providing the
majority of media-type definitions, and may be overridden by
<code class="directive"><a href="#addtype">AddType</a></code> directives as
- needed. You should not edit the <code>mime.types</code> file, because
- it may be replaced when you upgrade your server.</p>
+ needed. You should not edit the <code>mime.types</code> file,
+ because it may be replaced when you upgrade your server.</p>
<p>The file contains lines in the format of the arguments to
an <code class="directive"><a href="#addtype">AddType</a></code> directive:</p>
<div class="example"><p><code>
- <var>MIME-type</var> [<var>extension</var>] ...
+ <var>media-type</var> [<var>extension</var>] ...
</code></p></div>
<p>The case of the extension does not matter. Blank lines, and lines
<p><span>Available Languages: </span><a href="../en/mod/mod_mime.html" title="English"> en </a> |
<a href="../ja/mod/mod_mime.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a></p>
</div><div id="footer">
-<p class="apache">Copyright
1999-2004 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
+<p class="apache">Copyright
2010 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
<p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>
</body></html>
\ No newline at end of file
projects / apache / blobdiff