W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > January to April 1997

Re: MIME multipart/* vs HTTP

From: Dave Kristol <dmk@bell-labs.com>
Date: Wed, 30 Apr 1997 11:55:51 -0400
Message-Id: <33676B87.41C67EA6@bell-labs.com>
To: Scott Lawrence <lawrence@agranat.com>
Cc: ipp@pwg.org, http-wg@cuckoo.hpl.hp.com
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/3169
Scott Lawrence wrote:
> [...]
> IPP> There was also a question about how to send binary data in a
> IPP> multipart/mixed, especially in the chunked case because there is
> IPP> no way to know if a CRLF in the midst of binary data is really a
> IPP> CRLF. Thus it is hard to find the boundary string.
>   CRLF is what it is - if it is in the binary data and is followed by
>   the specified boundary string and another CRLF then you are at the
>   end of the body part.  What is the question?
>   As I understand it, the selection of a boundary string in MIME is
>   already 'probabilistic'; the sender is responsible for choosing a
>   string that 'probably' won't appear in the body (I do not claim to
>   be an authority on MIME).

In my ignorance of MIME, I've been puzzled about this boundary
business.  Assuming each multipart contains a Content-Length header,
does it matter what the boundary is?  Can't the recipient just eat the
number of content bytes before looking for the next boundary?  If so,
the boundary strings don't have to be particularly clever, do they?

Dave Kristol
Received on Wednesday, 30 April 1997 09:06:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:19 UTC