www/apache
1
0
Fork 0
mirror of https://github.com/apache/httpd.git synced 2026-01-06 09:01:14 +03:00
Code Activity

it's not the MIME RFC, but the HTTP RFC ;-)

Browse Source 
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
This commit is contained in:
André Malo
2002-12-15 16:12:34 +00:00
parent 61f472ac2a
commit 022336ac72
2 changed files with 20 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/manual/mod/mod_mime.html.en
View File

@@ -142,17 +142,17 @@
designed for transmitting a binary file in an ASCII (text)
format.</p>
<p>The <cite>MIME RFC</cite> puts it this way:</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>
<p>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.</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

20
docs/manual/mod/mod_mime.xml
View File

@@ -115,17 +115,17 @@ module="mod_mime_magic">MimeMagicFile</directive></seealso>
designed for transmitting a binary file in an ASCII (text)
format.</p>
<p>The <cite>MIME RFC</cite> puts it this way:</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>
<p>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.</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