Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 79482 - xml parser error with malformed text
Summary: xml parser error with malformed text
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site
Version: RHN Stable
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Greg DeKoenigsberg
QA Contact: Fanny Augustin
URL: https://rhn.redhat.com/rpc/recent-err...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-12-12 08:19 UTC by Rene van Paassen
Modified: 2007-04-18 16:49 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-12-12 13:08:58 UTC


Attachments (Terms of Use)

Description Rene van Paassen 2002-12-12 08:19:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2) Gecko/20021203

Description of problem:
Mozilla 1.2.1 gives me the following on https://rhn.redhat.com/rpc/recent-errata.pxt

XML Parsing Error: not well-formed
Location: https://rhn.redhat.com/rpc/recent-errata.pxt
Line Number 105, Column 37:

All Red Hat Linux users using wget < 1.8.2-4  should upgrade
------------------------------------^

The "<" is un-escaped. Guess mozilla is right here

The same gives a problem in summary of Ximian Evolution

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. open mozilla
2. enter https://rhn.redhat.com/rpc/recent-errata.pxt
3.
	

Actual Results:  XML error

Expected Results:  list of errata

Additional info:

Comment 1 Chip Turner 2002-12-12 13:08:51 UTC
This should now be fixed.  Thanks for the catch.

Comment 2 Josef Komenda 2002-12-12 16:40:25 UTC
Looks good, closing.


Note You need to log in before you can comment on or make changes to this bug.