From fd2bdea98eb4e88e6fb6e2654f7f85728d6cf358 Mon Sep 17 00:00:00 2001 From: Andre Malo Date: Sun, 15 Dec 2002 16:12:34 +0000 Subject: [PATCH] it's not the MIME RFC, but the HTTP RFC ;-) updated the quotation to be quoted from RFC 2616 git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@97922 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_mime.html.en | 22 +++++++++++----------- docs/manual/mod/mod_mime.xml | 22 +++++++++++----------- 2 files changed, 22 insertions(+), 22 deletions(-) diff --git a/docs/manual/mod/mod_mime.html.en b/docs/manual/mod/mod_mime.html.en index 108db445bf..7595b41f32 100644 --- a/docs/manual/mod/mod_mime.html.en +++ b/docs/manual/mod/mod_mime.html.en @@ -142,17 +142,17 @@ designed for transmitting a binary file in an ASCII (text) format.

-

The MIME RFC puts it this way:

- -
-

The Content-Encoding entity-header field is used as a - modifier to the media-type. When present, its value indicates - what additional content coding has been applied to the - resource, and thus what decoding mechanism must be applied in - order to obtain the media-type referenced by the Content-Type - header field. The Content-Encoding is primarily used to allow - a document to be compressed without losing the identity of - its underlying media type.

+

The HTTP/1.1 + RFC, section 14.11 puts it this way:

+ +
+

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.

By using more than one file extension (see section above about multiple file diff --git a/docs/manual/mod/mod_mime.xml b/docs/manual/mod/mod_mime.xml index ba1a1d4c47..f24a41d262 100644 --- a/docs/manual/mod/mod_mime.xml +++ b/docs/manual/mod/mod_mime.xml @@ -115,17 +115,17 @@ module="mod_mime_magic">MimeMagicFile designed for transmitting a binary file in an ASCII (text) format.

-

The MIME RFC puts it this way:

- -
-

The Content-Encoding entity-header field is used as a - modifier to the media-type. When present, its value indicates - what additional content coding has been applied to the - resource, and thus what decoding mechanism must be applied in - order to obtain the media-type referenced by the Content-Type - header field. The Content-Encoding is primarily used to allow - a document to be compressed without losing the identity of - its underlying media type.

+

The HTTP/1.1 + RFC, section 14.11 puts it this way:

+ +
+

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.

By using more than one file extension (see