This is an automated email from the ASF dual-hosted git repository.
oscerd 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 02912f4a62a7 CAMEL-24895: docs - sync camel-mustache/camel-chunk
header-alignment entry to 4_22 and 4_18 guides (#26809)
02912f4a62a7 is described below
commit 02912f4a62a75767a8080197fe5ef331fd3f90a7
Author: Andrea Cosentino <[email protected]>
AuthorDate: Thu Sep 24 07:38:39 2026 +0200
CAMEL-24895: docs - sync camel-mustache/camel-chunk header-alignment entry
to 4_22 and 4_18 guides (#26809)
Co-authored-by: Claude Opus 4.8 <[email protected]>
---
.../ROOT/pages/camel-4x-upgrade-guide-4_18.adoc | 36 ++++++++++++++++++++
.../ROOT/pages/camel-4x-upgrade-guide-4_22.adoc | 38 ++++++++++++++++++++++
2 files changed, 74 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 c9b3b666d0d8..f9c5f49202eb 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
@@ -220,6 +220,42 @@ To restore the previous behaviour and allow external
entity resolution, set the
`allowExternalEntities` option to `true` on the data format or on the endpoint
(`smooks:config.xml?allowExternalEntities=true`).
+=== camel-mustache, camel-chunk - potential breaking change
+
+The Exchange header constants in `MustacheConstants` and `ChunkConstants` have
been renamed to
+follow the Camel naming convention used across the rest of the component
catalog (so that they are
+handled consistently by `DefaultHeaderFilterStrategy`, like the other template
components). The Java
+field names are unchanged; only the header string values have changed.
+
+`MustacheConstants`:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `MustacheConstants.MUSTACHE_RESOURCE_URI` | `MustacheResourceUri` |
`CamelMustacheResourceUri`
+| `MustacheConstants.MUSTACHE_TEMPLATE` | `MustacheTemplate` |
`CamelMustacheTemplate`
+|===
+
+`ChunkConstants`:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `ChunkConstants.CHUNK_RESOURCE_URI` | `ChunkResourceUri` |
`CamelChunkResourceUri`
+| `ChunkConstants.CHUNK_TEMPLATE` | `ChunkTemplate` | `CamelChunkTemplate`
+|===
+
+Both components read these headers only when `allowTemplateFromHeader=true`.
Because the old names sat
+outside the `Camel` namespace, `DefaultHeaderFilterStrategy` did not strip
them, so such a header
+arriving from an untrusted sender reached the producer; with the `Camel`
prefix the headers are now
+filtered at the component boundary, so the template or resource can only come
from the route. For that
+reason the old names should not simply be restored.
+
+Routes that reference the constants (for example
`setHeader(MustacheConstants.MUSTACHE_TEMPLATE, ...)`)
+are unaffected. Routes that set the header by its literal string name, or that
use
+`allowTemplateFromHeader=true` with the old header names, must switch to the
new `Camel`-prefixed
+names.
+
== 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 a964fb36ea5b..fac86e48c844 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
@@ -11,6 +11,44 @@ Note that manual migration is still required.
See the xref:camel-upgrade-recipes-tool.adoc[documentation] page for details.
====
+== Upgrading from 4.22.1 to 4.22.2
+
+=== camel-mustache, camel-chunk - potential breaking change
+
+The Exchange header constants in `MustacheConstants` and `ChunkConstants` have
been renamed to
+follow the Camel naming convention used across the rest of the component
catalog (so that they are
+handled consistently by `DefaultHeaderFilterStrategy`, like the other template
components). The Java
+field names are unchanged; only the header string values have changed.
+
+`MustacheConstants`:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `MustacheConstants.MUSTACHE_RESOURCE_URI` | `MustacheResourceUri` |
`CamelMustacheResourceUri`
+| `MustacheConstants.MUSTACHE_TEMPLATE` | `MustacheTemplate` |
`CamelMustacheTemplate`
+|===
+
+`ChunkConstants`:
+
+[options="header"]
+|===
+| Constant | Previous value | New value
+| `ChunkConstants.CHUNK_RESOURCE_URI` | `ChunkResourceUri` |
`CamelChunkResourceUri`
+| `ChunkConstants.CHUNK_TEMPLATE` | `ChunkTemplate` | `CamelChunkTemplate`
+|===
+
+Both components read these headers only when `allowTemplateFromHeader=true`.
Because the old names sat
+outside the `Camel` namespace, `DefaultHeaderFilterStrategy` did not strip
them, so such a header
+arriving from an untrusted sender reached the producer; with the `Camel`
prefix the headers are now
+filtered at the component boundary, so the template or resource can only come
from the route. For that
+reason the old names should not simply be restored.
+
+Routes that reference the constants (for example
`setHeader(MustacheConstants.MUSTACHE_TEMPLATE, ...)`)
+are unaffected. Routes that set the header by its literal string name, or that
use
+`allowTemplateFromHeader=true` with the old header names, must switch to the
new `Camel`-prefixed
+names.
+
== Upgrading from 4.22.0 to 4.22.1
=== camel-docling
