Gili wrote:
> Craig McClanahan (via Nabble) wrote:
> > Binary entities will work just fine with multipart/mixed, just like
> they
> > work fine on individual entities with media types like
> > "application/octet-stream".
>
> Yes, but it turns out that the content-type is not enough. What
> Content-Transfer-Encoding does jersey-multipart use by default?
> http://en.wikipedia.org/wiki/MIME#Content-Transfer-Encoding
>
It doesn't set this header by default -- and neither does the rest of
Jersey for non-multipart data -- meaning no transfer encoding is done.
Email servers originally had to deal with this kind of thing because
they transmitted data across 7-bit paths (remember "even parity" and
"odd parity" settings on COM ports? :-). They are pretty much unneeded
across 8-bit paths like TCP-IP sockets.
You should take a look at the HTTP 1.1 spec[1] for the details of how
these headers are used differently in HTTP than in email ... in
particular see sections 3.6, 14.15, 19.1, and (especially) 19.4.5.
> Gili
>
Craig
[1[
http://www.ietf.org/rfc/rfc2616.txt
> ------------------------------------------------------------------------
> View this message in context: Re: [Jersey] Sending binary files over
> multipart/mixed
> <http://n2.nabble.com/Sending-binary-files-over-multipart-mixed-tp1573660p1573792.html>
> Sent from the Jersey mailing list archive
> <http://n2.nabble.com/Jersey-f576304.html> at Nabble.com.