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 af18072feb2a CAMEL-24360: doc-sync backported upgrade-guide entries to
main
af18072feb2a is described below
commit af18072feb2a71c9801c89918f06947333247522
Author: Claus Ibsen <[email protected]>
AuthorDate: Thu Aug 6 12:43:28 2026 +0200
CAMEL-24360: doc-sync backported upgrade-guide entries to main
Add the UndertowHeaderFilterStrategy endpoint default upgrade-guide entry
to the 4.18 and 4.14 guides on main, keeping them in sync with the
backport PRs (#25379, #25381).
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Signed-off-by: Claus Ibsen <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc | 31 ++++++++++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 31 ++++++++++++++++++++++
2 files changed, 62 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 b79f499a92d6..fc33b266b7dd 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
@@ -1275,6 +1275,37 @@ Routes that intentionally relied on undertow mapping
`websocket.*` wire
headers in or out can supply a custom `headerFilterStrategy` endpoint option
to restore the previous behaviour.
+=== camel-undertow - UndertowHeaderFilterStrategy is now the endpoint default
+
+`UndertowEndpoint` defaulted its `headerFilterStrategy` to the base
+`HttpHeaderFilterStrategy`, and pushed that strategy into the
`DefaultUndertowHttpBinding`
+it creates lazily, overwriting the `UndertowHeaderFilterStrategy` that the
binding installs
+in its own constructor. The undertow-specific filtering was therefore not
applied on
+endpoint-configured routes.
+
+The endpoint now defaults to `UndertowHeaderFilterStrategy`, which makes two
already
+documented behaviours take effect:
+
+* The legacy `websocket.*` Exchange-header prefix, added to the in and out
filters in
+ 4.14.8 / 4.18.3 / 4.21.0 (see above), is now filtered at the undertow
+ transport boundary as described there.
+* Header names that undertow does not accept (those for which
+ `io.undertow.util.HttpString.tryFromString` returns `null`) are skipped when
mapping
+ external headers in, rather than being mapped onto the message.
+
+Ordinary application headers are unaffected, and Rest DSL consumers already
used an
+undertow-specific strategy (`UndertowRestHeaderFilterStrategy`) so their
behaviour does not
+change. Routes that relied on `websocket.*` headers crossing the undertow
boundary in either
+direction, and routes that relied on undertow-invalid header names being
mapped, can restore
+the previous behaviour by configuring `headerFilterStrategy` explicitly on the
endpoint:
+
+[source,java]
+----
+from("undertow:http://0.0.0.0:8080/foo?headerFilterStrategy=#myStrategy";)
+----
+
+Routes that already supply a custom `headerFilterStrategy` or a custom
`undertowHttpBinding`
+are unaffected.
=== camel-aws2-sqs
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 34e908bd9831..187a378e27b8 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
@@ -1605,6 +1605,37 @@ Routes that intentionally relied on undertow mapping
`websocket.*` wire
headers in or out can supply a custom `headerFilterStrategy` endpoint option
to restore the previous behaviour.
+=== camel-undertow - UndertowHeaderFilterStrategy is now the endpoint default
+
+`UndertowEndpoint` defaulted its `headerFilterStrategy` to the base
+`HttpHeaderFilterStrategy`, and pushed that strategy into the
`DefaultUndertowHttpBinding`
+it creates lazily, overwriting the `UndertowHeaderFilterStrategy` that the
binding installs
+in its own constructor. The undertow-specific filtering was therefore not
applied on
+endpoint-configured routes.
+
+The endpoint now defaults to `UndertowHeaderFilterStrategy`, which makes two
already
+documented behaviours take effect:
+
+* The legacy `websocket.*` Exchange-header prefix, added to the in and out
filters in
+ 4.14.8 / 4.18.3 / 4.21.0 (see above), is now filtered at the undertow
+ transport boundary as described there.
+* Header names that undertow does not accept (those for which
+ `io.undertow.util.HttpString.tryFromString` returns `null`) are skipped when
mapping
+ external headers in, rather than being mapped onto the message.
+
+Ordinary application headers are unaffected, and Rest DSL consumers already
used an
+undertow-specific strategy (`UndertowRestHeaderFilterStrategy`) so their
behaviour does not
+change. Routes that relied on `websocket.*` headers crossing the undertow
boundary in either
+direction, and routes that relied on undertow-invalid header names being
mapped, can restore
+the previous behaviour by configuring `headerFilterStrategy` explicitly on the
endpoint:
+
+[source,java]
+----
+from("undertow:http://0.0.0.0:8080/foo?headerFilterStrategy=#myStrategy";)
+----
+
+Routes that already supply a custom `headerFilterStrategy` or a custom
`undertowHttpBinding`
+are unaffected.
=== camel-aws2-sqs
