Apex Code Development You need to sign in to do that
Don't have an account?
Rudi Out of place characters in SForce SOAP reply
Hi there,
When I receive SForce SOAP reply to a query, characters are included in the SOAP body that often break XML structure, especially when placed inside the tag brackets. With HEX editor, I've noticed that characters are placed on regular intervals, so I doubt they are random. Here's the example of the SOAP reply:
HTTP/1.1 200 OK
Server: sfdc
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
Date: Fri, 06 Jan 2006 22:56:22 GMT
3f59
... and then 3ff8 is added (with line feed and carriage return before and after) after every 6400 bytes. I've also tried to capture TCP stream, and repeating 3ff8 shows up there as well. Here's the header of my SOAP request if that helps:
POST /services/Soap/u/6.0 HTTP/1.1
User-Agent: 4D SOAP client
Content-Type: text/xml; charset=utf-8
Host: na0-api.salesforce.com
Connection: Close
SoapAction: ""
Content-Length: 5076
Any ideas, hints, or pointers why those characters show up? Thanks,
Rudy
When I receive SForce SOAP reply to a query, characters are included in the SOAP body that often break XML structure, especially when placed inside the tag brackets. With HEX editor, I've noticed that characters are placed on regular intervals, so I doubt they are random. Here's the example of the SOAP reply:
HTTP/1.1 200 OK
Server: sfdc
Cache-Control: private
Content-Type: text/xml; charset=utf-8
Transfer-Encoding: chunked
Date: Fri, 06 Jan 2006 22:56:22 GMT
3f59
... and then 3ff8 is added (with line feed and carriage return before and after) after every 6400 bytes. I've also tried to capture TCP stream, and repeating 3ff8 shows up there as well. Here's the header of my SOAP request if that helps:
POST /services/Soap/u/6.0 HTTP/1.1
User-Agent: 4D SOAP client
Content-Type: text/xml; charset=utf-8
Host: na0-api.salesforce.com
Connection: Close
SoapAction: ""
Content-Length: 5076
Any ideas, hints, or pointers why those characters show up? Thanks,
Rudy
This the http/1.1 chunked transfer, which is required to be supported by clients claiming to be HTTP/1.1 (as your request is). See the HTTP 1.1 spec for more details.
RudiI've passed the request as HTTP 1.0 and it worked. Thanks!