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

Mohamed Moez MANSOURI commented on CXF-7016:
--------------------------------------------

Iam using 

{code:java}
                 <dependency>
                        <groupId>org.apache.cxf</groupId>
                        <artifactId>cxf-rt-features-logging</artifactId>
                        <version>3.2.1</version>
                </dependency>
{code}

And i still have logs of binary parts of a multipart message (image/png)  even 
if the flag "logBinary" of AbstractLoggingInterceptor is false by default.
Can you help me ? I would like that if that flag is false , it applies also to 
the inner parts of a multipart message.

> 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.1.10, 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.4.14#64029)

Reply via email to