This is an automated email from the ASF dual-hosted git repository. gnodet pushed a commit to branch backport/26183-to-camel-4.18.x in repository https://gitbox.apache.org/repos/asf/camel.git
commit e06e431bafbdedcb084564fe8000c8e1b2a002b0 Author: Andrea Cosentino <[email protected]> AuthorDate: Tue Sep 8 13:30:13 2026 +0200 [backport camel-4.18.x] CAMEL-24424: camel-vertx-http - apply the outbound header filter on the REST producer --- .../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 19 +++++++++++++++++++ 1 file changed, 19 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 c8c83b5f4366..b2d8f08edd7f 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 @@ -1707,3 +1707,22 @@ Routes that set `useRecovery=false` are unaffected. Routes that left recovery en default, stop seeing in-progress aggregations re-delivered, and start seeing genuine recovery. The cache 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.
