[ 
https://issues.apache.org/jira/browse/CAMEL-7152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14632364#comment-14632364
 ] 

ASF GitHub Bot commented on CAMEL-7152:
---------------------------------------

GitHub user rbudzko opened a pull request:

    https://github.com/apache/camel/pull/566

    CAMEL-7152

    HttpProducer loses response data (specifically which hea…ders where 
returned):
    
    1) Added copyHeaders to http and http4 components
    2) Fixed some "online" tests which were outdated

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/rbudzko/camel master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/566.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #566
    
----
commit 6ca2e6f1825fc99a0149b09d986d95d24d1302d4
Author: Robert Budźko <[email protected]>
Date:   2015-07-18T10:35:47Z

    CAMEL-7152 - HttpProducer loses response data (specifically which headers 
where returned):
    
    1) Added copyHeaders to http and http4 components
    2) Fixed some "online" tests which were outdated

----


> HttpProducer loses response data (specifically which headers where returned)
> ----------------------------------------------------------------------------
>
>                 Key: CAMEL-7152
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7152
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-http, camel-http4
>    Affects Versions: 2.12.2
>            Reporter: Yannick Menager
>            Priority: Minor
>             Fix For: Future
>
>
> HTTPProducer is currently copying all the older headers from IN onto the OUT.
> This means that after doing an HTTP call, there is *no way* to know which 
> headers where returned by destination server, and which were there originally.
> In my case this is disastrous because I need to do an HMAC which include all 
> headers :(
> Please add an HttpEndpoint Options which allows to disable that behaviour and 
> not copy any old headers from IN. (and yes in that case the original headers 
> would get lost, but then the developer can just preserve whatever he needs by 
> storing the data in the exchange properties)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to