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 1d4067ce49d5 CAMEL-23532: docs - sync camel-vertx-websocket / 
camel-atmosphere-websocket 4.14 upgrade-guide entry to main (#23353)
1d4067ce49d5 is described below

commit 1d4067ce49d5752365b02ead3433e8b59c19804d
Author: Andrea Cosentino <[email protected]>
AuthorDate: Wed May 20 10:27:26 2026 +0200

    CAMEL-23532: docs - sync camel-vertx-websocket / camel-atmosphere-websocket 
4.14 upgrade-guide entry to main (#23353)
    
    The 4.14.x backport (#23352) adds the HeaderFilterStrategy upgrade-guide
    note for camel-vertx-websocket and camel-atmosphere-websocket to
    camel-4x-upgrade-guide-4_14.adoc on the camel-4.14.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_14.adoc on main. (camel-iggy is not
    part of the 4.14.x backport because the component does not exist on that
    branch.)
    
    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_14.adoc       | 19 +++++++++++++++++++
 1 file changed, 19 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 eed28e0a9adb..7bc6f56b514a 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
@@ -283,3 +283,22 @@ aligning the component with the rest of the Camel 
component catalog (`camel-kafk
 `camel-coap`, `camel-google-pubsub`, ...). Routes that relied on passing 
through these header
 names from XMPP messages can supply a custom `headerFilterStrategy` to restore 
the previous
 behaviour.
+
+=== 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.

Reply via email to