Andrea Cosentino created CAMEL-23543:
----------------------------------------
Summary: camel-core - Investigate centralizing Camel* inbound
header filtering in DefaultHeaderFilterStrategy
Key: CAMEL-23543
URL: https://issues.apache.org/jira/browse/CAMEL-23543
Project: Camel
Issue Type: Improvement
Components: camel-core
Reporter: Andrea Cosentino
Follow-up from the CAMEL-23515 (camel-nats) and CAMEL-23516 (camel-xmpp) review
discussion.
Many components ship a dedicated {{HeaderFilterStrategy}} subclass purely to
filter out headers starting with {{Camel}} / {{camel}} / {{org.apache.camel.}}
in the inbound and outbound directions: camel-kafka, camel-mail, camel-coap,
camel-google-pubsub, camel-jms, camel-sjms, camel-nats, camel-xmpp, plus the
HTTP/REST family.
Proposal: investigate whether
{{org.apache.camel.support.DefaultHeaderFilterStrategy}} should filter the
{{Camel}} / {{camel}} / {{org.apache.camel.}} prefixes by default (at least on
the inbound direction), which would remove the need for most of these
per-component subclasses going forward.
Context / constraints:
* CAMEL-23379 changed the {{lowerCase}} default to {{true}} but deliberately
did NOT add inbound {{Camel*}} filtering to the base class.
* Changing the base default is a behavioural change that needs: an assessment
of the impact on the existing test suite, identification of components/routes
that legitimately propagate {{Camel*}} headers, an upgrade-guide entry, and PMC
sign-off.
* Per the review discussion, the per-component approach is kept for now
(consistent with what has already been done for many components); this ticket
tracks the longer-term consolidation for a future release on {{main}}.
_Raised by Claus Ibsen during PR #23283 review; logged by Claude Code on behalf
of Andrea Cosentino._
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
