On Jun 15, 7:18pm, [EMAIL PROTECTED] wrote: > There are not supposed to be mime types listed for .Z > and .gz files because the default config file contains > AddEncoding directives for those. You should be getting > a mime type of something (depending on if it is the default, > if there are any mime types for other extensions, etc.) > with an encoding of x-compress or x-gzip.
On Jun 15, 7:23pm, [EMAIL PROTECTED] wrote: > As Marc pointed out, .Z and .gz don't properly identify > content types, but rather content-encodings. Remove the > AddType directives you inserted for these, and make sure > your server config files include > > AddEncoding x-compress Z > AddEncoding x-gzip gz > > Reload the server and try to fetch a .tar, .tar.Z, and a > .tar.gz file. All should show up as application/x-tar > with the Content-encoding response header missing, > "x-compress," or "x-gzip" respectively. If you don't get > these, your server is probably misconfigured. Ok, yes AddEncoding works better. It would be nice if these encodings could be added in a more foolproof than expecting people to copy them from a default .conf file. Also, I just noticed that the reason that the '.gz' file was always coming up as application/octet-stream was because it was coming from a CGI script. I'm sorry I didn't notice that and that I included it in my bug report. Thanks for your prompt replies. You can go ahead and close it. - Dave Dykstra
