You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Roman Kalukiewicz (JIRA)" <ji...@apache.org> on 2007/12/04 10:56:27 UTC

[jira] Commented: (CAMEL-254) Support for http request headers for http component

    [ https://issues.apache.org/activemq/browse/CAMEL-254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40776 ] 

Roman Kalukiewicz commented on CAMEL-254:
-----------------------------------------

Maybe we should exclude some of headers by default like content-length or host? On the other hand maybe it will be required by someone?
Or maybe some flag?

To show the problem there is a code snippet that could lead to a problem:
{code}
from("direct:start").to("http://host:1234/a").to("http://host:1234/b");
{code}

After first http invocation we have {{content-length}} header set and when we execute the second http endpoint this header is propagated and {{/b}} endpoint is fooled by wrong value in {{content-length}} header.

On the other hand maybe it is a feature we shouldn't worry about -- header set, header used..

> 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.