httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Burry" <>
Subject Re: Apache q for site.
Date Tue, 04 Feb 2003 18:58:43 GMT
I've seen the exact same problem, and diagnosed it as the same issue.  It
would be very nice to have the default apache installation handle this
properly, to prevent the dumb we-think-we're-smarter-than-you browsers from
renaming files...  if not by monkeying with the mime types file for pureness
reasons, then at least by adding config params in the default httpd.conf.


----- Original Message -----
From: "William A. Rowe, Jr." <>
To: <>; <>
Sent: Tuesday, February 04, 2003 10:20 AM
Subject: Re: Apache q for site.

> An answer to a user question (and a gripe from me since I've hit this
> problem myself on;
> > [the links] point to .tar.gz files, which exist.  When they are clicked
> > however, they are being renamed to .tar.tar files. Any ideas?
> Renamed by the browser, not the server.
> Check in mime.types that we have content types for .tar *and* .gz.  The
> default defines only .tar, so we return application/x-tar.  If it included
> the *final* pathname element determines the mime type, which would
> be application/x-gzip.
> Almost makes you wish for application/x-gtar or something.  You can only
> count on gnu tar to support tar -z.
> Anyways, because the content type is application/x-tar, and the browser
> sees the *final* extension is .gz, it is choosing to replace .gz with .tar
> even adding another .tar (e.g., .tar.gz.tar which I've seen also.)
> Seems like the ASF needs to choose between removing application/x-tar
> or adding application/x-gzip in the default mime types.  Sure, we have a
> general policy against adding x- extentions, but by adding one, we open
> ourselves up to problems. :-)
> Bill

View raw message