You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by da...@apache.org on 2026/09/03 08:41:23 UTC

(camel) branch doc-sync/CAMEL-24409-upgrade-guide created (now c2229907735a)

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a change to branch doc-sync/CAMEL-24409-upgrade-guide
in repository https://gitbox.apache.org/repos/asf/camel.git


      at c2229907735a CAMEL-24409: sync REST client request validation upgrade-guide note to 4.22 and 4.18 guides

This branch includes the following new commits:

     new c2229907735a CAMEL-24409: sync REST client request validation upgrade-guide note to 4.22 and 4.18 guides

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



(camel) 01/01: CAMEL-24409: sync REST client request validation upgrade-guide note to 4.22 and 4.18 guides

Posted by da...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch doc-sync/CAMEL-24409-upgrade-guide
in repository https://gitbox.apache.org/repos/asf/camel.git

commit c2229907735a95800a3bce75631ea53e91cd1cb3
Author: Claus Ibsen <cl...@gmail.com>
AuthorDate: Thu Sep 3 10:41:11 2026 +0200

    CAMEL-24409: sync REST client request validation upgrade-guide note to 4.22 and 4.18 guides
    
    The binary-body fix (PR #26024) is backported to camel-4.22.x (PR #26070) and camel-4.18.x
    (PR #26071). Per the backport upgrade-guide policy, main's version-specific guides are the
    canonical history, so add the matching note to the 4.22 and 4.18 upgrade guides on main.
    
    Co-Authored-By: Claude Opus 4.8 <no...@anthropic.com>
    Signed-off-by: Claus Ibsen <cl...@gmail.com>
---
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_18.adoc            | 7 +++++++
 .../modules/ROOT/pages/camel-4x-upgrade-guide-4_22.adoc            | 7 +++++++
 2 files changed, 14 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 d0780934c477..accc42e81f52 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
@@ -2099,3 +2099,10 @@ that resolve outside the configured directory are rejected.
 
 If `downloadFileName` is configured with an expression (i.e. it contains `$`), the local
 path is built by that expression as before and is not subject to this check.
+
+=== camel-core - REST client request validation and binary bodies
+
+When `clientRequestValidation` is enabled and the REST service declares a required body, the incoming
+message body is no longer replaced with a `String` version of itself. That conversion corrupted binary
+payloads such as `application/octet-stream`. The body is still read to check that it is present, using
+stream caching so it stays re-readable, but it now keeps its original type.
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 9ad31f1f55c9..519c54102036 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
@@ -1851,3 +1851,10 @@ they say:
   `CamelGoogleVertexAIStreamOutputMode` header.
 * `jsonMode=true` sets the response MIME type of the request to `application/json`, so the model is
   asked to answer with JSON. The default `false` leaves the request untouched.
+
+=== camel-core - REST client request validation and binary bodies
+
+When `clientRequestValidation` is enabled and the REST service declares a required body, the incoming
+message body is no longer replaced with a `String` version of itself. That conversion corrupted binary
+payloads such as `application/octet-stream`. The body is still read to check that it is present, using
+stream caching so it stays re-readable, but it now keeps its original type.