httpd-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: apache-1.3/htdocs/manual/mod mod_mime.html
Date Thu, 12 Feb 1998 01:14:37 GMT
dgaudet     98/02/11 17:14:37

  Modified:    htdocs/manual/mod mod_mime.html
  doc the addencoding mess
  Revision  Changes    Path
  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 @@
   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><HR>
  +encoding, and .Z files to be marked as encoded with x-compress.<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 (i.e. <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>.
   <H2><A name="addhandler">AddHandler</A></H2>

View raw message