#32857 [Fbk->Csd]: Correct SoapFaults encoded in SOAP Body does work if Axis sends HTTP error 500

ID: 32857 User updated by: thetaphi@php.net Reported By: thetaphi@php.net -Status: Feedback +Status: Closed Bug Type: SOAP related Operating System: Solaris 9 PHP Version: 5CVS-2005-04-27 (dev) New Comment: Works since Dmitry's last change: http://cvs.php.net/diff.php/php-src/ext/soap/php_http.c?r1=1.55.2.14&r2=1.55.2.15&ty=h Tested this on Saturday but forgot to close this bug. Previous Comments: ------------------------------------------------------------------------ [2005-05-17 17:16:04] sniper@php.net Please try using this CVS snapshot: http://snaps.php.net/php5-latest.tar.gz For Windows: http://snaps.php.net/win32/php5-win32-latest.zip ------------------------------------------------------------------------ [2005-04-27 20:04:46] thetaphi@php.net Description: ------------ After updating our application server to a Axis 1.2 (before it was Axis 1.1), the handling of SOAP faults in PHP does not work correct. Axis 1.2 sends a HTTP server error 500 together with the XML body containing the SoapFault with its error message (in Axis the Message of a java.rmi.RemoteException). Instead of throwing a correct exception containing the FaultString of the XML body, PHP displays a "Internal Server Error" fault (I think because he gets the 500 HTTP Error). PHP should also handle "500" as valid response from SOAP if it contains a correct XML body with SOAP envelope and decode it. If there is some HTML or other non-XML in it (a "real" HTTP error) it can throw the exeption with the server error like before. ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=32857&edit=1