Closed Bug 461123 Opened 16 years ago Closed 16 years ago

Non-printable chars in bug description were not encoded properly when displayed

Categories

(Bugzilla :: Creating/Changing Bugs, defect)

3.0.4
x86
All
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 458218

People

(Reporter: gkareev, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3) Gecko/2008092700 SUSE/3.0.3-2.2 Firefox/3.0.3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.3) Gecko/2008092700 SUSE/3.0.3-2.2 Firefox/3.0.3

If I type something like this in bug description (exact copy of the error message from windows event logger):
------
<b>C:\Prog
^
└er  [.\xml_parse.cpp:113]
[11:27:36|INFO: 2512:p.log] => wu57017 web user
------

Then in post_bug.cgi, show_bug.cgi, process_bug.cgi and on show_bug.cgi?ctype=xml pages sources I get the symbol '' not encoded properly.
I'm getting raw \x01 utf-8 byte, which is unexpected for any xml-parser used to parse Bugzilla bugs details.

Using my browser I'm getting the following error, when trying to open page show_bug.cgi?ctype=xml:
------
XML Parsing Error: not well-formed
Location: http://testbugs.[domain].[domain]/show_bug.cgi?ctype=xml&id=142130
Line Number 65, Column 2:
└er  [.\xml_parse.cpp:113]
-^
------

It should be encoded as "&#01;", if I'm right.

Reproducible: Always

Steps to Reproduce:
1. Enter new bug with non-printable char(s) in description area
2. Open show_bug.cgi?ctype=xml&id=<bug_id> page with Mozilla Firefox or download the page and use libxml2 'xmllint --noout <downloaded_page.filename>' command to validate the page. Or view the show_bug.cgi?id=<bug_id> page html source.
Actual Results:  
Libxml2 'xmllint --noout <downloaded_page.filename>' will tell you that xml is not valid.
Or view the show_bug.cgi?id=<bug_id> page html source. You'll find raw non-printable char(s) there.

Expected Results:  
Properly encoded non-printable chars in html output and valid xml output.

Bugzilla 3.0.4/3.0.5
Oops. Your current bugzilla has the same problem too, so 3.2rc1+ and latest too.
Version: unspecified → 3.0.4
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.