From: Stephen Zander <gibreel@pobox.com>
Cc: Gnus Mailing List <ding@gnus.org>
Subject: Re: doubly-gzipped files
Date: 19 Nov 1998 20:40:20 -0800 [thread overview]
Message-ID: <87n25nvux7.fsf@wsfs05.mckesson.com> (raw)
In-Reply-To: "Edward J. Sabol"'s message of "Wed, 18 Nov 1998 10:38:19 -0500"
>>>>> "Edward" == Edward J Sabol <sabol@alderaan.gsfc.nasa.gov> writes:
Edward> How about at least turning off jka-compr when the
Edward> Content-Type is application/x-gzip or the filename
Edward> specified in the Content-Disposition ends with ".gz"? You
Edward> can do the same for uuencoded attachments where the
Edward> filename ends with ".gz" as well. That should catch just
Edward> about all cases where the problem arises.
Could you not just check the whether the attachment is compressed by
looking at the file? If the first two bytes are \037\213 then it's
likely that file was compressed with the gzip algorithm. Similarly,
if the file starts with \037\235, it's likely file was compressed
using LZW (aka compress).
Checking the Content-Type is good, but determination of filetype by
extension is *evil* :)
--
Stephen
---
Perl is really designed more for the guys that will hack Perl at least
20 minutes a day for the rest of their career. TCL/Python is more a
"20 minutes a week", and VB is probably in that "20 minutes a month"
group. :) -- Randal Schwartz
prev parent reply other threads:[~1998-11-20 4:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-16 13:25 Alexandre Oliva
1998-11-17 23:55 ` Lars Magne Ingebrigtsen
1998-11-18 15:38 ` Edward J. Sabol
1998-11-19 2:44 ` Lars Magne Ingebrigtsen
1998-11-20 4:40 ` Stephen Zander [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87n25nvux7.fsf@wsfs05.mckesson.com \
--to=gibreel@pobox.com \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).