如何提取SOAP响应Body并使用SimpleXML解析以规避头错误？

Absolutely, you can extract just the SOAP Body content and parse that separately with simplexml_load_string—this is a common workaround when the full SOAP response has invalid XML in the header (like your signature section appears to, given the malformed structure in your snippet). Here's a step-by-step solution:

The Problem with Your Current Approach #

Your full SOAP response fails to parse because the XML structure in the SOAP Header is invalid (looking at your snippet, the <ds:SignatureValue> is incorrectly nested inside <ds:SignedInfo>, which breaks XML rules). Instead of trying to fix the entire response, we can target just the SOAP Body, which likely has valid XML.

Modified Code to Extract and Parse SOAP Body #

Replace your XML parsing logic with this code after fetching the response with cURL:

$headers = array(
    "Content-type: text/xml;charset=\"utf-8\"",
    "Accept: text/xml",
    "Cache-Control: no-cache",
    "Pragma: no-cache",
    "Content-length: ".strlen($xml_post_string),
);
$url = $soapUrl;
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, $xml_post_string);
curl_setopt($ch, CURLOPT_HTTPHEADER, $headers);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_HEADER, 0);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, 0);
$response = curl_exec($ch);
curl_close($ch);

// Step 1: Decode HTML entities in the response
$decodedResponse = html_entity_decode($response);

// Step 2: Use DOMDocument to navigate the XML (more tolerant of partial invalidity)
$dom = new DOMDocument();
libxml_use_internal_errors(true); // Suppress XML parsing errors for the full response
$dom->loadXML($decodedResponse);
libxml_clear_errors(); // Clear any errors from loading the full invalid XML

// Step 3: Use XPath to find the SOAP Body node (using the correct namespace)
$xpath = new DOMXPath($dom);
$xpath->registerNamespace('soap', 'http://schemas.xmlsoap.org/soap/envelope/');
$bodyNodes = $xpath->query('//soap:Body');

if ($bodyNodes->length > 0) {
    // Extract the SOAP Body as a standalone XML string
    $bodyXml = $dom->saveXML($bodyNodes->item(0));
    
    // Step 4: Parse the Body XML with simplexml_load_string
    $xml = simplexml_load_string($bodyXml, 'SimpleXMLElement', LIBXML_NOCDATA);
    
    if ($xml === false) {
        echo "Failed to load Body XML: ";
        foreach(libxml_get_errors() as $error) {
            echo "<br>", $error->message;
        }
    } else {
        echo $xml->asXML();
        var_dump($xml);
    }
} else {
    echo "Could not locate the SOAP Body in the response.";
}

Why This Works #

• DOMDocument is more error-tolerant: Unlike simplexml_load_string, which fails completely if the XML is invalid, DOMDocument can still load the document and let you navigate valid parts (like the SOAP Body) even if other sections are broken.
• XPath targeting: By registering the SOAP namespace and using an XPath query, we reliably locate the <SOAP-ENV:Body> node regardless of other invalid content in the response.
• Standalone Body parsing: Once we extract the Body as a valid XML snippet, simplexml_load_string can parse it without issues.

Note #

If you have control over the SOAP service generating the response, fixing the invalid signature XML in the header is the better long-term solution. But if that's not an option, this workaround will let you access the data you need.

内容的提问来源于stack exchange，提问作者Frank W.