Bug 531953

Summary: XML output fails to include XML declaration (encoding is vitally important)
Product: [Retired] Dogtag Certificate System Reporter: John Dennis <jdennis>
Component: Certificate ManagerAssignee: RHCS Maintainers <rhcs-maint>
Status: CLOSED EOL QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: low    
Version: 1.2CC: dpal, rcritten
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 20:10:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 431022, 532092, 533287, 533979    
Attachments:
Description Flags
patch none

Description John Dennis 2009-10-29 23:45:12 UTC
The CMS server generates XML documents in a variety of circumstances, however it always omits the critically import xml declaration entity. The XML rfc's suggest the declaration should always be included. In particular it is critically important because the xml declaration declares the document encoding. The xml documents should be preceded by something like this:

<?xml version="1.0" encoding="UTF-8"?>

I have not verified that all text being output by CMS is in fact encoded in UTF-8, but it should be, and I assume it is.

The primary point is the receiver of the XML document should be able to parse an xml declaration and by virtue of that establish the xml version and document encoding.

Comment 1 John Dennis 2009-11-12 16:22:43 UTC
Created attachment 369247 [details]
patch

Comment 2 Andrew Wnuk 2009-11-18 00:10:55 UTC
attachment (id=369247) +awnuk

Comment 3 Andrew Wnuk 2009-11-25 23:43:33 UTC
Patch included in in bug #533979 (attachment #373874 [details]) is committed.