Description: ------------ In revision 1.60 of SOAP/Transport/HTTP.php, the following logic was added for HTTP 200 and 202 response codes in the method _parseResponse(): $this->incoming_payload = trim($match[2]); if (!strlen($this->incoming_payload)) { /* Valid one-way message response. */ return true; } This code resets $this->incoming_payload to the body of the HTTP response, removing the HTTP headers. The issue I'm running into is if the HTTP response has a content-type of multipart/related, when _decodeMimeMessage() is called a little farther down, $this->incoming_payload no longer has the HTTP headers, including the boundary string which is needed to correctly parse the incoming message and separate it into its individual parts.

Ryan, any chance of making a small executable test case? It'll make it a lot easier for us to fix that way...

Ah hah. This looks like a duplicate of Bug #14756

I see a test case was posted in the other issue 14756, but I just attached the patch file that I ran against version 0.12.0 on my system that fixes the issue for me.

I can confirm this. I received a parser error "Invalid document end" when consuming a JAX-based webservice. Investigation shows that the 'content-type: multipart/related' header was being stripped from the message, resulting in the message not being fully MIME-decoded. Applying the posted patch resolves.

This bug has been fixed in SVN. If this was a documentation problem, the fix will appear on pear.php.net by the end of next Sunday (CET). If this was a problem with the pear.php.net website, the change should be live shortly. Otherwise, the fix will appear in the package's next release. Thank you for the report and for helping us make PEAR better.