Multipart HTTP and Content-Type

[David Hoyt]

We're sending multipart messages back to our netty http client and apparently
it doesn't like (valid) headers such as: Content-type:
multipart/x-mixed-replace; boundary=--myboundary--

I get an IllegalArgumentException: Invalid header syntax: --myboundary--

I don't need to actually parse the individual parts, but it should accept
that header.
-- 
View this message in context: http://n2.nabble.com/Multipart-HTTP-and-Content-Type-tp2790008p2790008.html
Sent from the Netty User Group mailing list archive at Nabble.com.