[
https://issues.apache.org/activemq/browse/CAMEL-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Trev updated CAMEL-1119:
------------------------
Attachment: camel_1119_b.patch
This will be more self-explanatory if the field name is responseHeaders
instead of just headers. It will be obvious that responseHeaders is
closely associated with responseBody, and it will help distinguish these
headers from the several other kinds of headers that are found in Camel.
I don't know why I didn't name it this way in the first place. Must
have been operating with insufficient caffeine, I suppose.
Attached: [^camel_1119_b.patch]
> HttpProducer discards response headers, if response code >= 300
> ---------------------------------------------------------------
>
> Key: CAMEL-1119
> URL: https://issues.apache.org/activemq/browse/CAMEL-1119
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-http
> Affects Versions: 1.5.0
> Reporter: Trev
> Assignee: Claus Ibsen
> Attachments: camel_1119.patch, camel_1119_b.patch
>
>
> In Camel 1.4.0, when a Web server sends an error page to HttpProducer, the
> Camel route can access the response headers that were sent by the server. In
> Camel 1.5.0, these headers are discarded by HttpProducer, so the Camel route
> cannot access them.
> Camel 1.5.0 also discards the _content_ of the error page, but that was fixed
> in [CAMEL-1083|https://issues.apache.org/activemq/browse/CAMEL-1083].
> See discussion: [HttpProducer: how to access the body of an error
> page?|http://www.nabble.com/HttpProducer%3A-how-to-access-the-body-of-an-error-page--to20475651s22882.html]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
