Hey Sergey, Thanks for your answer. Won't adding the fastinfoset type as binary cause the message not to be logged at all? I don't want to disable logging it, just decode it beforehand.
Regards, Artur -----Original Message----- From: Sergey Beryozkin [mailto:[email protected]] Sent: Monday, July 03, 2017 3:17 PM To: [email protected] Subject: Re: Issues with logging compressed payloads Hi The logging interceptors disable showing the binary content by default however at the moment an application/fastinfoset type is not recognized as a binary type. Try setting a 'binaryContentMediaTypes'on the interceptors. Not possible to set them on the feature only on the interceptors Cheers, Sergey On 03/07/17 13:44, Popławski Artur (Grupa PZU) wrote: > Hello, > I'm having some trouble with the logging feature. What I'm trying to achieve > is to log the messages that's payload has been compressed (message header > includes Content-Type: application/fastinfoset). In that scenario the logged > payload is still in it's binary form, so the logfiles are hardly readable. > Would it be possible to configure the feature so the messages will be decoded > before logging them? > Regards, Artur > >
