Re: comments? MIME types for HTTP
Tony Sanders <sanders@bsdi.com>
Errors-To: sanders@bsdi.com
Errors-To: sanders@bsdi.com
Message-id: <9308121552.AA13757@austin.BSDI.COM>
To: www-talk@nxoc01.cern.ch
Subject: Re: comments? MIME types for HTTP
In-Reply-To: Your message of Thu, 12 Aug 93 11:44:30 +0200.
Errors-To: sanders@bsdi.com
Reply-To: sanders@bsdi.com
Organization: Berkeley Software Design, Inc.
Date: Thu, 12 Aug 1993 10:52:17 -0500
From: Tony Sanders <sanders@bsdi.com>
Status: RO
> A good list of formats there. I have nothing against the list itself, but I
> noted 2 MIME types which I don't think are registered yet (based on the
> contents of ftp://isi.edu/in-notes/mime tree). They are
from file://venera.isi.edu/in-notes/mime/mime-types
remote-printing [RFC1486,MTR]
tiff Tag Image File Format [MTR]
> Further down, you talk about encodings. I would suggest the following
> alterations.
>
> encoding = Description
> gzip gz Gnu Zip Compressed
> zip zip zip Compressed
>
> As gz is now the extension for gzip files, and I don't feel that zip is really
> gzip compressed (at least I can't gunzip a zip archive, or make a zip archive
> with gzip)
You can gunzip a zip archive if it has a single element. But you are
correct, it's an archive format, not an encoding. I will fix that.
So it's now:
archive/zip zip zip Compressed
Thanks for pointing that out.
--sanders