MIME RFC nit????

Thread View: comp.mail.mime

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Warner Losh Mon, 28 Dec 1992 02:11

Author: Warner Losh
Date: Mon, 28 Dec 1992 02:11

25 lines
1143 bytes

mh 6.8 barfs on the following header:

Content-Type: message/external-body; access-type=local-file;
	name=/x/ap1/imp/Mail/inbox/29

but it does accept the following header:

Content-Type: message/external-body; access-type=local-file;
	name="/x/ap1/imp/Mail/inbox/29"

RFC1341 uses the following example (on page 40, ASCII version):

Content-Type: message/external-body; access-type=local-file;
	name=/u/nsb/Me.gif

It would seem to me that this example is in error, in light of the
parameter definitions on page 7, listing "/" as a tspecial, thus in
need of quoting.

Is this nit old news?  Does anybody care?

Warner
-- 
Warner Losh		imp@boulder.parcplace.COM	ParcPlace Boulder
I've almost finished my brute force solution to subtlety.

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads