[Tickets #7680] Re: gzip/bzip2 upload doubly compressed

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7680
------------------------------------------------------------------------------
  Ticket             | 7680
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | gzip/bzip2 upload doubly compressed
  Queue              | IMP
  Version            | HEAD
  Type               | Bug
-State              | Feedback
+State              | Not A Bug
  Priority           | 2. Medium
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2008-12-09 00:03) wrote:

> # file archive.tgz
> archive.tgz: gzip compressed data, from Unix, last modified: Mon Dec
> 8 11:28:54 2008

And this is correct.  This is a gzip'd file.  How can 'file' know what  
is inside the file without uncompressing it?  'file' simply guess what  
kind of data is in the file.

> Not much of a difference. So where is the MIME type sent to HORDE/IMP
> coming from?

The browser/OS.

> For a ".tgz", IMP receives "application/x-gtar" and for a ".tar.gz",
> it receives "application/x-gzip"

Technically, there is nothing wrong with application/x-gzip.  Because  
that is exactly what the file is.  On OS's like windows, there can  
only be a single extension.  So the MIME type 'application/x-gzip' is  
correct.  I realize Thunderbird is sending something different, but I  
don't necessarily agree with what they are doing (x-compressed-tar  
does not seem to be used by many people.).

So I think the previous analysis in this ticket remains.