You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Christian Schneider (JIRA)" <ji...@apache.org> on 2017/03/13 10:26:04 UTC

[jira] [Resolved] (CXF-7016) Update New Logging interceptors to control the logging of binary & multipart payloads

     [ https://issues.apache.org/jira/browse/CXF-7016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Christian Schneider resolved CXF-7016.
--------------------------------------
    Resolution: Fixed

I think this issue is already solved. There are switches for logging multipart and binary content and by default they are not logged.


> Update New Logging interceptors to control the logging of binary & multipart payloads
> -------------------------------------------------------------------------------------
>
>                 Key: CXF-7016
>                 URL: https://issues.apache.org/jira/browse/CXF-7016
>             Project: CXF
>          Issue Type: Sub-task
>          Components: logging
>            Reporter: Sergey Beryozkin
>            Assignee: Christian Schneider
>            Priority: Minor
>             Fix For: 3.2.0
>
>
> Hi Christian, here is the one:
> The core interceptors turn off the logging of binary data by default (if enabled this comes up as a sequence of unreadable characters)
> Proposal: at the very least the new interceptors should disable it by default too. The possible improvement would be, in case the binary logging is on, to correctly show the byte representations, ex, format then to hex, etc
> Also, the core interceptors do log Multiparts by default - in many cases (JAXWS, JAXRS) they can be readable but if a multipart is used to pass a binary blob then it also makes sense to let users disable it
> If you'd like I can do an initial sync and then you can improve further as you wish 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)