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

[Felipe C. <FC...@tr...>]

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...@li...>
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?