[
https://issues.apache.org/jira/browse/CAMEL-13116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16751031#comment-16751031
]
Önder Sezgin edited comment on CAMEL-13116 at 1/24/19 11:43 AM:
----------------------------------------------------------------
0 - I am neutral. more use cases would be better. However, it is simple
already, no reason no to have it.
was (Author: onders):
0 - I am neutral. more use cases would be better.
> DefaultHeaderFilterStrategy match action configurable
> -----------------------------------------------------
>
> Key: CAMEL-13116
> URL: https://issues.apache.org/jira/browse/CAMEL-13116
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Aniol Massana
> Priority: Minor
> Labels: pull-request-available
>
> The Exchange headers are sent to target systems in some components such as
> JMS (as JMS message headers), HTTP (as HTTP headers).
> In order to send only some of the existing Exchange headers, without removing
> the undesired ones so they are available later on on the route, a filter
> strategy kicks in.
> The current implementation of the DefaultHeaderFilterStrategy class match
> action removes the headers you configure, so is exactly the reverse of this
> use case.
> With this modification, you'd keep some headers and you'd avoid sending
> anything not matched, preventing any information to be leaked.
> The default value for this new setting keeps the current behaviour, so it
> should be safe to be introduced.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
