[
https://issues.apache.org/activemq/browse/CAMEL-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40777
]
Guillaume Nodet commented on CAMEL-254:
---------------------------------------
We need to worry about that, as basic use case will fail.
There are at least two ways to solve the problem:
* do not include those http headers in the camel exchange
* do not use these headers when building the http request
I'm thinking we need to implement the second one, as if we don't, requests will
be unusable.
But the first option may be interesting to save bandwith and could be
controlled by a flag in the uri maybe.
Also, I suppose the same patch should be applied to the camel-jhc component,
which uses asynchronous nio.
> Support for http request headers for http component
> ---------------------------------------------------
>
> Key: CAMEL-254
> URL: https://issues.apache.org/activemq/browse/CAMEL-254
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-http
> Reporter: Roman Kalukiewicz
> Attachments: http-headers.patch
>
>
> Now there is no way to set http request headers via camel headers while
> response headers are available.
> This functionality is required when we want to send SOAP request via http
> component as there is SOAPAction header required.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
