You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2020/07/23 11:35:00 UTC

[jira] [Commented] (CAMEL-15332) Http Headerfilterstrategy

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

Andrea Cosentino commented on CAMEL-15332:
------------------------------------------

You can pass a custom httpFilterStrategy as uri option in camel-http. This is not a bug.

[https://github.com/apache/camel/blob/master/components/camel-http-common/src/main/java/org/apache/camel/http/common/HttpHeaderFilterStrategy.java]

You can create a filterStrategy like this and removing date. Then add that to the camel registry and reference it, but again it's not a bug.

https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.5

> Http Headerfilterstrategy
> -------------------------
>
>                 Key: CAMEL-15332
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15332
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-http
>         Environment: SAP Cloud platform integration
> I did also a dummy test http request using 2 headers: date & newdate
> While checking i see that date-header never arrives at destination!!! only the newdate-header comes true.
>            Reporter: Erik De Meyer
>            Priority: Minor
>
> Hi,
> I try to do an Http request API call for for a banking application in SAP Cloud platform integration.
> Therefore I need a mandatory header for security reasons: Date
> My issue is that the camel framework headerfilterstrategy filters out this header, so the request gives me an error:
> {"errors":[\{"code":"missingHeader","detail":"There is a missing mandatory header in the request: Date.","meta":{"header":"Date"}}]}
>  
> Is there any possibility to override his behavior with an javascript or groovyscript? 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)