illegal characters in XML when querying history / comments

[luther_miller]

This is with the last version of Vault 4.x so maybe it is fixed in 5, but wanted to give you a heads up. We have an auto build app that uses the Vault command line to query history and then parse the XML to put the comments of checkins into an email report.

The other day a developer copied from an and email pasted -- this blew up our autobuilder, because the XMl that came back contained hex 0x07 character in the body of a node, which is illegal in XML.

We implemented a workaround (now we pre-process your xml and remove all characters in the 0-31 range and 127), but you probably should have some kind of validation or processing on the vault side to handle this kind of situation.

[Beth]

I can put in a feature request for this functionality. Thank you for your feedback.

F: 15388