From: "Edward J. Sabol" <sabol@alderaan.gsfc.nasa.gov>
Subject: Re: doubly-gzipped files
Date: Wed, 18 Nov 1998 10:38:19 -0500 [thread overview]
Message-ID: <199811181538.KAA29104@alderaan.gsfc.nasa.gov> (raw)
In-Reply-To: <m3d86lub5u.fsf@sparky.gnus.org> (message from Lars Magne Ingebrigtsen on 18 Nov 1998 00:55:41 +0100)
Excerpts from mail: (18-Nov-98) Re: doubly-gzipped files by Lars Magne Ingebrigtsen
> On the one hand, it should be possible to say that the file should be saved
> to "something.gz" to signal that you want "something" to be gzipped. But if
> the thing already has been gzipped, and you just want to save it, that's
> not possible. So I don't know how to work around this problem...
How about at least turning off jka-compr when the Content-Type is
application/x-gzip or the filename specified in the Content-Disposition ends
with ".gz"? You can do the same for uuencoded attachments where the filename
ends with ".gz" as well. That should catch just about all cases where the
problem arises.
next prev parent reply other threads:[~1998-11-18 15:38 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 [this message]
1998-11-19 2:44 ` Lars Magne Ingebrigtsen
1998-11-20 4:40 ` Stephen Zander
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=199811181538.KAA29104@alderaan.gsfc.nasa.gov \
--to=sabol@alderaan.gsfc.nasa.gov \
/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).