This is an automated email from the ASF dual-hosted git repository.

davsclaus 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 3f589c0c5489 CAMEL-26922: camel-atmosphere-websocket - upgrade guide 
notes for 4.22.3 and 4.18.6 (#30190)
3f589c0c5489 is described below

commit 3f589c0c5489ef6bb65092b3492eb22b34d6c691
Author: Claus Ibsen <[email protected]>
AuthorDate: Mon Nov 16 14:34:15 2026 +0100

    CAMEL-26922: camel-atmosphere-websocket - upgrade guide notes for 4.22.3 
and 4.18.6 (#30190)
    
    Adds the upgrade guide notes for CAMEL-26922 (#29845, 
camel-atmosphere-websocket: the open, close and error events carry the query 
parameters of their own connection) to the guides of the maintenance lines it 
is backported to. The guides of all versions live on `main`, so the backports' 
notes are kept here too.
    
    - `camel-4x-upgrade-guide-4_22.adoc`, section "Upgrading from 4.22.2 to 
4.22.3"
    - `camel-4x-upgrade-guide-4_18.adoc`, section "Upgrading from 4.18.5 to 
4.18.6"
    
    _Claude Code on behalf of davsclaus_
    
    Co-Authored-By: Claude Opus 5.5 <[email protected]>
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc    | 14 ++++++++++++++
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc    | 14 ++++++++++++++
 2 files changed, 28 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 4bbc681f44c7..a3f44d146e5e 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
@@ -50,6 +50,20 @@ only the default port of `http` (80); to deliver to another 
port, list it explic
 
 A deployment that lists a bare host and receives asynchronous MDNs on a 
non-default port must add the port to the entry.
 
+=== camel-atmosphere-websocket - events carry the query parameters of their 
own connection
+
+With the `events` init-param of `CamelWebSocketServlet` set to `true`, the 
open, close and error event exchanges now carry
+the query parameters of the request that opened their websocket connection, 
with the names and values URL-decoded.
+This is also the case with the JSR 356 transport, which Atmosphere uses on 
current servlet containers, where the
+parameters of the connection did not reach its events before. Before, the 
event headers came from the last HTTP request
+that the servlet handled for the endpoint, and their values were not 
URL-decoded, so a route that used these headers
+can see different values. `WebsocketConsumer.sendEventNotification` takes the 
query parameters of the connection as a
+third argument.
+
+The query string of a request is also read more leniently: a parameter without 
a value (`?foo` or `?foo=`) gets an empty
+value, and a value that contains `=` is kept whole. Before, such a parameter 
made the request fail, and a value was cut at
+the first `=` it contained.
+
 === camel-azure-eventhubs - per-partition checkpoint counters and timer; 
checkpoint window boundary fix
 
 Several fixes from 4.22.x have been brought forward to 4.18.6 to give this 
change a sound base.
diff --git 
a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc 
b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
index 9132e46f0b7b..210a74b9feca 100644
--- a/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
+++ b/docs/user-manual/modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc
@@ -69,6 +69,20 @@ only the default port of `http` (80); to deliver to another 
port, list it explic
 
 A deployment that lists a bare host and receives asynchronous MDNs on a 
non-default port must add the port to the entry.
 
+=== camel-atmosphere-websocket - events carry the query parameters of their 
own connection
+
+With the `events` init-param of `CamelWebSocketServlet` set to `true`, the 
open, close and error event exchanges now carry
+the query parameters of the request that opened their websocket connection, 
with the names and values URL-decoded.
+This is also the case with the JSR 356 transport, which Atmosphere uses on 
current servlet containers, where the
+parameters of the connection did not reach its events before. Before, the 
event headers came from the last HTTP request
+that the servlet handled for the endpoint, and their values were not 
URL-decoded, so a route that used these headers
+can see different values. `WebsocketConsumer.sendEventNotification` takes the 
query parameters of the connection as a
+third argument.
+
+The query string of a request is also read more leniently: a parameter without 
a value (`?foo` or `?foo=`) gets an empty
+value, and a value that contains `=` is kept whole. Before, such a parameter 
made the request fail, and a value was cut at
+the first `=` it contained.
+
 === camel-azure-eventhubs - an event that completes when the checkpoint timer 
of its window has run is checkpointed
 
 With `checkpointBatchTimeout`, the consumer now starts a new checkpoint window 
when the timer of the current window

Reply via email to