From 3deaea9e260f1d9e3e9ae224000d1ccfb7665d6c Mon Sep 17 00:00:00 2001 From: Andrea Cosentino Date: Sun, 19 Jul 2026 16:19:29 +0200 Subject: [PATCH] CAMEL-24085: Sync IronMQ envelope header-filtering upgrade notes to 4_18 and 4_14 guides The camel-ironmq message envelope header-filtering change (CAMEL-24085) is backported to 4.18.4 and 4.14.9. Per the backport upgrade-guide policy, add the matching notes to the 4_18 and 4_14 upgrade guides on main (the 4_22 note shipped with the main fix PR). Co-Authored-By: Claude Fable 5 Signed-off-by: Andrea Cosentino --- .../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 10 ++++++++++ .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 10 ++++++++++ 2 files changed, 20 insertions(+) diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc index ff6f485b2fe5a..b2eebbb02085d 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc @@ -34,6 +34,16 @@ content-mode / HTTP header path. Ordinary CloudEvent extension attributes are unaffected. If a route relied on `Camel*`-named fields being propagated from the structured payload, set them explicitly after consuming the event. +=== camel-ironmq - message envelope header filtering + +When consuming a message with `preserveHeaders=true`, the IronMQ consumer now applies a `HeaderFilterStrategy` to +the header entries embedded in the JSON message envelope before mapping them onto the Camel message. Camel-internal +headers (the `Camel*` namespace, matched case-insensitively) present in the envelope are no longer mapped onto the +message, consistent with the inbound header filtering performed by other consumers. + +Ordinary application headers are unaffected. If a route relied on `Camel*` headers being propagated from the +message envelope, set them explicitly after consuming the message. + === camel-azure-eventhubs - producer now filters Camel-internal headers The `azure-eventhubs` producer now applies a `DefaultHeaderFilterStrategy` to the headers copied onto diff --git a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc index 8a54c092b7646..e36e04c77e25b 100644 --- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc +++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc @@ -61,6 +61,16 @@ content-mode / HTTP header path. Ordinary CloudEvent extension attributes are unaffected. If a route relied on `Camel*`-named fields being propagated from the structured payload, set them explicitly after consuming the event. +=== camel-ironmq - message envelope header filtering + +When consuming a message with `preserveHeaders=true`, the IronMQ consumer now applies a `HeaderFilterStrategy` to +the header entries embedded in the JSON message envelope before mapping them onto the Camel message. Camel-internal +headers (the `Camel*` namespace, matched case-insensitively) present in the envelope are no longer mapped onto the +message, consistent with the inbound header filtering performed by other consumers. + +Ordinary application headers are unaffected. If a route relied on `Camel*` headers being propagated from the +message envelope, set them explicitly after consuming the message. + === camel-azure-eventhubs - producer now filters Camel-internal headers The `azure-eventhubs` producer now applies a `DefaultHeaderFilterStrategy` to the headers copied onto