Re: Unknown content types

On Wednesday, July 9, 2003, 10:09:51 PM, Julian wrote:

JR> (my personal preference would be alternative 2 because it doesn't
JR> require to special-case one particular MIME type).

A good idea in general, except that this particular media type has
been created for that special case.

>> The "octet-stream" subtype is used to indicate that a body contains
>> arbitrary binary data.

>> The recommended action for an implementation that receives
>> application/octet-stream mail is to simply offer to put the data in
>> a file, with any Content-Transfer-Encoding undone, or perhaps to
>> use it as input to a user-specified process.
http://www.ietf.org/rfc/rfc2046.txt

Hmm this text was also in 1521 and is becoming a fixture:

>> RFC 1341 also defined the use of a "NAME" parameter which gave a
>> suggested file name to be used if the data were to be written to a
>> file. This has been deprecated in anticipation of a separate
>> Content-Disposition header field, to be defined in a subsequent
>> RFC.


-- 
 Chris                            mailto:chris@w3.org