Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Questions about character entities in XML and PCI security compliance

From: Peter Flynn <peter.nosp@-.--------.-->
To: NULL
Date: 8/8/2008 11:49:00 PM

Joe Fawcett wrote:
[snip]
> Well we have similar files and I've never seen that happen. As you say 
> they seem to be escaping twice. In my opinion they're wrong but I'd need 
> to know their process etc.

I would suspect they are not used to dealing with XML, and have been 
told by some less-than-well-informed person that "you always have to do 
this with those funny characters in web pages". But as Joe says, without 
knowing their process it's hard to be sure.

What *is* sure is that they are wrong to do this. The file when 
decrypted should be the file that was encrypted. They have corrupted it, 
and they must stop doing that.

> Pragmatically you may need to un-escape once before treating the file as 
> XML.

That may not be possible if parts of the document already use numeric 
character references or the &amp;amp; escapement for other reasons (eg 
in CDATA sections). But with luck you may just be able to reconvert it 
until your hosting bods fix the bug.

///Peter



transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent