W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 1998

Re: Issue: message/http or application/http

From: Nathaniel Borenstein <nsb@aa.fv.com>
Date: Mon, 2 Feb 1998 12:18:35 GMT
Message-Id: <IopPQ=_Mc5V201ZvE0@aa.fv.com>
To: "Roy T. Fielding" <fielding@kiwi.ics.uci.edu>, Jacob Palme <jpalme@dsv.su.se>
Cc: Jim Gettys <jg@pa.dec.com>, http-wg@cuckoo.hpl.hp.com, IETF working group on HTML in e-mail <mhtml@segate.sunet.se>
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/5331
Excerpts from mail: 2-Feb-98 Re: Issue: message/http or .. Jacob
Palme@dsv.su.se (1058*)

> However, it is probably not permitted to include Content-Encoding
> or Transfer-Encoding in headings transported through e-mail,
> even if the heading is of type message/http, since those encoding
> format may not be permitted in e-mail?

Sure, you could do that.  You'd just have to encode it a layer up.  If
you had the equivalent of:

	Content-type: message/http
	Content-Transfer-Encoding: binary

	[binary data]

and you wanted to send it through email as a message/http type, you
could do something like this:

	Content-type: message/rfc822
	Content-Transfer-Encoding: base64


When you decoded this, you'd have the original message/http data.  

What's less clear to me is *why* you'd want to do this....  -- Nathaniel
Imagination was given to man to compensate him for what he is not;
a sense of humor to console him for what he is.  -- Francis Bacon

Nathaniel Borenstein <nsb@fv.com>          |  FAQ & PGP key:
Chief Scientist, First Virtual Holdings    |  nsb+faq@nsb.fv.com
Received on Monday, 2 February 1998 08:51:59 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:04 UTC