camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin O'Toole (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CAMEL-9551) ErrorHandler - Should not log message body by default
Date Thu, 30 Jun 2016 04:28:10 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15356499#comment-15356499
] 

Kevin O'Toole edited comment on CAMEL-9551 at 6/30/16 4:27 AM:
---------------------------------------------------------------

Is it possible to backport this change to 2.16.x? (can default to on to not impact behavior
of 2.16.x)


was (Author: kevo_tool):
Is it possible to backport this change to 2.16.x? (can leave default to on to not impact behavior
of 2.16.x)

> ErrorHandler - Should not log message body by default
> -----------------------------------------------------
>
>                 Key: CAMEL-9551
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9551
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.17.0
>
>
> Related to ticket: CAMEL-9539	
> The error handler will log exhausted exchanges with stacktrace and exchange message body/header
details. We should turn the latter off, so they are not logged by default.
> This helps to avoid logging message details that may be sensitive. And do that by default.
> People can turn on the old behavior with the new logExhaustedMessageBody option. Which
logs all the message exchange/body details as before (also headers).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message