To ensure that the data arrives and is interpreted correctly, the following encoding standards should be adhered to when POSTing XML data to Logistech's server.

XML Document Markup

The XML document should be marked up according to the W3C specfication on character data markup with special characters (such as &, <, and >) escaped according to the W3C specification on character references.

So, for example the following document : 
  <some_xml>1 & 2 > 3</some_xml>
would be marked up to become : 
  <some_xml>1 &#38; 2 &#62; 3</some_xml>
If this is not done correctly, you are likely to receive a parse error such as "Illegal character or entity reference syntax" if the document contains special characters. Note that the Java XML parser we use cannot handle text entities (e.g. &amp;) the ASCII entity should be used instead (e.g. &#38;).

POST Data Encoding

The data POSTed to the appropriate URL should follow the W3C specfication for mime type application/x-www-form-urlencoded.

Encoding Example

If client=123, profile=1234, and the XML text is : 
  <some_xml>1 & 2 > 3</some_xml>
You would first mark up the special characters in the XML text, so it would become (as above): 
  <some_xml>1 &#38; 2 &#62; 3</some_xml>
Then the ENTIRE XML DOCUMENT would be urlencoded for the post to become: 
  %3Csome_xml%3E1+%26%2338%3B+2+%26%2362%3B+3%3C%2Fsome_xml%3E
So, the final text sent as the POST would be: 
client=123&profile=1234&
 orders=%3Csome_xml%3E1+%26%2338%3B+2+%26%2362%3B+3%3C%2Fsome_xml%3E