From 3a8c7d369719612743ad509ed044b291b1f1a0e4 Mon Sep 17 00:00:00 2001 From: Claus Ibsen Date: Fri, 24 Jul 2026 08:02:58 +0200 Subject: [PATCH] chore: sync camel-4x-upgrade-guide-4_18.adoc with camel-4.18.x branch Sync the camel-http gzip double-decompression entry (CAMEL-24234) from the camel-4.18.x backport to the main branch upgrade guide. Co-Authored-By: Claude Opus 4.6 Signed-off-by: Claus Ibsen --- .../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 9 +++++++++ 1 file changed, 9 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 e36e04c77e25b..57772d7be1fa3 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 @@ -40,6 +40,15 @@ The new behavior activates automatically when all of the following are true: No configuration changes are required. The existing `maxAutoLockRenewDuration` option controls how long Camel will continue renewing a message's lock. +=== camel-http - gzip double decompression with HttpClient 5.6+ + +When using HttpClient 5.6+ (including transitively via a Spring Boot BOM on Camel 4.18.x), HttpClient +auto-decompresses gzip response bodies but may leave stale `Content-Encoding`, `Content-Length`, and +`Content-MD5` headers. Camel now reads content encoding from `entity.getContentEncoding()` instead of +the response header and strips stale compression headers after the HTTP call. This prevents a second +decompression attempt that could fail with `ZipException: Not in GZIP format` against gzip-compressing +servers with default settings. + === camel-mail - MimeMultipartDataFormat inbound header filtering When unmarshalling a MIME message with `headersInline=true`, the `mime-multipart` data format now applies a