Today I have a really geeky topic for you: a problem that you may run into with applications that send XML data as POST requests but do so incorrectly.This is an important topic, and if you are trying to do a client\/server interfacing job what I'm going to tell you may save you a few hours of head scratching.Now, in case you have forgotten, the payload of a POST request follows the header. It looks something like this:POST \/test.asp HTTP\/1.1\u00a0Host: www.somehost.com\u00a0User-Agent: Mozilla\/4.0\u00a0Content-Length: 27\u00a0Content-Type: application\/x-www-form-urlencoded\u00a0userid=bob&password=fishThe payload is everything that comes after the blank line that follows the header. The format of the POST payload should be "variable=value" pairs separated by ampersands. This format is expected by the Web server because the original design for the POST interface was based on a data stream generated by a form in a browser. The form's data consisted of fields and their values.So, when you create a script (ASP, JSP, VBScript, etc.) to handle a POST request the data is parsed by the Web server on receipt from the client and then passed to your script.Consider what this looks like using Active Server Pages (ASP) code: When you retrieve form data, you access the browser's POST request through the Request object's Form collection - in VBScript it looks like this:\u00a0mydata = Request.Form("userid")From the POST request I detailed above, this code would set mydata equal to "bob" (quotes not included) - the same result would be gained using:mydata = Request.Form(1).If your application sends an XML data stream to a Web server, it may well look something like the following:\u00a0\u00a0\u00a0 \u00a0\u00a0 A A A\u00a0\u00a0 B B B\u00a0\u00a0 C C C\u00a0 \u00a0 \u00a0\u00a0 D\u00a0\u00a0 E\u00a0\u00a0 F\u00a0 This is actually the format of a three column, two-row table-type format generated by an application I was working with. When that data is received and processed by a Web server through the Form collection using the code above, the contents of mydata will be:"SomeStuff">AAABBBCCCDEFWhat has happened is that the built-in parsing of POST requests by the Web server assumed that the characters "