Showing results for 
Search instead for 
Did you mean: 

Developers with Magento having issues with CIM SOAP API



     So today I came in and we were unable to charge any orders through CIM SOAP API, after talking with their support they said this is a magento wide issue.


     I've found the issue, they're response header has changed lengths from 335 characters to 395 characters. The module we were using has a parseXML function like this:


public function parseXML($start, $end, $xml)	 {
		return preg_replace('|^.*?'.$start.'(.*?)'.$end.'.*?$|i', '$1', substr($xml, 335));

     What is should really be is:

public function parseXML($start, $end, $xml)	 {
		return preg_replace('|^.*?'.$start.'(.*?)'.$end.'.*?$|i', '$1', substr($xml, 395));


Realistically we should probably use strpos($xml, "<?xml ") in place of "substr($xml, 395)" which would prevent future issues if the response header changes, but unfortunately I don't have time to debug this right now, at least it works...


Accepted Solutions

View solution in original post


@autojunkie05 This is great information, thank you.

Could you elaborate on what you mean by "response header"? Do you mean the HTTP headers prior to the XML stream? Or do you mean the root element of the XML?

"Move fast and break things," out. "Move carefully and fix what you break," in.
Administrator Administrator

yes, I mean the HTTP response header before the XML Response:


HTTP/1.1 200 OK
Cache-Control: private
Content-Length: 501
Content-Type: application/xml; charset=utf-8
Server: Microsoft-IIS/7.5
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
Access-Control-Allow-Origin: *
Access-Control-Allow-Methods: GET,POST,OPTIONS
Access-Control-Allow-Headers: x-requested-with,cache-control,content-type,origin,method
Date: Wed, 25 Feb 2015 20:13:55 GMT

<?xml version="1.0" encoding="utf-8"?><createCustomerProfileResponse xmlns:xsi="" xmlns:xsd="" xmlns="AnetApi/xml/v1/schema/AnetApiSchema.xsd"><messages><resultCode>Error</resultCode><message><code>E00039</code><text>A duplicate record with ID XXXXXXXX already exists.</text></message></messages><customerPaymentProfileIdList /><customerShippingAddressIdList /><validationDirectResponseList /></createCustomerProfileResponse>


it's 395 characters to the actually XML response, and there's a few weird characters before the response (and some special characters in the HTTP header) that throw off the regex expression and prevent the code in magento from parsing the XML tags for the data. I'm assuming that the previous HTTP response was only 335 characters because that was the value in the orginal function "Substr($xml, 335)"  Which worked up until this moring.


If you take the original function:

public function parseXML($start, $end, $xml)	 {
		return preg_replace('|^.*?'.$start.'(.*?)'.$end.'.*?$|i', '$1', substr($xml, 335));

 and run the response I posted above this in this post, you'll see that it incorrectly parses the XML