Project

General

Profile

Bug #23551

Updated by Alexis Mousset 9 months ago

Currently, when the input @yml@ technique contains a escaped non-printable character like @\b@, it gets rendered into the output files, and in particular the generated @metdata.xml@ is invalid (non-printable characters are "forbidden in XML 1.0 and must be escaped in XML 1.1":https://stackoverflow.com/a/28651048). 

 <pre><code class="yaml"> 
 id: "test" 
 name: "Test" 
 version: "0.1" 
 items: 
   - method: command_execution 
     params: 
       command: "my command \b is here" 
 </code></pre> 

 The @\b@ is interpreted as backspace char in output files. 

 We need to: 

 * Check the behavior in 7.3 
 * Prevent our XML output from including forbidden chars. Check with upstream @quick_xml@ lib which should not accept it. 
 * Implement a simple fix for RC 2

Back