This is an automated email from the ASF dual-hosted git repository. davsclaus pushed a commit to branch docs/CAMEL-24424-upgrade-guide-4_22-4_18-sync in repository https://gitbox.apache.org/repos/asf/camel.git
commit 13a8de15050b42023f3caa24f2fba29c8319da2a Author: Claus Ibsen <[email protected]> AuthorDate: Tue Sep 8 20:53:55 2026 +0200 CAMEL-24424: sync the vertx-http REST header filter note into the 4.22 and 4.18 upgrade guides The fix was backported to camel-4.22.x (#26209, 4.22.1) and camel-4.18.x (#26210, 4.18.5), but the upgrade guide note only existed in camel-4x-upgrade-guide-4_23.adoc. The version-specific guides for every release line live on main, so the note is added to the 4.22.0 -> 4.22.1 and 4.18.4 -> 4.18.5 sections as well. Co-Authored-By: Claude <[email protected]> Signed-off-by: Claus Ibsen <[email protected]> --- .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 19 +++++++++++++++++++ .../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 19 +++++++++++++++++++ 2 files changed, 38 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 cc831ec08821..65a49340f9d5 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 @@ -145,6 +145,25 @@ default, stop seeing in-progress aggregations re-delivered, and start seeing gen now also holds one entry per completed and not yet confirmed exchange; those entries are removed on confirmation. +=== camel-vertx-http - the REST producer applies the outbound header filter + +`VertxHttpRestHeaderFilterStrategy.applyFilterToCamelHeaders` delegated to +`applyFilterToExternalHeaders`, so it consulted the inbound filter while implementing the outbound +direction. The outbound filter that `VertxHttpHeaderFilterStrategy` installs was therefore never +applied, and the sibling REST strategies in `camel-http-common`, `camel-netty-http` and +`camel-undertow` all delegate to the matching method. + +A REST producer that resolves to `vertx-http` and does not configure its own `headerFilterStrategy` +now filters the common HTTP headers on the outbound direction, as the other HTTP components already +did. A message header named `Content-Length`, `Content-Type`, `Host`, `Cache-Control`, `Connection`, +`Date`, `Pragma`, `Trailer`, `Transfer-Encoding`, `Upgrade`, `Via` or `Warning` is no longer copied +onto the outgoing request; the `Content-Type` of the request is still taken from the exchange as +before. Headers consumed by the URI template or the query parameters continue to be filtered, and a +custom `headerFilterStrategy` is used as-is and is unaffected. + +Routes that relied on one of those headers reaching the wire must set it through the endpoint +configuration or supply a `headerFilterStrategy` that permits it. + == Upgrading from 4.18.3 to 4.18.4 === camel-core - Multicast EIP honors UseOriginalAggregationStrategy 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 ffd0e77298ad..345f03354632 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 @@ -145,6 +145,25 @@ default, stop seeing in-progress aggregations re-delivered, and start seeing gen now also holds one entry per completed and not yet confirmed exchange; those entries are removed on confirmation. +=== camel-vertx-http - the REST producer applies the outbound header filter + +`VertxHttpRestHeaderFilterStrategy.applyFilterToCamelHeaders` delegated to +`applyFilterToExternalHeaders`, so it consulted the inbound filter while implementing the outbound +direction. The outbound filter that `VertxHttpHeaderFilterStrategy` installs was therefore never +applied, and the sibling REST strategies in `camel-http-common`, `camel-netty-http` and +`camel-undertow` all delegate to the matching method. + +A REST producer that resolves to `vertx-http` and does not configure its own `headerFilterStrategy` +now filters the common HTTP headers on the outbound direction, as the other HTTP components already +did. A message header named `Content-Length`, `Content-Type`, `Host`, `Cache-Control`, `Connection`, +`Date`, `Pragma`, `Trailer`, `Transfer-Encoding`, `Upgrade`, `Via` or `Warning` is no longer copied +onto the outgoing request; the `Content-Type` of the request is still taken from the exchange as +before. Headers consumed by the URI template or the query parameters continue to be filtered, and a +custom `headerFilterStrategy` is used as-is and is unaffected. + +Routes that relied on one of those headers reaching the wire must set it through the endpoint +configuration or supply a `headerFilterStrategy` that permits it. + == Upgrading Camel 4.21 to 4.22 === camel-tika
