oscerd opened a new pull request, #23923:
URL: https://github.com/apache/camel/pull/23923

   ## Backport of #23913
   
   Cherry-pick of #23913 onto `camel-4.18.x`.
   
   **Original PR:** #23913 — CAMEL-23651: camel-netty-http and camel-undertow - 
align muteException default with the other HTTP components
   **Original author:** @oscerd
   **Target branch:** `camel-4.18.x`
   **JIRA:** [CAMEL-23651](https://issues.apache.org/jira/browse/CAMEL-23651) 
(fixVersions 4.14.8 / 4.18.3 / 4.21.0)
   
   ### What
   
   Flips the `muteException` consumer default from `false` to `true` in 
`camel-netty-http` and `camel-undertow`, aligning them with `camel-http` / 
`camel-jetty` / `camel-servlet` / `camel-platform-http`. A consumer-side 
processing failure now returns an empty response body instead of the exception 
stack trace as `text/plain`.
   
   Includes the undertow Rest DSL binding fix (the `RestUndertowHttpBinding` 
now receives the endpoint's `muteException` value instead of a hard-coded 
`false`), the three new default-behaviour tests, the three tests updated to opt 
out with `muteException=false`, and regenerated metadata.
   
   ### Cherry-pick notes
   
   - Clean cherry-pick except for the upgrade-guide entry: the original landed 
in `camel-4x-upgrade-guide-4_21.adoc` (not present on this branch). The 
equivalent note was added under **Upgrading from 4.18.2 to 4.18.3** in 
`camel-4x-upgrade-guide-4_18.adoc` instead. The canonical 4_18 entry on `main` 
is already present via #23913.
   
   ### Validation
   
   - `camel-netty-http`: 249 tests, 0 failures
   - `camel-undertow`: 164 tests, 0 failures
   - Full reactor build green
   
   ---
   _Claude Code on behalf of Andrea Cosentino_
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to