From: André Malo Date: Sun, 2 Nov 2003 12:59:48 +0000 (+0000) Subject: backport the note about accumulative extension behaviours. X-Git-Tag: 2.0.49~401 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=3b5f384e1f068f01590ba9afdc8c61450456a16f;p=thirdparty%2Fapache%2Fhttpd.git backport the note about accumulative extension behaviours. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/APACHE_2_0_BRANCH@101680 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_mime.html.en b/docs/manual/mod/mod_mime.html.en index 752a9baac60..610b077bcdf 100644 --- a/docs/manual/mod/mod_mime.html.en +++ b/docs/manual/mod/mod_mime.html.en @@ -118,10 +118,17 @@ welcome.fr.html 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 .gif maps to the MIME-type - image/gif and .html maps to the MIME-type - text/html, then the file welcome.gif.html - will be associated with the MIME-type text/html.

+ used, except for languages and content encodings. For example, if + .gif maps to the MIME-type image/gif and + .html maps to the MIME-type text/html, then the + file welcome.gif.html will be associated with the MIME-type + text/html.

+ +

Languages and content encodings are treated accumulative, because one can assign + more than one language or encoding to a particular ressource. For example, + the file welcome.html.en.de will be delivered with + Content-Language: en, de and Content-Type: + text/html.

Care should be taken when a file with multiple extensions gets associated with both a MIME-type and a handler. This will @@ -169,7 +176,7 @@ .doc extension is associated with the Microsoft Word file type, and the .zip extension is associated with the pkzip file encoding, then the file - Resume.doc.zipwould be known to be a pkzip'ed Word + Resume.doc.zip would be known to be a pkzip'ed Word document.

Apache sends a Content-encoding header with the diff --git a/docs/manual/mod/mod_mime.xml b/docs/manual/mod/mod_mime.xml index a5cbe58329d..ad509aeb67c 100644 --- a/docs/manual/mod/mod_mime.xml +++ b/docs/manual/mod/mod_mime.xml @@ -87,10 +87,18 @@ module="mod_mime_magic">MimeMagicFile welcome.fr.html 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 .gif maps to the MIME-type - image/gif and .html maps to the MIME-type - text/html, then the file welcome.gif.html - will be associated with the MIME-type text/html.

+ used, except for languages and content encodings. For example, if + .gif maps to the MIME-type image/gif and + .html maps to the MIME-type text/html, then the + file welcome.gif.html will be associated with the MIME-type + text/html.

+ +

Languages and content encodings are treated accumulative, because one can assign + more than one language or encoding to a particular ressource. For example, + the file welcome.html.en.de will be delivered with + Content-Language: en, de and Content-Type: + text/html.

Care should be taken when a file with multiple extensions gets associated with both a MIME-type and a handler. This will @@ -139,7 +147,7 @@ module="mod_mime_magic">MimeMagicFile .doc extension is associated with the Microsoft Word file type, and the .zip extension is associated with the pkzip file encoding, then the file - Resume.doc.zipwould be known to be a pkzip'ed Word + Resume.doc.zip would be known to be a pkzip'ed Word document.

Apache sends a Content-encoding header with the