camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-11425) Camel Olingo needs a way to dynamically set and receive HTTP headers
Date Tue, 11 Jul 2017 15:02:00 GMT

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

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

GitHub user sarhaynes opened a pull request:

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

    CAMEL-11425 Add dynamic HTTP header capability on producer endpoints.

    

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

    $ git pull https://github.com/sarhaynes/camel CAMEL-11425

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

    https://github.com/apache/camel/pull/1818.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 #1818
    
----
commit c32d22f43a0cbcbcd2281c9625e35defdaacfb56
Author: Sean Haynes <s.a.haynes@ieee.org>
Date:   2017-07-11T14:56:03Z

    CAMEL-11425 Add dynamic HTTP header capability on producer endpoints.

----


> Camel Olingo needs a way to dynamically set and receive HTTP headers
> --------------------------------------------------------------------
>
>                 Key: CAMEL-11425
>                 URL: https://issues.apache.org/jira/browse/CAMEL-11425
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-olingo2
>    Affects Versions: 2.17.7, 2.19.0
>            Reporter: Sean Haynes
>   Original Estimate: 48h
>  Remaining Estimate: 48h
>
> Our interface with SAP Netweaver Gateway requires that we request a CSRF token and then
pass that value to future calls associated with our transaction.  The current design of the
camel-olingo2 component only allows us to set headers at component level.  This change will
allow the user to set headers at the endpoint level prior to calling the endpoint and receive
the response headers after endpoint is called.  I have already created a version of the component
that supports this change.  I will submit this change for approval shortly...



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message