Now I understand what you are meaning. The situation here is that the server is mixing mime message headers in http metadata (response headers). You are right that the whole mime message _should_ be in the payload (=http response body), but that server is managed by third party vendor so we don't have control to change that.
-ripok- Tatu Saloranta wrote: > > > So if there are headers that are logically part of the > mime message, they belong to payload (from httpclient > perspective); but if you were talking about http > headers, they'd be part of response metadata, not > payload. > > -- View this message in context: http://www.nabble.com/Whole-HTTP-response-as-InputStream--tp15759846p15845836.html Sent from the HttpClient-User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
