We're receiving the hosted pay page asynchronous response via HTTPS POST. The POST body contains what purports to be XML, but in certain cases it's not well-formed XML. For example, if the cardholder name contains special characters:
<?xml version='1.0 standalone='yes'?>
Problem is, that "eacute" entity reference can't be resolved by any XML parser, because there is no DTD associated with this XML and, even if there was, it would be ignored due to the standalone='yes' attribute on the XML declaration.
Vanilla XML only defines five named entities. Anything else should be encoded using the relevant character (é in this case).
Any chance this can be rectified?
In reply to MB_Moneris:
In reply to yrqpeter: