Skip to content

CAMEL-24085: Sync IronMQ envelope header-filtering upgrade notes to 4_18 and 4_14 guides #24908

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
davsclaus merged 1 commit into from
Jul 19, 2026
Merged

CAMEL-24085: Sync IronMQ envelope header-filtering upgrade notes to 4_18 and 4_14 guides #24908

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_14.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
10 changes: 10 additions & 0 deletions docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down