From: wmperry@aventail.com (William M. Perry)
Cc: Ding mailing list <ding@gnus.org>
Subject: Re: OK, so how do I *use* MIME?
Date: 14 Jan 1999 11:01:48 -0500 [thread overview]
Message-ID: <86zp7ldes3.fsf@kramer.bp.aventail.com> (raw)
In-Reply-To: jari.aalto@poboxes.com's message of "14 Jan 1999 17:36:26 +0200"
jari.aalto@poboxes.com (Jari Aalto+list.ding) writes:
> * 1999-01-13 wmperry@aventail.com (William Perry) list.ding
> | ...The fact that
> | application/x-gzip64 is an abomination is a totally different problem. :)
>
> What is the proper MIME type for for base64 encoded gzip files ?
> I've also seen plain "application/gzip"
i assume one would need an appropriate content-transfer-encoding. Not a
content-type for this. So you would have:
Content-type: application/x-tar
Content-transfer-encoding: x-base64-gzip
[base64 gobbledygook]
I don't know if such a beast exists or not. Or just have a content-type of
application/octet-stream and a content-transfer-encoding of 'base64' and
let the user figure it out.
-Bill P.
next prev parent reply other threads:[~1999-01-14 16:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-12 16:34 Hrvoje Niksic
1999-01-13 18:33 ` Lars Magne Ingebrigtsen
1999-01-13 22:39 ` Hrvoje Niksic
1999-01-13 23:26 ` Lars Magne Ingebrigtsen
1999-01-14 10:09 ` Kai.Grossjohann
1999-01-14 10:26 ` William M. Perry
1999-01-14 16:17 ` Hrvoje Niksic
1999-01-14 19:17 ` Lars Magne Ingebrigtsen
1999-01-14 23:29 ` Hrvoje Niksic
1999-01-15 0:17 ` Lars Magne Ingebrigtsen
1999-01-15 1:22 ` Hrvoje Niksic
1999-01-15 15:15 ` Lars Magne Ingebrigtsen
1999-01-15 2:29 ` lconrad
1999-01-15 15:16 ` Lars Magne Ingebrigtsen
1999-01-15 9:11 ` Steinar Bang
1999-01-15 15:16 ` Lars Magne Ingebrigtsen
1999-01-15 18:26 ` Graham Murray
1999-01-15 15:43 ` Andrew Hobson
1999-01-15 16:03 ` Lars Magne Ingebrigtsen
1999-01-14 0:36 ` William M. Perry
1999-01-14 15:36 ` Jari Aalto+list.ding
1999-01-14 16:01 ` William M. Perry [this message]
1999-01-14 16:11 ` Richard Coleman
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=86zp7ldes3.fsf@kramer.bp.aventail.com \
--to=wmperry@aventail.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).