Re: [Mod-security-developers] Xml parse errors detected by libxml2 are being written to console

[William C. <wil...@mu...>]

NO_COUT has no effect (v3.0.1). Also didn't find it, or similarly named in
the ModSec source tree.

Could you perhaps please point me to the src where this callback can be
initialized to a null writer?

Our product use case is one where various internal log appenders write
structured data (xml and/or json) to standard out and error, which are in
turn consumed (parsed) by other entities. So unexpected writes to console
by other components/libraries makes these latter entities a bit grumpy ;)

Kind Regards - Jay

On Mon, Apr 2, 2018 at 10:45 PM, Felipe Costa <FC...@tr...> wrote:

> Hi Jai,
>
> You may want to try this:
>
> ./configure CFLAGS='-DNO_COUT' CXXFLAGS='-DNO_COUT'
>
> That was a callback on the libxml that was not set, let me know if you
> have a multi thread environment that we can use for test so we can proper
> address this issue.
>
>
>  Br.,
>   Felipe “Zimmerle”  Costa
>   Security Researcher, Lead Developer ModSecurity.
>
>   Trustwave | SMART  SECURITY ON DEMAND
>   www.trustwave.com
>
>
>
>
>
>
>
>
> From: Jai Harpalani via mod-security-developers <mod-security-developers@
> lists.sourceforge.net>
> Sent: Monday, April 2, 2018 8:38 PM
> To: mod-security-d.
> Cc: Jai Harpalani; William Case
> Subject: [Mod-security-developers] Xml parse errors detected by libxml2
> are being written to console
>
>
> While parsing a malformed xml request body, errors such as the following
> are written to the console:
>
>
> body.xml:3:  parser error : error parsing attribute name
>       <soapenv:Body>
>       ^
> body.xml:3:  parser error : attributes construct error
>       <soapenv:Body>
>       ^
> body.xml:3:  parser error : Couldn't find end of Start Tag Envelope
>       <soapenv:Body>
>       ^
>
>
>
> Is  there a way to prevent these from being displayed on the console?
>