home *** CD-ROM | disk | FTP | other *** search
syntax> <default>LogFormat "%h %l %u %t \"%r\" %>s %b"</default> <contextlist><context>server config</context><context>virtual host</context> </contextlist> <usage> <p>This directive specifies the format of the access log file.</p> <p>The <directive>LogFormat</directive> directive can take one of two forms. In the first form, where only one argument is specified, this directive sets the log format which will be used by logs specified in subsequent <directive>TransferLog</directive> directives. The single argument can specify an explicit <var>format</var> as discussed in the <a href="#formats">custom log formats</a> section above. Alternatively, it can use a <var>nickname</var> to refer to a log format defined in a previous <directive>LogFormat</directive> directive as described below.</p> <p>The second form of the <directive>LogFormat</directive> directive associates an explicit <var>format</var> with a <var>nickname</var>. This <var>nickname</var> can then be used in subsequent <directive>LogFormat</directive> or <directive module="mod_log_config">CustomLog</directive> directives rather than repeating the entire format string. A <directive>LogFormat</directive> directive that defines a nickname <strong>does nothing else</strong> -- that is, it <em>only</em> defines the nickname, it doesn't actually apply the format and make it the default. Therefore, it will not affect subsequent <directive module="mod_log_config">TransferLog</directive> directives. In addition, <directive>LogFormat</directive> cannot use one nickname to define another nickname. Note that the nickname should not contain percent signs (<code>%</code>).</p> <example><title>Example</title> LogFormat "%v %h %l %u %t \"%r\" %>s %b" vhost_common </example> </usage> </directivesynopsis> <directivesynopsis> <name>TransferLog</name> <description>Specify location of a log file</description> <syntax>TransferLog <var>file</var>|<var>pipe</var></syntax> <contextlist><context>server config</context><context>virtual host</context> </contextlist> <usage> <p>This directive has exactly the same arguments and effect as the <directive module="mod_log_config">CustomLog</directive> directive, with the exception that it does not allow the log format to be specified explicitly or for conditional logging of requests. Instead, the log format is determined by the most recently specified <directive module="mod_log_config">LogFormat</directive> directive which does not define a nickname. Common Log Format is used if no other format has been specified.</p> <example><title>Example</title> LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\""<br /> TransferLog logs/access_log </example> </usage> </directivesynopsis> </modulesynopsis> <?xml version="1.0" encoding="UTF-8" ?> <metafile> <basename>mod_log_config</basename> <path>/mod/</path> <relpath>..</relpath> <variants> <variant>en</variant> </variants> </metafile> <?xml version="1.0"?> <!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd"> <?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?> <modulesynopsis metafile="mod_mem_cache.xml.meta"> <name>mod_mem_cache</name> <description>Content cache keyed to URIs</description> <status>Experimental</status> <sourcefile>mod_mem_cache.c</sourcefile> <identifier>mem_cache_module</identifier> <summary> <note type="warning"> This module is experimental. Documentation is still under development... </note> <p>This module <em>requires</em> the service of <module >mod_cache</module>. It acts as a support module for <module >mod_cache</module> and provides a memory based storage manager. <module>mod_mem_cache</module> can be configured to operate in two modes: caching open file descriptors or caching objects in heap storage. <module>mod_mem_cache</module> is most useful when used to cache locally generated content or to cache backend server content for <module >mod_proxy</module> configured for <directive module="mod_proxy" >ProxyPass</directive> (aka <dfn>reverse proxy</dfn>).</p> <p>Content is stored in and retrieved from the cache using URI based keys. Content with access protection is not cached.</p> </summary> <seealso><module>mod_cache</module></seealso> <seealso><module>mod_disk_cache</module></seealso> <directivesynopsis> <name>MCacheSize</name> <description>The maximum amount of memory used by the cache in KBytes</description> <syntax>MCacheSize <var>KBytes</var></syntax> <default>MCacheSize 100</default> <contextlist><context>server config</context></contextlist> <usage> <p>The <directive>MCacheSize</directive> directive sets the maximum amount of memory to be used by the cache, in KBytes (1024-byte units). If a new object needs to be inserted in the cache and the size of the object is greater than the remaining memory, objects will be removed until the new object can be cached. The object to be removed is selected using the algorithm specified by <directive module="mod_mem_cache">MCacheRemovalAlgorithm</directive>.</p> <example><title>Example</title> MCacheSize 700000 </example> <note><title>Note</title> <p>The <directive>MCacheSize</directive> value must be greater than the value specified by the <directive module="mod_mem_cache" >MCacheMaxObjectSize</directive> directive.</p> </note> </usage> </directivesynopsis> <directivesynopsis> <name>MCacheMaxObjectCount</name> <description>The maximum number of objects allowed to be placed in the cache</description> <syntax>MCacheMaxObjectCount <var>value</var></syntax> <default>MCacheMaxObjectCount 1009</default> <contextlist><context>server config</context></contextlist> <usage> <p>The <directive>MCacheMaxObjectCount</directive> directive sets the maximum number of objects to be cached. The value is used to create the open hash table. If a new object needs to be inserted in the cache and the maximum number of objects has been reached, an object will be removed to allow the new object to be cached. The object to be removed is selected using the algorithm specified by <directive module="mod_mem_cache">MCacheRemovalAlgorithm</directive>.</p> <example><title>Example</title> MCacheMaxObjectCount 13001 </example> </usage> </directivesynopsis> <directivesynopsis> <name>MCacheMinObjectSize</name> <description>The minimum size (in bytes) of a document to be allowed in the cache</description> <syntax>MCacheMinObjectSize <var>bytes</var></syntax> <default>MCacheMinObjectSize 0</default> <contextlist><context>server config</context></contextlist> <usage> <p>The <directive>MCacheMinObjectSize</directive> directive sets the minimum size in bytes of a document for it to be considered cacheable.</p> <example><title>Example</title> MCacheMinObjectSize 10000 </example> </usage> </directivesynopsis> <directivesynopsis> <name>MCacheMaxObjectSize</name> <description>The maximum size (in bytes) of a document allowed in the cache</description> <syntax>MCacheMaxObjectSize <var>bytes</var></syntax> <default>MCacheMaxObjectSize 10000</default> <contextlist><context>server config</context></contextlist> <usage> <p>The <directive>MCacheMaxObjectSize</directive> directive sets the maximum allowable size, in bytes, of a document for it to be considered cacheable.</p> <example><title>Example</title> MCacheMaxObjectSize 6400000 </example> <note><title>Note</title> <p>The value of <directive>MCacheMaxObjectSize</directive> must be greater than the value specified by the <directive module="mod_mem_cache">MCacheMinObjectSize</directive> directive.</p> </note> </usage> </directivesynopsis> <directivesynopsis> <name>MCacheRemovalAlgorithm</name> <description>The algorithm used to select documents for removal from the cache</description> <syntax>MCacheRemovalAlgorithm LRU|GDSF</syntax> <default>MCacheRemovalAlgorithm GDSF</default> <contextlist><context>server config</context></contextlist> <usage> <p>The <directive>MCacheRemovalAlgorithm</directive> directive specifies the algorithm used to select documents for removal from the cache. Two choices are available:</p> <dl> <dt><code>LRU</code> (Least Recently Used)</dt> <dd><code>LRU</code> removes the documents that have not been accessed for the longest time.</dd> <dt><code>GDSF</code> (GreadyDual-Size)</dt> <dd><code>GDSF</code> assigns a priority to cached documents based on the cost of a cache miss and the size of the document. Documents with the lowest priority are removed first.</dd> </dl> <example><title>Example</title> MCacheRemovalAlgorithm GDSF<br /> MCacheRemovalAlgorithm LRU </example> </usage> </directivesynopsis> <directivesynopsis> <name>MCacheMaxStreamingBuffer</name> <description>Maximum amount of a streamed response to buffer in memory before declaring the response uncacheable</description> <syntax>MCacheMaxStreamingBuffer <var>size_in_bytes</var></syntax> <default>MCacheMaxStreamingBuffer the smaller of 100000 or MCacheMaxObjectSize</default> <contextlist><context>server config</context> </contextlist> <usage> <p>The <directive>MCacheMaxStreamingBuffer</directive> directive specifies the maximum number of bytes of a streamed response to buffer before deciding that the response is too big to cache. A streamed response is one in which the entire content is not immediately available and in which the <code>Content-Length</code> may not be known. Sources of streaming responses include proxied responses and the output of CGI scripts. By default, a streamed response will <em>not</em> be cached unless it has a <code>Content-Length</code> header. The reason for this is to avoid using a large amount of memory to buffer a partial response that might end up being too large to fit in the cache. The <directive>MCacheMaxStreamingBuffer</directive> directive allows buffering of streamed responses that don't contain a <code>Content-Length</code> up to the specified maximum amount of space. If the maximum buffer space is reached, the buffered content is discarded and the attempt to cache is abandoned.</p> <note><title>Note:</title> <p>Using a nonzero value for <directive>MCacheMaxStreamingBuffer</directive> will not delay the transmission of the response to the client. As soon as <module>mod_mem_cache</module> copies a block of streamed content into a buffer, it sends the block on to the next output filter for delivery to the client.</p> </note> <example> # Enable caching of streamed responses up to 64KB:<br /> MCacheMaxStreamingBuffer 65536 </example> </usage> </directivesynopsis> </modulesynopsis> <?xml version="1.0" encoding="UTF-8" ?> <metafile> <basename>mod_mem_cache</basename> <path>/mod/</path> <relpath>..</relpath> <variants> <variant>en</variant> </variants> </metafile> <?xml version="1.0"?> <!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd"> <?xml-stylesheet type="text/xsl" href="../style/manual.en.xsl"?> <modulesynopsis metafile="mod_mime.xml.meta"> <name>mod_mime</name> <description>Associates the requested filename's extensions with the file's behavior (handlers and filters) and content (mime-type, language, character set and encoding)</description> <status>Base</status> <sourcefile>mod_mime.c</sourcefile> <identifier>mime_module</identifier> <summary> <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 <module>mod_negotiation</module> for more information about <a href="../content-negotiation.html">content negotiation</a>.</p> <p>The directives <directive module="mod_mime">AddCharset</directive>, <directive module="mod_mime">AddEncoding</directive>, <directive module="mod_mime">AddLanguage</directive> and <directive module="mod_mime">AddType</directive> are all used to map file extensions onto the meta-information for that file. Respectively they set the character set, content-encoding, content-language, and MIME-type (content-type) of documents. The directive <directive module="mod_mime">TypesConfig</directive> is used to specify a file which also maps extensions onto MIME types. </p> <p>In addition, <module>mod_mime</module> may define the <a href="../handler.html">handler</a> and <a href="../filter.html">filters</a> that originate and process content. The directives <directive module="mod_mime">AddHandler</directive>, <directive module="mod_mime">AddOutputFilter</directive>, and <directive module="mod_mime">AddInputFilter</directive> control the modules or scripts that serve the document. The <directive module="mod_mime">MultiviewsMatch</directive> directive allows <module>mod_negotiation</module> to consider these file extensions to be included when testing Multiviews matches.</p> <p>While <module>mod_mime</module> associates meta-information with filename extensions, the <module>core</module> server provides directives that are used to associate all the files in a given container (<em>e.g.</em>, <directive type="section" module="core">Location</directive>, <directive type="section" module="core">Directory</directive>, or <directive type="section" module="core">Files</directive>) with particular meta-information. These directives include <directive module="core">ForceType</directive>, <directive module="core">SetHandler</directive>, <directive module="core">SetInputFilter</directive>, and <directive module="core">SetOutputFilter</directive>. The core directives override any filename extension mappings defined in <module>mod_mime</module>.</p> <p>Note that changing the meta-information 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 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> </summary> <seealso><directive module="mod_mime_magic">MimeMagicFile</directive></seealso> <seealso><directive module="core">AddDefaultCharset</directive></seealso> <seealso><directive module="core">ForceType</directive></seealso> <seealso><directive module="core">DefaultType</directive></seealso> <seealso><directive module="core">SetHandler</directive></seealso> <seealso><directive module="core">SetInputFilter</directive></seealso> <seealso><directive module="core">SetOutputFilter</directive></seealso> <section id="multipleext"><title>Files with Multiple Extensions</title> <p>Files can have more than one extension, and 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. 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> <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 with the handler. For example, if the <code>.imap</code> extension is mapped to the handler <code>imap-file</code> (from <module>mod_imap</module>) and the <code>.html</code> extension is mapped to the MIME-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. When it is processed, the <code>imap-file</code> handler will be used, and so it will be treated as a <module>mod_imap</module> imagemap file.</p> </section> <section id="contentencoding"><title>Content encoding</title> <p>A file of a particular MIME type 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 <code>pgp</code> or to an encoding such as UUencoding, which is designed for transmitting a binary file in an ASCII (text) format.</p> <p>The <a href="http://www.ietf.org/rfc/rfc2616.txt">HTTP/1.1 RFC</a>, section 14.11 puts it this way:</p> <blockquote cite="http://www.ietf.org/rfc/rfc2616.txt"> <p>The Content-Encoding entity-header field is used as a modifier to the media-type. When present, its value indicates what additional content codings have been applied to the entity-body, and thus what decoding mechanisms must be applied in order to obtain the media-type referenced by the Content-Type header field. Content-Encoding is primarily used to allow a document to be compressed without losing the identity of its underlying media type.</p> </blockquote> <p>By using more than one file extension (see <a href="#multipleext">section above about multiple file extensions</a>), you can indicate that a file is of a particular <em>type</em>, and also has a particular <em>encoding</em>. </p> <p>For example, you may have a file which is a Microsoft Word document, which is pkzipped to reduce its size. If the <code>.doc</code> extension is associated with the Microsoft Word file type, and the <code>.zip</code> extension is associated with the pkzip file encoding, then the file <code>Resume.doc.zip</code>would be known to be a pkzip'ed Word document.</p> <p>Apache sends a <code>Content-encoding</code> header with the resource, in order to tell the client browser about the encoding method.</p> <example>Content-encoding: pkzip</example> </section> <section id="charset-lang"><title>Character sets and languages</title> <p>In addition to file type and the file encoding, another important piece of information is what language a particular document is in, and in what character set the file should be displayed. For example, the document might be written in the Vietnamese alphabet, or in Cyrillic, and should be displayed as such. This information, also, is transmitted in HTTP headers.</p> <p>The character set, language, encoding and mime type are all used in the process of content negotiation (See <module>mod_negotiation</module>) to determine which document to give to the client, when there are alternative documents in more than one character set, language, encoding or mime type. All filename extensions associations created with <directive module="mod_mime">AddCharset</directive>, <directive module="mod_mime">AddEncoding</directive>, <directive module="mod_mime">AddLanguage</directive> and <directive module="mod_mime">AddType</directive> directives (and extensions listed in the <directive module="mod_mime_magic" >MimeMagicFile</directive>) participate in this select process. Filename extensions that are only associated using the <directive module="mod_mime">AddHandler</directive>, <directive module="mod_mime" >AddInputFilter</directive> or <directive module="mod_mime" >AddOutputFilter</directive> directives may be included or excluded from matching by using the <directive module="mod_mime" >MultiviewsMatch</directive> directive.</p> <section id="charset"><title>Charset</title> <p>To convey this further information, Apache optionally sends a <code>Content-Language</code> header, to specify the language that the document is in, and can append additional information onto the <code>Content-Type</code> header to indicate the particular character set that should be used to correctly render the information.</p> <example> Content-Language: en, fr<br /> Content-Type: text/plain; charset=ISO-8859-1 </example> <p>The language specification is the two-letter abbreviation for the language. The <code>charset</code> is the name of the particular character set which should be used.</p> </section> </section> <directivesynopsis> <name>AddCharset</name> <description>Maps the given filename extensions to the specified content charset</description> <syntax>AddCharset <var>charset</var> <var>extension</var> [<var>extension</var>] ...</syntax> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <override>FileInfo</override> <usage> <p>The <directive>AddCharset</directive> directive maps the given filename extensions to the specified content charset. <var>charset</var> is the MIME charset parameter of 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> <example><title>Example</title> AddLanguage ja .ja<br /> AddCharset EUC-JP .euc<br /> AddCharset ISO-2022-JP .jis<br /> AddCharset SHIFT_JIS .sjis </example> <p>Then the document <code>xxxx.ja.jis</code> will be treated as being a Japanese document whose charset is <code>ISO-2022-JP</code> (as will the document <code>xxxx.jis.ja</code>). The <directive>AddCharset</directive> directive is useful for both to inform the client about the character encoding of the document so that the document can be interpreted and displayed appropriately, and for <a href="../content-negotiation.html">content negotiation</a>, 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> </usage> <seealso><module>mod_negotiation</module></seealso> <seealso><directive module="core">AddDefaultCharset</directive></seealso> </directivesynopsis> <directivesynopsis> <name>AddEncoding</name> <description>Maps the given filename extensions to the specified encoding type</description> <syntax>AddEncoding <var>MIME-enc</var> <var>extension</var> [<var>extension</var>] ...</syntax> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <override>FileInfo</override> <usage> <p>The <directive>AddEncoding</directive> 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 <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> <example><title>Example</title> AddEncoding x-gzip .gz<br /> AddEncoding x-compress .Z </example> <p>This will cause filenames containing the <code>.gz</code> extension to be marked as encoded using the <code>x-gzip</code> encoding, and filenames containing the <code>.Z</code> extension to be marked as encoded with <code>x-compress</code>.</p> <p>Old clients expect <code>x-gzip</code> and <code>x-compress</code>, however the standard dictates that they're equivalent to <code>gzip</code> and <code>compress</code> respectively. Apache does content encoding comparisons by ignoring any leading <code>x-</code>. When responding with an encoding Apache will use whatever form (<em>i.e.</em>, <code>x-foo</code> or <code>foo</code>) the client requested. If the client didn't specifically request a particular form Apache will use the form given by the <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 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> </usage> </directivesynopsis> <directivesynopsis> <name>AddHandler</name> <description>Maps the filename extensions to the specified handler</description> <syntax>AddHandler <var>handler-name</var> <var>extension</var> [<var>extension</var>] ...</syntax> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <override>FileInfo</override> <usage> <p>Files having the name <var>extension</var> will be served by the specified <var><a href="../handler.html">handler-name</a></var>. This mapping is added to any already in force, overriding any mappings that already exist for the same <var>extension</var>. For example, to activate CGI scripts with the file extension <code>.cgi</code>, you might use:</p> <example> AddHandler cgi-script .cgi </example> <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> </usage> <seealso><directive module="core">SetHandler</directive></seealso> </directivesynopsis> <directivesynopsis> <name>AddInputFilter</name> <description>Maps filename extensions to the filters that will process client requests</description> <syntax>AddInputFilter <var>filter</var>[;<var>filter</var>...] <var>extension</var> [<var>extension</var>] ...</syntax> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <override>FileInfo</override> <compatibility>AddInputFilter is only available in Apache 2.0.26 and later.</compatibility> <usage> <p><directive>AddInputFilter</directive> maps the filename extension <var>extension</var> to the <a href="../filter.html">filters</a> which will process client requests and POST input when they are received by the server. This is in addition to any filters defined elsewhere, including the <directive module="core">SetInputFilter</directive> 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 filter and <var>extension</var> arguments are case-insensitive, and the extension may be specified with or without a leading dot.</p> </usage> </directivesynopsis> <directivesynopsis> <name>AddLanguage</name> <description>Maps the given filename extension to the specified content language</description> <syntax>AddLanguage <var>MIME-lang</var> <var>extension</var> [<var>extension</var>] ...</syntax> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <override>FileInfo</override> <usage> <p>The <directive>AddLanguage</directive> 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 <var>extension</var>.</p> <example><title>Example</title> AddEncoding x-compress .Z<br /> AddLanguage en .en<br /> AddLanguage fr .fr </example> <p>Then the document <code>xxxx.en.Z</code> will be treated as being a compressed English document (as will the document <code>xxxx.Z.en</code>). Although the content language is reported to the client, the browser is unlikely to use this information. The <directive>AddLanguage</directive> directive is more useful for <a href="../content-negotiation.html">content negotiation</a>, where the server returns one from several documents based on the client's language preference.</p> <p>If multiple language assignments are made for the same extension, the last one encountered is the one that is used. That is, for the case of:</p> <example> AddLanguage en .en<br /> AddLanguage en-uk .en<br /> AddLanguage en-us .en </example> <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> </usage> <seealso><module>mod_negotiation</module></seealso> </directivesynopsis> <directivesynopsis> <name>AddOutputFilter</name> <description>Maps filename extensions to the filters that will process responses from the server</description> <syntax>AddOutputFilter <var>filter</var>[;<var>filter</var>...] <var>extension</var> [<var>extension</var>] ...</syntax> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <override>FileInfo</override> <compatibility>AddOutputFilter is only available in Apache 2.0.26 and later.</compatibility> <usage> <p>The <directive>AddOutputFilter</directive> 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 <directive module="core">SetOutputFilter</directive> and <directive module="core" >AddOutputFilterByType</directive> directive. This mapping is merged over any already in force, overriding any mappings that already exist for the same <var>extension</var>.</p> <p>For example, the following configuration will process all <code>.shtml</code> files for server-side included procextension, and the order o w/The directives <direc<p>Old ciption <cotive> d;jLUDES;DEFLATE ration<br /> AddLanguage <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>AddOutputFilter ss the content. Both the filtey are srer>extension</var> arguments are case-insensitive, and the extension may be specified with or without a leading dot.</p> </d using thalAlgeseealso><directive module="core">Setmod_negotiation</module></seealso> </directivesynopsiodule=ectivesynopsis> <name>AddEncoding</name> <descriptionn one extehe given filename tensions to the specified encodpe he specifitensio<syntax>AddLanguage <var>MIME-lang</var> <var>extension</var> [<var>extension</var>] ...</syntax> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <overridater.</compatibility> odule="core" >AddOutpve>AddLanguage<</name> /directive> are all used tiven filenamextensions to thetensio<syntihe order intle> enc</var> de>x-gzip</code> enconguage of filenames contair.html">handler-name</a></var>. This mapping is added to any already in force, overriding any mappings that already exist </contextlist> argument iontent-Enddany alreadmingve> directivesile which n put usintocument <code>xxxxents. The directive <directive module modu)r characterame <var>extension</var>.</p> <examppe e> maps t </co> MCacheMaxObjectSize 6 <exIt spac%h %shouddy in t wiile which nume.d extension e>GDSF</coatibility> odule="core" >AddOutpvltehize</dire</module>.</e>GDSF</coatibilitents. The directive <directive moduleule>mis still under deved 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> </usage> <seealso><directive module="core">DefaultType</directive></seealso> <seealso><directive module="corethm LRU </example> </usage> </directivesynop<directive modulsis> <name>MCacheRemovahich nIME-lanps filename sider these file seare inclfthe aay be incl <p>Cap<dirVctive declaring the response <directive mod Any|Np> </uedO <c|o><dirs|seealsoir.[seealsoi|o><dirs]amingBuffer <var>size<directive mod Np> </uedO <c<default>MCacheRemovalAlgorithm GDSF</default> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <override>Fpatibility>AddOutputFilter is nly available in Apache 2.0.26 and later.</compatibi <directive module="mod_mimepule>e> corecharimum ="../cone's extesctive> directiot.</p> </usag/var> tot.</p> </usage>a>s the fins to featurnsiins to ltiviean . If the that chan,type</em>, les in atype. houx. mapped to theoay be to anp> </ued/directive> are aar>.</p> age ihat . If th,/em>, les in ade> will be ahoux. map>documents,ill be ahoux. map>if the , the extell be ahoux. map>use filented as being <cofilenNp> </uedO <c<dm ing the <module fileee nexilter</directivar>.</p> age ihat e> < thanharacl>Contoan . cognized/direciviews matches.</p> are tha href="../con <p>em>, les in ade> wi><direc, media-type , Lts in morthaE-type, la before tode>x-ricextee in whiche This moample, to ecumenuns</code</mode>e encosage a he order inefault>ne's exteted as beingo meta-inencoding or mime tyinsensitHons wi/thao><dirs, cached.trs defined elsehe <directive module="mod_mime">Mucodeiehize extell be Hons cuments,ill be F the <a he , th</dire ing thkeywsepse cache, inme type facdified dr thal,> <defaultstl <ping the name,type</em>, les in aty>Aamed respbetw</exll be ahoux. map>any file coIME5le> spquivalent ahoux. map>pl file coIMEheMa the conf file, any file cfig</directicolon/p>meMagicFi MCache.<dt>r nIME file, as<p>Then th-lanpile extensiop <cod a use:</p>op</codeiME file, as<p>Then th-lanpnt to give code>.zip</code> ex file,as<p-lename exfilented as beinY</em>. fiis furncodinwill usny file containing sheoay be ,eee >mef/direciviews matches.</p> ompr cli. cognizements are with boahe order ine's exteny>AddOutpu1.3guage <unp ode>Cbilitd a hasis usually wille naresp.oldirec.bakE-lanps fctiebmas.</pnith as</code</ining e name for the same <var>extension</var>.</p> <p>For examplncodinheealsoir.-file</cion>Maps oic" >MimeMae <drecti, bulename tive> d<un<codefig</direcs used. That is, for the ce<directive mod Hons F the < MCacheMaxStreamingBuffeDefaultType</directive></seealso>Op</cos<directive module="core">DefaultTyading dot.</p> </usage> <seealso><module>mod_negotiation</module></seealso> </directivesyno <seeas> <directivesynopsis> <naSecriptis that areLanguage<<scopeription>Maps the fiextension to the specified conte <seeas> <dthe specified contenton</var> [<var>extension</var>] ...</syntax> <contextlist><context>server config</context><context>virtual host</context> <context>directory</context><context>.htaccess</context></contextlist> <overridater.</compatibility <seeas> <dir module="mod_mime">MucellsAddOutp memory to ptis that areLangd_mime">M's<scoperthe files in a ptis thatder in wv in the curr </expe</directive></seealsoDirectory</directive>ve type="section" ociate all) bufferi</p> nas</l tnguage</code> h <p>By udings. More if the (<em>i.e.deual-Size)< <pr is specif_mime">AddCharset</directive>, s> <dir module="m)odings, such as n bytes, o considersed tiven he specified content -letter abbrand the <tivieareamed xt>virtuies the <code>.gz</c/code> encoDumod href=",lfthe he brox-coppin, and ca/overridd e> <dOuts onto le>mod_mimorted tensio/directive> are aode>Contentset-lang",ompatibility <seeas> <dir module="md <var>en> <co>TypesCon nsio preference on the client's lanoompatibility <seeas> <dir module="mod_mime">Mue rece mapping is ts asschanging the i</p> nntset-langnencoding or m <pr is specif_mime">AddCharset</directive>, s> <dir module="mociated wons onte file <code>wn bytes, o conU</codereference.<t-ribulor it to be considered cacheable.</p> <ex <seeas> <dt.en<br /> Addwith or without a leading dot.</p> </usage> <seealso><module>mod_negotiation</module></seealso> </directivesynoModctivdt>Pathntext>sis> <name>MCacheRemellsAiviews matches.</p> iptixtenlso refeath_itext>ile cfilablon <sic" client de>x-gzie declaring the response odctivdt>Pathntex On|OffamingBuffer <var>sizeodctivdt>Pathntex Offamefault>MCacheRemovalAlgorithm GDxt>virtual host</conontext><context>t> <override>Fpatibility>AddOutputFil41r is nly aailable in Apache 2.0.26 and later.</compatibilityModctivdt>Pathntext>>). The <directive>Addde <var>exlabbn, <modu/name> </code> ex file,eath_itext>ile c URL lablon e <var>extpp<coiviews matches.</p> 'le>core</moduloer. This wilnlikelefault>var>ex the m. More Offamile c -documess r,e> ex file,eath_itext>ile cr server-son ee re cme for the same </contextlist spac%h %shouddfile To m</p> ext>serv thatys.<mr it to be considered cacheable.</p> <exaodctivdt>Pathntex Onn<br /> AddLanguage <vaTo m</p> . If the tha file,/bar/foouration will paddite extell be /bar for the laa e type="e="mod_mime">AddLanguyModctivdt>Pathntext>>). The m. More One>x-gzip</codeiviews matches.</p> filesxtenl be us%h may nIf the se extell be /bar/foouration will p thore</moduted twill use seealso><dir cache,;jLUDES uration will paamplndhe Microsoft,;jLUDES>Then th-lateader wontent-encs wilnlIfompatibilityModctivdt>Pathntext>>). The is ondocumem Apache will u,;jLUDES>Then th-lateadStreamingume.d excified with or without a leading dot.</p> </usage>AextptPathntext>>). The lso><module>mod_negotiation</module></seealso> </directivesynoalAlgen> <directivesynopsis> <nR)</dt> nntt to it's mime type. e that (lanfs onte epleext"><tideclaring the responsealAlgen> < ilter</var>[;<var>filter</var>...] <var>ex nsion</var> [<var>extension</var>] ext>server config</conorithm GDxt>virtual host</cotext><contecontext>directory</context><context>.htaccess</context></contextlist> <override>alAlgen> < de> <compatibility>AddOutputFilt4r is only available in Apache 2.0.26 and later.</compatibilityalAlgen> <di"core" >AddOutpvl)</dt> nnmeta-infoo it's mime type. e thaf <sectionLanguage<<ation" withencounteio ltiviea <module>text>direcn th-lanpny>Asubxt>virtuies thage, ennd</var>.mime type. einddiioding whic" he >virtuies y mappy wille na/syntax> h-lanpted as being <code>en-us</code>.</p> <p>The <var>extension</var> argument is case-insensitive, and can be specified be considered cacheable.</p> <exalAlgen> < . map uratio/> MCacheRemovalAlgorithm LRU </example> </usage> </directivesynoalAlges> <directivesynopsis> <naR)</dt> nnttde> respectively mime type. e that (lanfs onte epleext"><tideclaring the responsealAlgeing type</des</var>[;<var>filter</var>...] <var>ex nsion</var> [<var>extension</var>] ext>server config</conorithm GDxt>virtual host</cotext><contecontext>directory</context><context>.htaccess</context></contextli2.0.26 and later.</compatibilityalAlge <usage> <p>The <directivl)</dt> nnmeta-ipectively mime type. e thaf <sectionLanguage<<ation" withbbrand the <tiviea <module>text>direcn th-lanpny>Asubxt>virtuies thennd<ver any al.mime type. einddiioding whic" he >virtuies y mappy wille na/syntax> h-lanpt Anr>extensd withoutsedisplayed:ified be considered ca/foo/le>tex 
