oscerd opened a new pull request, #24409: URL: https://github.com/apache/camel/pull/24409
## Backport of #24406 Cherry-pick of #24406 onto `camel-4.18.x` (targeting the 4.18.4 release). **Original PR:** #24406 — CAMEL-23891: camel-mail - filter Camel internal headers in MimeMultipartDataFormat unmarshal **Original author:** @oscerd **Target branch:** `camel-4.18.x` ### What changed `MimeMultipartDataFormat` unmarshalling (`headersInline=true`) now aligns with the camel-mail consumer: internal Camel headers (`Camel*`, matched case-insensitively) present in the external MIME headers are no longer copied verbatim onto the Camel message. Ordinary application headers (e.g. `X-...`) continue to pass through unchanged. `copyNonStandardHeaders()` delegates to `DefaultHeaderFilterStrategy.applyFilterToExternalHeaders(...)` on the inbound path, consistent with the `MailHeaderFilterStrategy` already applied by the consumer. ### Backport notes - Code + unit test cherry-picked from the merged commit; verified to apply cleanly on `camel-4.18.x` (the `HeaderFilterStrategy` SPI and the `direct:unmarshalonlyinlineheaders` test route already exist on the branch). - The upgrade-guide entry is intentionally **not** included here: per project policy the upgrade-guide history is canonical on `main` (the `camel-4x-upgrade-guide-4_22.adoc` note lives on `main`; the 4.18-line note is handled as a separate doc-sync on `main`). JIRA: https://issues.apache.org/jira/browse/CAMEL-23891 🤖 Generated with [Claude Code](https://claude.com/claude-code) on behalf of Andrea Cosentino -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
