httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cliff Skolnick <>
Subject WWW Form Bug Report: "application/x-compress and application/x-gzip in mime.types cause problems" on Solaris 2.x (fwd)
Date Wed, 17 Jul 1996 19:02:16 GMT

More conf file cleanup (maybe)

Cliff Skolnick, CIO
Organic Online, Inc.       ** we're hiring **           (415) 278-5650
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759

---------- Forwarded message ----------
Date: Wed Jul 17  3:08:28 1996
Subject: WWW Form Bug Report: "application/x-compress and application/x-gzip in mime.types
cause problems" on Solaris 2.x

Operating system: Solaris 2.x, version: 
Version of Apache Used: 1.0.0 and 1.1.1
Extra Modules used: for 1.1.1 only default (as distributed) modules used
URL exhibiting problem: 

for a file foo.*.Z or foo.*.gz
(where * is eg. 'ps' or 'txt')
the content-type gets set to resp.
application/x-compress or application/x-gzip
and the 'real' type is ignore.

The header of a HEAD request contains eg.

Content-type: application/x-gzip
Content-encoding: x-gzip

The reason seems to be that the mime.types file
in the conf directory as distributed contains
the lines

  application/x-compress          Z
  application/x-gzip              gz

which are still used for the content-type, even
if lines

  AddEncoding x-compress Z
  AddEncoding x-gzip gz

are present in the srm.conf file.

The simple way to fix this is to delete the
application/* lines from the mime.types file.

The nice way to fix this seems to be to fix
mod_mime.c in such a way that a suffix can
not at the same time be used _both_ for
Content-Type _and_ Content-Encoding (and, I
suppose also Content-Language), butonly for
one of Content-Type, Content-Language
of Content-Encoding, where Content-Encoding
and Content-Language take preference over




View raw message