This is an automated email from the ASF dual-hosted git repository.
oscerd pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git
The following commit(s) were added to refs/heads/main by this push:
new 4b45e4bf0d9f CAMEL-23532: docs - sync camel-vertx-websocket /
camel-atmosphere-websocket / camel-iggy 4.18 upgrade-guide entry to main
(#23315)
4b45e4bf0d9f is described below
commit 4b45e4bf0d9f33e1506f2bd9e905ad540626aafa
Author: Andrea Cosentino <[email protected]>
AuthorDate: Tue May 19 13:46:22 2026 +0200
CAMEL-23532: docs - sync camel-vertx-websocket / camel-atmosphere-websocket
/ camel-iggy 4.18 upgrade-guide entry to main (#23315)
The 4.18.x backport (#23313) adds the HeaderFilterStrategy upgrade-guide
note to camel-4x-upgrade-guide-4_18.adoc on the camel-4.18.x branch. Per
the project policy, the version-specific upgrade guides on main are the
canonical history across all releases, so the same entry must also be
added to camel-4x-upgrade-guide-4_18.adoc on main.
Signed-off-by: Andrea Cosentino <[email protected]>
Co-authored-by: Claude Opus 4.7 (1M context) <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 29 ++++++++++++++++++++++
1 file changed, 29 insertions(+)
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 482df9442470..7dec0b2f0b32 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
@@ -518,3 +518,32 @@ behaviour.
The `camel-olingo2` and `camel-olingo4` component are deprecated.
This is due the Apache Olingo project is EOL and has been moved to the attic
and is no longer maintained.
+
+=== camel-vertx-websocket
+
+The `vertx-websocket` consumer now applies a `HeaderFilterStrategy` to the
WebSocket query and
+path parameters before mapping them into the Camel message headers. The new
default
+`VertxWebsocketHeaderFilterStrategy` filters headers starting with `Camel` /
`camel`
+(case-insensitive) in both the inbound and outbound directions, aligning the
component with the
+rest of the Camel component catalog (`camel-coap`, `camel-kafka`,
`camel-nats`, ...). A new
+`headerFilterStrategy` endpoint option is available; routes that relied on
receiving
+`Camel`-prefixed header names from WebSocket query or path parameters can
supply a custom
+`headerFilterStrategy` to restore the previous behaviour.
+
+=== camel-atmosphere-websocket
+
+The `atmosphere-websocket` consumer now applies the endpoint
`HeaderFilterStrategy` to the
+WebSocket query parameters before mapping them into the Camel message headers.
The inherited
+default `HttpHeaderFilterStrategy` filters headers starting with `Camel` /
`camel`
+(case-insensitive). Routes that relied on receiving `Camel`-prefixed header
names from WebSocket
+query parameters can supply a custom `headerFilterStrategy` to restore the
previous behaviour.
+
+=== camel-iggy
+
+The `iggy` consumer now applies a `HeaderFilterStrategy` to the Iggy message
user-headers before
+mapping them into the Camel message headers. The new default
`IggyHeaderFilterStrategy` filters
+headers starting with `Camel` / `camel` (case-insensitive) in both the inbound
and outbound
+directions, aligning the component with the rest of the Camel component
catalog. A new
+`headerFilterStrategy` endpoint option is available; routes that relied on
receiving
+`Camel`-prefixed user-header names from Iggy messages can supply a custom
`headerFilterStrategy`
+to restore the previous behaviour.
