cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
rse 00/02/05 03:34:38 Modified:htdocs/manual/mod mod_mime.html Log: Enhance AddCharset description. Submitted by: Youichirou Koga [EMAIL PROTECTED] PR: 5554 Revision ChangesPath 1.35 +5 -5 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.34 retrieving revision 1.35 diff -u -r1.34 -r1.35 --- mod_mime.html 2000/01/08 19:57:29 1.34 +++ mod_mime.html 2000/02/05 11:34:36 1.35 @@ -139,12 +139,12 @@ /pre P -Then the document samp.ja.jis/samp will be treated as being a +Then the document CODE.ja.jis/CODE will be treated as being a Japanese document whose charset is ISO-2022-JP (as will the document -samp.jis.ja/samp). Although the content charset is reported to -the client, the browser is unlikely to use this information. The -AddCharset directive is more useful for -A HREF=../content-negotiation.htmlcontent negotiation/A, where +CODE.jis.ja/CODE). The AddCharset 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.htmlcontent negotiation/A, where the server returns one from several documents based on the client's charset preference. /P
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
lars00/01/08 11:57:30 Modified:htdocs/manual/mod mod_mime.html Log: add missing compatiblity info Revision ChangesPath 1.34 +6 -1 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.33 retrieving revision 1.34 diff -u -r1.33 -r1.34 --- mod_mime.html 1999/12/09 18:10:39 1.33 +++ mod_mime.html 2000/01/08 19:57:29 1.34 @@ -397,7 +397,12 @@ A HREF=directive-dict.html#Module REL=Help -STRONGModule:/STRONG/A mod_mimeP +STRONGModule:/STRONG/A mod_mimeBR +A + HREF=directive-dict.html#Compatibility + REL=Help +STRONGCompatibility:/STRONG/A DefaultLanguage is only available in Apache +1.3.4 and later.P The DefaultLanguage directive tells Apache that all files in the directive's scope (EMe.g./EM, all files covered by the current
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
coar99/12/09 10:10:42
Modified:src CHANGES
.STATUS
src/modules/standard mod_mime.c
htdocs/manual/mod mod_mime.html
Log:
Add the AddCharset functionality to mod_mime.
Submitted by: Youichirou Koga [EMAIL PROTECTED]
Reviewed by: Ken Coar, Martin Kraemer
Revision ChangesPath
1.1478+3 -0 apache-1.3/src/CHANGES
Index: CHANGES
===
RCS file: /home/cvs/apache-1.3/src/CHANGES,v
retrieving revision 1.1477
retrieving revision 1.1478
diff -u -r1.1477 -r1.1478
--- CHANGES 1999/12/09 17:19:28 1.1477
+++ CHANGES 1999/12/09 18:10:24 1.1478
@@ -1,4 +1,7 @@
Changes with Apache 1.3.10
+ *) Enhance mod_mime with an AddCharset directive to properly handle
+ that negotiation dimension.
+ [Youichirou Koga [EMAIL PROTECTED]]
*) OS: Added first cut at support for IBM's OS/390.
[Ovies Brabson [EMAIL PROTECTED]]
1.764 +1 -4 apache-1.3/STATUS
Index: STATUS
===
RCS file: /home/cvs/apache-1.3/STATUS,v
retrieving revision 1.763
retrieving revision 1.764
diff -u -r1.763 -r1.764
--- STATUS1999/12/09 17:21:35 1.763
+++ STATUS1999/12/09 18:10:30 1.764
@@ -1,5 +1,5 @@
1.3 STATUS:
- Last modified at [$Date: 1999/12/09 17:21:35 $]
+ Last modified at [$Date: 1999/12/09 18:10:30 $]
Release:
@@ -42,9 +42,6 @@
Available Patches:
-* Youichirou Koga's patch to add AddCharset to mod_mime.
- Message-ID: 384E91DF.D92FABC2.Golux.Com
- Status: Ken +1, Martin +1(after minor fix)
* Andrew Ford's patch (1999/12/05) to add absolute times to mod_expires
Message-ID: [EMAIL PROTECTED]
1.50 +336 -11 apache-1.3/src/modules/standard/mod_mime.c
Index: mod_mime.c
===
RCS file: /home/cvs/apache-1.3/src/modules/standard/mod_mime.c,v
retrieving revision 1.49
retrieving revision 1.50
diff -u -r1.49 -r1.50
--- mod_mime.c1999/04/20 17:27:51 1.49
+++ mod_mime.c1999/12/09 18:10:34 1.50
@@ -75,6 +75,7 @@
typedef struct {
table *forced_types;/* Additional AddTyped stuff */
table *encoding_types; /* Added with AddEncoding... */
+table *charset_types;/* Added with AddCharset... */
table *language_types; /* Added with AddLanguage... */
table *handlers;/* Added with AddHandler... */
array_header *handlers_remove; /* List of handlers to remove */
@@ -84,6 +85,24 @@
char *default_language; /* Language if no AddLanguage ext found */
} mime_dir_config;
+typedef struct param_s {
+char *attr;
+char *val;
+struct param_s *next;
+} param;
+
+typedef struct {
+char *type;
+char *subtype;
+param *param;
+} content_type;
+
+static char tspecial[] = {
+'(', ')', '', '', '@', ',', ';', ':',
+'\\', '', '/', '[', ']', '?', '=',
+'\0'
+};
+
module MODULE_VAR_EXPORT mime_module;
static void *create_mime_dir_config(pool *p, char *dummy)
@@ -93,6 +112,7 @@
new-forced_types = ap_make_table(p, 4);
new-encoding_types = ap_make_table(p, 4);
+new-charset_types = ap_make_table(p, 4);
new-language_types = ap_make_table(p, 4);
new-handlers = ap_make_table(p, 4);
new-handlers_remove = ap_make_array(p, 4, sizeof(handlers_info));
@@ -119,9 +139,11 @@
}
new-forced_types = ap_overlay_tables(p, add-forced_types,
- base-forced_types);
+ base-forced_types);
new-encoding_types = ap_overlay_tables(p, add-encoding_types,
base-encoding_types);
+new-charset_types = ap_overlay_tables(p, add-charset_types,
+base-charset_types);
new-language_types = ap_overlay_tables(p, add-language_types,
base-language_types);
new-handlers = ap_overlay_tables(p, add-handlers,
@@ -135,17 +157,18 @@
return new;
}
-static const char *add_type(cmd_parms *cmd, mime_dir_config * m, char *ct,
+static const char *add_type(cmd_parms *cmd, mime_dir_config *m, char *ct,
char *ext)
{
if (*ext == '.')
-++ext;
+ ++ext;
+
ap_str_tolower(ct);
ap_table_setn(m-forced_types, ext, ct);
return NULL;
}
-static const char *add_encoding(cmd_parms *cmd, mime_dir_config * m, char
*enc,
+static const char *add_encoding(cmd_parms *cmd, mime_dir_config *m, char
*enc,
char *ext)
{
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
coar99/04/29 12:55:55 Modified:htdocs/manual/mod mod_mime.html Log: Point out that for multiple AddLanguage directives with the same extension, the last one encountered dominates. This is true of lots of directives, but this is the one on which we got a PR.. PR: 3570 Revision ChangesPath 1.32 +25 -8 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.31 retrieving revision 1.32 diff -u -r1.31 -r1.32 --- mod_mime.html 1999/01/08 23:13:29 1.31 +++ mod_mime.html 1999/04/29 19:55:53 1.32 @@ -226,34 +226,51 @@ A HREF=directive-dict.html#Module REL=Help -STRONGModule:/STRONG/A mod_mimeP +STRONGModule:/STRONG/A mod_mime +P The AddLanguage directive maps the given filename extensions to the specified content language. EMMIME-lang/EM is the MIME language of filenames containing EMextension/EM. This mapping is added to any already in force, overriding any mappings that already exist for the same EMextension/EM. - +/P +P Example: BLOCKQUOTECODE AddEncoding x-compress ZBR AddLanguage en .enBR AddLanguage fr .frBR /CODE/BLOCKQUOTE - +/P +P Then the document CODE.en.Z/CODE will be treated as being a compressed English document (as will the document CODE.Z.en/CODE). Although the content language is reported to the client, the browser is unlikely to use this information. The -AddLanguage directive is more useful for A -HREF=../content-negotiation.htmlcontent negotiation/A, where +AddLanguage directive is more useful for +A HREF=../content-negotiation.htmlcontent negotiation/A, where the server returns one from several documents based on the client's -language preference.P - +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 +PRE +AddLanguage en .en +AddLanguage en-uk .en +AddLanguage en-us .en +/PRE +P +documents with the extension CODE.en/CODE would be treated as +being CODEen-us/CODE. +/P +P STRONGSee also/STRONG: A HREF=#multipleextFiles with multiple extensions/A BR STRONGSee also/STRONG: A HREF=./mod_negotiation.htmlmod_negotiation/A +/P HR
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
coar99/01/08 14:37:04 Modified:.STATUS htdocs/manual/mod mod_mime.html Log: Add the documentation for the RemoveHandler directive. Revision ChangesPath 1.596 +1 -3 apache-1.3/STATUS Index: STATUS === RCS file: /home/cvs/apache-1.3/STATUS,v retrieving revision 1.595 retrieving revision 1.596 diff -u -r1.595 -r1.596 --- STATUS1999/01/08 22:20:36 1.595 +++ STATUS1999/01/08 22:37:02 1.596 @@ -1,5 +1,5 @@ 1.3 STATUS: - Last modified at [$Date: 1999/01/08 22:20:36 $] + Last modified at [$Date: 1999/01/08 22:37:02 $] Release: @@ -46,8 +46,6 @@ Documentation that needs writing: * Document compilation on Win95 and NT - -* RemoveHandler directive needs docs * Need a document explaining mod_rewrite/UseCanonicalName off based virtualhosting. (If it exists already I can't find it easily.) 1.30 +47 -1 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.29 retrieving revision 1.30 diff -u -r1.29 -r1.30 --- mod_mime.html 1998/12/27 02:38:15 1.29 +++ mod_mime.html 1999/01/08 22:37:03 1.30 @@ -48,7 +48,7 @@ value of the CODELast-Modified/CODE header. Thus, previously cached copies may still be used by a client or proxy, with the previous headers. -A NAME=multipleextH2Files with Multiple Extensions/H2/A +H2A NAME=multipleextFiles with Multiple Extensions/A/H2 Files can have more than one extension, and the order of the extensions is inormally/i irrelevant. For example, if the file @@ -92,6 +92,7 @@ LIA HREF=#addtypeAddType/A LIA HREF=#defaultlanguageDefaultLanguage/A LIA HREF=#forcetypeForceType/A +LIA HREF=#removehandlerRemoveHandler/A LIA HREF=#sethandlerSetHandler/A LIA HREF=#typesconfigTypesConfig/A /UL @@ -389,6 +390,51 @@ /PRE PNote that this will override any filename extensions that might determine the media type./PHR + +H2A NAME=removehandlerRemoveHandler/A/H2 + +A + HREF=directive-dict.html#Syntax + REL=Help +STRONGSyntax:/STRONG/A RemoveHandler EMextension extension.../EMBR +A + HREF=directive-dict.html#Context + REL=Help +STRONGContext:/STRONG/A directory, .htaccessBR +A + HREF=directive-dict.html#Status + REL=Help +STRONGStatus:/STRONG/A BaseBR +A + HREF=directive-dict.html#Module + REL=Help +STRONGModule:/STRONG/A mod_mimeBR +A + HREF=directive-dict.html#Compatibility + REL=Help +STRONGCompatibility:/STRONG/A RemoveHandler is only available in Apache +1.3.4 and later.P + +P +The SAMPRemoveHandler/SAMP directive removes any +handler 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 +DL + DTCODE/foo/.htaccess:/CODE/DT + DDCODEAddHandler server-parsed .html/CODE/DD + DTCODE/foo/bar/.htaccess:/CODE/DT + DDCODERemoveHandler .html/CODE/DD +/DL +P +This has the effect of returning SAMP.html/SAMP files in the +SAMP/foo/bar/SAMP directory to being treated as normal +files, rather than as candidates for parsing (see the +A HREF=mod_include.htmlSAMPmod_include/SAMP/A module). +/P +HR H2A NAME=sethandlerSetHandler/A/H2
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
coar99/01/08 15:13:30 Modified:htdocs/manual install-tpf.html readme-tpf.html suexec.html suexec_1_2.html htdocs/manual/mod mod_mime.html Log: The semi-occasional partial cleaning-up of the HTML.. Revision ChangesPath 1.4 +157 -148 apache-1.3/htdocs/manual/install-tpf.html Index: install-tpf.html === RCS file: /home/cvs/apache-1.3/htdocs/manual/install-tpf.html,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- install-tpf.html 1999/01/06 21:56:57 1.3 +++ install-tpf.html 1999/01/08 23:13:27 1.4 @@ -1,109 +1,121 @@ !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2 Final//EN -html -head -titleInstalling Apache on TPF/title -/head +HTML +HEAD +TITLEInstalling Apache on TPF/TITLE +/HEAD -a name=top/a -h1 align=centerInstalling the Apache 1.3 HTTP Server on TPF/h1 -hr -center[nbspa href=#setupSetup/a - nbsp|nbspa href=#compilationCompilation/a - nbsp|nbspa href=#installationInstallation/a - nbsp|nbspa href=#visualageVisualAge/anbsp] -/center -hr -br +BODY +H1 ALIGN=center + A NAME=topInstalling the Apache 1.3 HTTP Server on TPF/A +/H1 +HR +CENTER[nbsp;A HREF=#setupSetup/A + nbsp;|nbsp;A HREF=#compilationCompilation/A + nbsp;|nbsp;A HREF=#installationInstallation/A + nbsp;|nbsp;A HREF=#visualageVisualAge/Anbsp;] +/CENTER +HR +BR -p +P This document outlines the steps needed to install Apache onto a TPF system. -brbr -You should first read htdocs/manual/a href=readme-tpf.htmlreadme-tpf.html/a +/P +P +You should first read +htdocs/manual/A HREF=readme-tpf.htmlreadme-tpf.html/A for basic information on the port of Apache to TPF including required PUT level and supported functions amp; modules. -/p +/P -a name=setupnbsp;/a -h2 align=centerSetup/h2 -p -Due to the use of EBCDIC on MVS OS/390 Open Edition (later referred to simply as +H2 align=centerA NAME=setupSetup/A/H2 +P +Due to the use of EBCDIC on MVS OS/390 Open Edition +(later referred to simply as Open Edition), we've found that the most reliable method for loading Apache onto your system is to unzip and tar the distribution -file on your PC, and then copy the extracted files to Open Edition via an NFS client +file on your PC, and then copy the extracted files to Open Edition +via an NFS client capable of transferring the data in EBCDIC format. -brbr +/P +P Before moving the distribution to an Open Edition environment, verify that the NFS drive will transfer the filenames with upper/lower case preserved. -brbr +/P +P Since Open Edition is not the ultimate destination of the files, -the only required files and subdirectories that need to be moved to Open Edition +the only required files and subdirectories that need to be moved to +Open Edition are in /src. -brbr -font strong color=redWARNING/font: +/P +P +FONT COLOR=redSTRONGWARNING/STRONG/FONT: If you are using a product such as WinZip on your PC, verify that -the iTAR File Smart CR/LF Conversion/i option is NOT checked. +the EMTAR File Smart CR/LF Conversion/EM option is NOT checked. You can find this in WinZip under Options, Configuration. Since you had to tar and unzip the file to read this document, you need to re-tar and -unzip if the CR/LF option was checked. This will save you lots of headaches later on. -brbr -font strong color=redWARNING/font: +/P +P +FONT COLOR=redSTRONGWARNING/STRONG/FONT: Editing files on a PC before moving them to Open Edition may result -in the loss/addition of unprintable characters. Files of concern include shell -scripts and src/Configuration. The most common problems are with tab characters +in the loss/addition of unprSintable characters. Files of concern include shell +scripts and src/Configuration. The most common problems are with +tab characters and CR/LF characters. Most editors will handle the CR/LF problem correctly but none seem to handle tab characters. If you need to edit files, edit them in a UNIX editor such as vi or emacs. -/p +/P -a name=compilationnbsp;/a -h2 align=centerCompilation/h2 -p +H2 align=centerA NAME=compilationCompilation/A/H2 +P Apache supports the notion of optional modules. However, the server has to know which modules are compiled into it. In order for those modules to be effective, it is necessary to generate a short bit of code (modules.c) which simply has a list of them. If you are using the make and Configure utility, modules.c will be created for you. -brbr +/P +P The provided scripts assume a c89 compiler and have only been tested on an Open Edition environment. If you are using a platform other that Open Edition you may need to modify
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
pcs 98/12/04 09:39:25 Modified:htdocs/manual/mod mod_mime.html Log: Fix HTML Revision ChangesPath 1.28 +1 -1 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.27 retrieving revision 1.28 diff -u -r1.27 -r1.28 --- mod_mime.html 1998/12/02 17:01:26 1.27 +++ mod_mime.html 1998/12/04 17:39:24 1.28 @@ -1,4 +1,4 @@ -!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2 Final//EN +!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2 Final//EN HTML HEAD TITLEApache module mod_mime/TITLE
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
pcs 98/12/02 09:01:26 Modified:htdocs/manual/mod mod_mime.html Log: Actually, without a DefaultLanguage documents are considered to have _no_ language attribute. Apache does not default to English. Revision ChangesPath 1.27 +16 -7 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.26 retrieving revision 1.27 diff -u -r1.26 -r1.27 --- mod_mime.html 1998/12/02 03:45:51 1.26 +++ mod_mime.html 1998/12/02 17:01:26 1.27 @@ -1,4 +1,4 @@ -!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2 Final//EN +!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 3.2 Final//EN HTML HEAD TITLEApache module mod_mime/TITLE @@ -324,12 +324,21 @@ The DefaultLanguage directive tells Apache that all files in the directive's scope (EMe.g./EM, all files covered by the current -CODElt;Directorygt;/CODE container) that don't have an explicit language -extension (such as SAMP.fr/SAMP or SAMP.de/SAMP) should be -considered to be the specified EMMIME-lang/EM language -by default, rather than English. This allows entire directories -to be marked as containing Dutch content, for instance, without -having to rename each file. +CODElt;Directorygt;/CODE container) that don't have an explicit +language extension (such as SAMP.fr/SAMP or SAMP.de/SAMP as +configured by SAMPAddLanguage/SAMP) should be considered to be in +the specified EMMIME-lang/EM language. This allows entire +directories to be marked as containing Dutch content, for instance, +without having to rename each file. Note that unlike using extensions +to specify languages, SAMPDefaultLanguage/SAMP can only specify a +single language. + +P + +If no SAMPDefaultLanguage/SAMP directive is in force, and a file +does not have any language extensions as configured by +SAMPAddLanguage/SAMP, then that file will be considered to have no +language attribute. P
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
pcs 98/11/20 07:45:36 Modified:htdocs/manual/mod mod_mime.html Log: Be more careful when documenting the way that extensions are mapped to meta data. Note the effect of multiple extensions in all the Add* directive descriptions, and explain that these directives add or override existing mappings. Remove assumptions that there is only one extension. Add note about how setting both handlers and media types could result in unexpected results. Remove some highly misleading information such as that the type is the extension left after content-encoding and language extensions have been removed PR: 3151 Revision ChangesPath 1.25 +91 -41apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.24 retrieving revision 1.25 diff -u -r1.24 -r1.25 --- mod_mime.html 1998/09/17 12:33:07 1.24 +++ mod_mime.html 1998/11/20 15:45:36 1.25 @@ -44,8 +44,14 @@ P +Note that changing the type or encoding of a file does not change the +value of the CODELast-Modified/CODE header. Thus, previously cached +copies may still be used by a client or proxy, with the previous headers. + +A NAME=multipleextH2Files with Multiple Extensions/H2/A + Files can have more than one extension, and the order of the -extensions is normally irrelevant. For example, if the file +extensions is inormally/i irrelevant. For example, if the file CODEwelcome.html.fr/CODE maps onto content type text/html and language French then the file CODEwelcome.fr.html/CODE will map onto exactly the same information. The only exception to this is if an @@ -59,19 +65,26 @@ P -Note that changing the type or encoding of a file does not change the -value of the CODELast-Modified/CODE header. Thus, previously cached -copies may still be used by a client or proxy, with the previous headers. +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 CODEwelcome.gif.html/CODE will +be associated with the MIME-type text/html. P -Please note that changing a file's type or encoding does not change -the value of the CODELast-Modified/CODE header. Previously cached -copies may still be used by a client or proxy. +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 imap-file (from mod_imap) and the CODE.html/CODE +extension is mapped to the MIME-type text/html, then the file +CODEworld.imap.html/CODE will be associated with both the +imap-file handler and text/html MIME-type. When it is processed, +the imap-file handler will be used, and so it will be treated as a +mod_imap imagemap file. -P - -H2 Directives/H2 +H2Directives/H2 UL LIA HREF=#addencodingAddEncoding/A LIA HREF=#addhandlerAddHandler/A @@ -106,18 +119,20 @@ HREF=directive-dict.html#Module REL=Help STRONGModule:/STRONG/A mod_mimeP + +The AddEncoding directive maps the given filename extensions to the +specified encoding type. EMMime-enc/EM is the mime encoding to use +for documents containing the EMextension/EM. This mapping is added +to any already in force, overriding any mappings that already exist +for the same EMextension/EM. -The AddEncoding directive adds to the list of filename extensions which -filenames may end in for the specified encoding type. EMMime-enc/EM -is the mime encoding to use for documents ending in EMextension/EM. Example: -BLOCKQUOTECODE -AddEncoding x-gzip gzBR -AddEncoding x-compress Z +BLOCKQUOTECODE AddEncoding x-gzip gzBR AddEncoding x-compress Z /CODE/BLOCKQUOTE -This will cause files ending in .gz to be marked as encoded using the x-gzip -encoding, and .Z files to be marked as encoded with x-compress.P +This will cause filenames containing the .gz extension to be marked as +encoded using the x-gzip encoding, and filenames containing the .Z +extension to be marked as encoded with x-compress.P Old clients expect CODEx-gzip/CODE and CODEx-compress/CODE, however the standard dictates that they're equivalent to CODEgzip/CODE @@ -131,6 +146,11 @@ for these two specific encodings. More recent encodings, such as CODEdeflate/CODE should be specified without the CODEx-/CODE. +P + +STRONGSee also/STRONG: A HREF=#multipleextFiles with +multiple extensions/A + PHR H2A NAME=addhandlerAddHandler/A/H2 @@ -162,16 +182,25 @@
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
coar98/07/10 06:33:10 Modified:htdocs/manual/mod mod_mime.html Log: Add a missing 'Override' clause. PR: 2582 Submitted by: Andrew Gillespie [EMAIL PROTECTED] Reviewed by: Ken Coar Revision ChangesPath 1.22 +4 -0 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.21 retrieving revision 1.22 diff -u -r1.21 -r1.22 --- mod_mime.html 1998/05/20 14:12:58 1.21 +++ mod_mime.html 1998/07/10 13:33:09 1.22 @@ -144,6 +144,10 @@ REL=Help STRONGContext:/STRONG/A server config, virtual host, directory, .htaccessBR A + HREF=directive-dict.html#Override + REL=Help +STRONGOverride:/STRONG/A FileInfoBR +A HREF=directive-dict.html#Status REL=Help STRONGStatus:/STRONG/A BaseBR
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
ben 98/04/13 04:42:20 Modified:htdocs/manual/mod mod_mime.html Log: Fix grammar and layout error. Revision ChangesPath 1.20 +2 -2 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.19 retrieving revision 1.20 diff -u -r1.19 -r1.20 --- mod_mime.html 1998/02/12 01:14:36 1.19 +++ mod_mime.html 1998/04/13 11:42:20 1.20 @@ -277,8 +277,8 @@ PRE ForceType image/gif /PRE -PNote that this will override any filename extensions that might -media type./P +PNote that this will override any filename extensions that might determine +the media type./PHR H2A name=sethandlerSetHandler/A/H2
cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
dgaudet 98/02/11 17:14:37 Modified:htdocs/manual/mod mod_mime.html Log: doc the addencoding mess Revision ChangesPath 1.19 +15 -1 apache-1.3/htdocs/manual/mod/mod_mime.html Index: mod_mime.html === RCS file: /export/home/cvs/apache-1.3/htdocs/manual/mod/mod_mime.html,v retrieving revision 1.18 retrieving revision 1.19 diff -u -r1.18 -r1.19 --- mod_mime.html 1998/02/05 20:04:56 1.18 +++ mod_mime.html 1998/02/12 01:14:36 1.19 @@ -117,7 +117,21 @@ /CODE/BLOCKQUOTE This will cause files ending in .gz to be marked as encoded using the x-gzip -encoding, and .Z files to be marked as encoded with x-compress.PHR +encoding, and .Z files to be marked as encoded with x-compress.P + +Old clients expect codex-gzip/code and codex-compress/code, +however the standard dictates that they're equivalent to codegzip/code +and codecompress/code respectively. Apache does content encoding +comparisons by ignoring any leading codex-/code. When responding +with an encoding Apache will use whatever form (i.e. codex-foo/code +or codefoo/code) the client requested. If the client didn't +specifically request a particular form Apache will use the form given by +the codeAddEncoding/code directive. To make this long story short, +you should always use codex-gzip/code and codex-compress/code +for these two specific encodings. More recent encodings, such as +codedeflate/code should be specified without the codex-/code. + +PHR H2A name=addhandlerAddHandler/A/H2
