[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: "prefix" area in multipart message
>Leaving out the first boundary is particularly appealing, because it
>means that you can achieve essentially the functionality of the current
>"prefix" by simply starting with a blank line to indicate that the first
>encapsulation has no headers and has no content-type, encoding, etc. Of
>course, the current draft of the RFC says that a few such headers are
>REQUIRED. Perhaps we should relax this requirement?
By leaving out the encapsulation marker at the prefix area *may* create
an ambiguity. The encapsulation marker is used as the beginning of the
body part header especially for the first body part. Consider the
Content-Type: multipart; 1
Without the encapsulation marker, it is hard to tell if the prefix area
contains "testing." or "Content-Type: balh1..."