[Top] [All Lists]

Re: Is Content-type an RFC822 "structured header"?

1999-05-24 04:12:36
In <v04204d02b36b4173d020(_at_)resnick2(_dot_)qualcomm(_dot_)com> Pete Resnick 
<presnick(_at_)qualcomm(_dot_)com> writes:

On 5/21/99 at 10:43 AM +0000, Charles Lindsey wrote:

  Content-type: image/tiff; boundary=

Then you had:

Content-type: image/

Now, the latter is also a legal RFC 2045 Content-Type line, but it is 
not semantically identical to the first. In the former, the boundary 


In the latter, the boundary is:

longboundarystr    ingwrappedtonextli    netolimitlinelength

OK. Point taken. If that was indeed the boundary in some multipart (do
image/tiffs have boundaries?), then the boundary actually written in the
message would have to be

--longboundarystr    ingwrappedtonextli    netolimitlinelength

complete with exactly the correct amount of SPs.

Charles H. Lindsey ---------At Home, doing my own thing------------------------
Email:     chl(_at_)clw(_dot_)cs(_dot_)man(_dot_)ac(_dot_)uk  Web:
Voice/Fax: +44 161 437 4506      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9     Fingerprint: 73 6D C2 51 93 A0 01 E7  65 E8 64 7E 14 A4 AB A5