I know it's bizarre. Honestly I wouldn't waste everyones time with this unless I thought it was weird. According the my PHP page (using this to test the C# code) this is the contents of the payload when the XML is sent as text/xml in the payload of HTTP POST
[01/12/2008 13:08:52] INFO: POST.Raw: <request><service name="asset.create" session="11de698277eqBDXroHpbc2V2ScCdKE32QbSdf4e8Kbc"><args><anotherValue>test</ anotherValue><name>Some Name</name></args></request> and this is the same value when being sent using the code above that inlcludes the fields in the multipart/form-data, again using HTTP POST. [01/12/2008 13:08:52] INFO: POST.request: <request><service name= \"asset.create\" session=\"11de698277eqBDXroHpbc2V2ScCdKE32QbSdf4e8Kbc \"><args><anotherValue>test</anotherValue><name>Some Name</name></ args></request> The POST.Raw and POST.request is just my logging code in PHP telling me where it got the value from. POST.Raw is saying that it get the XML from the main payload and POST.request is telling me that it got the XML from the request field in the form encoding. It's the same code is creating the XML and outputting it. It;s even the same line that is generating the byte[] using UTF8Encoding.UTF8 (xmlDoc.InnerXml). Note the \ chars this time. It's is definetly coming through in the payload as if I do a simple string replace and change \" to " in PHP it can parse the XML! Al On Dec 1, 5:38 pm, Joe Enos <[EMAIL PROTECTED]> wrote: > Not sure on this one, but my guess is that the backslashes are just an > illusion. Visual Studio shows you the escape characters when you're > debugging, even though they're not really part of the string. Are you > sure they are really being sent? I'd stick a logger or something on > the other end to see what it's actually getting. The backslashes are > a C#-specific concept, so any compiled CIL code or XML parser or web > server or anything else wouldn't know about them.
