From: Steinar Bang <sb@metis.no>
Subject: Re: Send compressed postscript as attachment?
Date: 10 Jan 2001 09:27:50 +0100 [thread overview]
Message-ID: <whr92bak1l.fsf@viffer.computas.no> (raw)
In-Reply-To: <vaf1yucnvsz.fsf@lucy.cs.uni-dortmund.de>
>>>>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann):
> On 09 Jan 2001, Matthias Wiehl wrote:
>> Thus, I'd suggest specifying "application/postscript" as
>> content-type for your file.
> But that doesn't generate any additional MIME header that says that
> the stuff is gzip compressed. I think that something should be
> there. It's not Content-Transfer-Encoding, but some other header.
> Sadly, I forget which one it is.
HTTP defines the header "content-coding", which may have a value of
"zip" or "x-gzip":
<http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.5>
But I don't know if this header has been included into MIME proper,
or if it's used by any mail programs.
next prev parent reply other threads:[~2001-01-10 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 15:30 Kai Großjohann
2001-01-09 16:01 ` Matthias Wiehl
2001-01-09 23:35 ` Kai Großjohann
2001-01-10 8:27 ` Steinar Bang [this message]
2001-01-10 13:49 ` ShengHuo ZHU
2001-01-09 18:58 ` Jorge Godoy
2001-01-09 23:37 ` Kai Großjohann
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=whr92bak1l.fsf@viffer.computas.no \
--to=sb@metis.no \
/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).