[
https://issues.apache.org/jira/browse/CAMEL-13116?focusedWorklogId=196176&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-196176
]
ASF GitHub Bot logged work on CAMEL-13116:
------------------------------------------
Author: ASF GitHub Bot
Created on: 08/Feb/19 11:31
Start Date: 08/Feb/19 11:31
Worklog Time Spent: 10m
Work Description: amassana commented on pull request #2753: CAMEL-13116 -
DefaultHeaderFilterStrategy match action configurable
URL: https://github.com/apache/camel/pull/2753
* filterOnMatch parameter added
* test cases
* documentation
* adapted to the new folder structure
* checkstyle validated
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 196176)
Time Spent: 10m
Remaining Estimate: 0h
> 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
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)
