general/1439: Archives downloaded via HTTP not recognized by Winzip

[Jim Patterson <Ji...@Cognos.COM>]

>Number:         1439
>Category:       general
>Synopsis:       Archives downloaded via HTTP not recognized by Winzip
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          support
>Submitter-Id:   apache
>Arrival-Date:   Thu Nov 20 10:40:00 PST 1997
>Last-Modified:
>Originator:     Jim.Patterson@Cognos.COM
>Organization:
apache
>Release:        1.3b3
>Environment:
Windows NT 5.0 Beta
Netscame Communicator 4.04
Winzip version 6.2
>Description:
There seems to be a mismatch between the filenames stored on your server and 
what comes back to my browser when I download the .tar.gz archives from your
web site. This arises when using the "HTTP" download; I'm reasonably certain 
that it would not occur with an FTP download.

In this particular instance, I downloaded the new beta apache_1.3b3.tar.gz but
when Winzip was asked to load it after the download, I get an error from Winzip 
saying "error reading header after 0 entries".

If I look for the saved file after the download, I find a file called 
apache_1.3b3_tar.tar which is NOT what it was called in the directory listing.
If I rename it back to apache_1.3b3.tar.gz and then open it with Winzip, all
is well. So, it looks like the name passed back along with the file was somehow
mangled, which causes a problem for tools like Winzip.
>How-To-Repeat:
Using Communicator and Winzip under Windows 95 or NT, download an archive e.g. 
apache_1.3b3.tar.gz from your site.
>Fix:
Look at your server for how you are mapping file types. It seems to be a
configuration problem of some kind.

If the server always likes to translate filenames with multiple separators (dots)
for the benefit of those DOS users that don't seem to go away, maybe the solution
would be to translate .tar.gz to .tgz which Winzip and Gnu's gzip/gunzip both
recognize.
%0
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]