Hi If anyone knows if HttpClient will consider contenttype charset when you use it's method to get the response body as a String, then we could use this one and expose it on the HttpOperationFailedException as well so you can use this instead of dealing with the charset convertions yourself
/Claus Ibsen Apache Camel Committer Blog: http://davsclaus.blogspot.com/ On Tue, Nov 25, 2008 at 11:40 AM, Claus Ibsen <[EMAIL PROTECTED]> wrote: > On Tue, Nov 25, 2008 at 11:34 AM, Trevv <[EMAIL PROTECTED]> wrote: >> >> >> Claus Ibsen-2 wrote: >>> Ah that would be nice to have the content type on the >>> HttpOperationException as well? >>> >>> But I guess in 99% converting to String would be fine as most servers >>> return a text/plain or text/html error page. >> Yes, but to convert bytes to String, you need to know the charset. >> >> The charset that was used by the Web server to encode the error page >> content might not be the same as your camel's JVM's default charset. > Yeah but that must be on the content type header right? > text/xml;charset=utf-8 or how this is normally specified? > >> >> Do you mind adding a JIRA ticket to add a getter on the >>> HttpOperationException for the content type. >> As an addition to CAMEL-1083, or as a completely new issue? > A new issue linking to 1083 would be good. > >> -- >> View this message in context: >> http://www.nabble.com/HttpProducer%3A-how-to-access-the-body-of-an-error-page--tp20475651s22882p20678642.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> >
