Andrea Cosentino created CAMEL-23651:
----------------------------------------

             Summary: camel-netty-http and camel-undertow: align muteException 
default with the other HTTP components
                 Key: CAMEL-23651
                 URL: https://issues.apache.org/jira/browse/CAMEL-23651
             Project: Camel
          Issue Type: Improvement
          Components: camel-netty-http, camel-undertow
            Reporter: Andrea Cosentino
            Assignee: Andrea Cosentino
             Fix For: 4.21.0, 4.18.3, 4.14.8


h4. Background

The muteException consumer option is inconsistent across the HTTP server 
components:

* camel-http, camel-jetty and camel-servlet (via HttpCommonComponent) default 
muteException to true.
* camel-platform-http defaults muteException to true.
* camel-netty-http and camel-undertow default muteException to false.

With muteException=false a consumer-side processing failure returns the 
exception stack trace in the response body as text/plain; with 
muteException=true the response body is empty. The two groups behave 
differently out of the box.

h4. Proposal

Align camel-netty-http and camel-undertow with the other HTTP server components 
by defaulting muteException to true.

* camel-netty-http: initialise the field in NettyHttpConfiguration to true, set 
the same default in NettyHttpComponent, add defaultValue = "true" to the 
@UriParam, and regenerate the catalog metadata.
* camel-undertow: set the default in UndertowComponent to true, add 
defaultValue = "true" to the @UriParam, and regenerate the catalog metadata.

h4. Compatibility

This changes the default behaviour. Users who rely on the exception stack trace 
being present in the response body must set muteException=false explicitly 
after the upgrade. The change must ship with an upgrade-guide note on each 
affected release line.

h4. Backport

Backport to 4.18.x and 4.14.x. The option and its current false default are 
present on both branches.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to