Multipart REST responses should include "boundary" in Content-Type

When calling a REST service command such as "Blob.GetList", which returns a MIME multipart result, the MIME boundary is not specified in the response headers. This violates RFC2045, which requires a boundary parameter for multipart documents.

The Content-Type returned by "Blob.GetList":

Content-Type: multipart/mixed

The expected value:

Content-Type: multipart/mixed; boundary=the-boundary-value

This would make the HTTP response a valid MIME document, and would make it parseable by MIME tools.

See section 5, "Content-Type Header Field" of RFC2045:
http://www.ietf.org/rfc/rfc2045.txt

quote: 'For example, the "charset" parameter is applicable to any subtype of
"text", while the "boundary" parameter is required for any subtype of
the "multipart" media type.'

Note the "required" statement for multipart responses!