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 7c619a2bec50 CAMEL-25023: docs - sync the maxDecompressedSize entry
into the 4.22 and 4.18 upgrade guides (#27140)
7c619a2bec50 is described below
commit 7c619a2bec502a9e0dcca266cdd3067dc9a0e630
Author: Andrea Cosentino <[email protected]>
AuthorDate: Thu Oct 1 07:45:27 2026 +0200
CAMEL-25023: docs - sync the maxDecompressedSize entry into the 4.22 and
4.18 upgrade guides (#27140)
CAMEL-25023 is being backported to camel-4.22.x (#27137) and camel-4.18.x
(#27138), and the
upgrade guides for every release line live on main, so the entry #26892
added to the 4.23 guide
needs its counterpart under the matching 4.22.1 -> 4.22.2 and 4.18.4 ->
4.18.5 sections.
The behaviour being recorded is the same on all three lines: a
maxDecompressedSize of 2 GiB or more
is now enforced, and IOHelper.copy returns Integer.MAX_VALUE instead of a
wrapped negative.
Also fixes a pre-existing rendering defect in the 4.18 guide: "===
camel-dynamic-router" had no
blank line before it, so AsciiDoc rendered the section title as body text
of the preceding
paragraph instead of as a heading. Unrelated to CAMEL-25023, but it is one
line in a file this
change already touches.
Co-Authored-By: Claude Opus 5 <[email protected]>
Signed-off-by: Andrea Cosentino <[email protected]>
---
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 12 ++++++++++++
.../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 11 +++++++++++
2 files changed, 23 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 3b057c9bd2c0..a123740946f4 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
@@ -13,6 +13,17 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation]
page for details.
== Upgrading from 4.18.4 to 4.18.5
+=== camel-zipfile, camel-tarfile - a maxDecompressedSize of 2 GiB or more is
now enforced
+
+The `maxDecompressedSize` option of the Zip File and Tar File data formats
(and of `ZipSplitter`) was not
+enforced when set to 2 GiB (`Integer.MAX_VALUE` bytes) or more, because the
byte count behind the check
+wrapped around. The limit is now enforced for any value: unmarshalling an
entry that decompresses to more
+than the configured `maxDecompressedSize` fails with an `IOException`, as
documented. The default limit
+(1 GiB) is unchanged, and `-1` still disables the limit.
+
+`IOHelper.copy(InputStream, OutputStream, int, boolean, long)` now returns
`Integer.MAX_VALUE`, instead of a
+negative number, when it copies more than `Integer.MAX_VALUE` bytes.
+
=== camel-core - masking of sensitive values in endpoint URIs
`URISupport.sanitizeUri()`, which masks secrets in endpoint URIs shown in
logs, events, JMX names and error
@@ -64,6 +75,7 @@ It is unset by default, which keeps the previous behaviour of
accepting any path
Additionally, a local input path that does not exist is now reported as a
`File not found` `IOException`
before Docling is invoked. Previously the size check silently skipped a path
that resolved to nothing and
the failure surfaced later, from the Docling process or API call.
+
=== camel-dynamic-router
The `dynamic-router-control` endpoint no longer takes the subscription
`predicate`, or the
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 76a6ffe58edc..980426dfa44e 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
@@ -13,6 +13,17 @@ See the xref:camel-upgrade-recipes-tool.adoc[documentation]
page for details.
== Upgrading from 4.22.1 to 4.22.2
+=== camel-zipfile, camel-tarfile - a maxDecompressedSize of 2 GiB or more is
now enforced
+
+The `maxDecompressedSize` option of the Zip File and Tar File data formats
(and of `ZipSplitter`) was not
+enforced when set to 2 GiB (`Integer.MAX_VALUE` bytes) or more, because the
byte count behind the check
+wrapped around. The limit is now enforced for any value: unmarshalling an
entry that decompresses to more
+than the configured `maxDecompressedSize` fails with an `IOException`, as
documented. The default limit
+(1 GiB) is unchanged, and `-1` still disables the limit.
+
+`IOHelper.copy(InputStream, OutputStream, int, boolean, long)` now returns
`Integer.MAX_VALUE`, instead of a
+negative number, when it copies more than `Integer.MAX_VALUE` bytes.
+
=== camel-core - masking of sensitive values in endpoint URIs
`URISupport.sanitizeUri()`, which masks secrets in endpoint URIs shown in
logs, events, JMX names and error
