php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #64420 SoapClient ignores faults sent by SoapServer
Submitted: 2013-03-13 15:07 UTC Modified: -
From: polettog at gmail dot com Assigned:
Status: Open Package: SOAP related
PHP Version: 5.3.22 OS: linux 32bits
Private report: No CVE-ID: None
View Add Comment Developer Edit
Anyone can comment on a bug. Have a simpler test case? Does it work for you on a different platform? Let us know!
Just going to say 'Me too!'? Don't clutter the database with that please — but make sure to vote on the bug!
Your email address:
MUST BE VALID
Solve the problem:
36 + 28 = ?
Subscribe to this entry?

 
 [2013-03-13 15:07 UTC] polettog at gmail dot com
Description:
------------
A client request can be "one way" or not, if "one way", an empty response will be given to the caller (__getLastResponse() returns empty string).

As i can see in soap.c (do_soap_call() : 2692), the "one way" detection is based on the wsdl : if the function (operation) has no "output message", no need to read the response, but in this case no faults will be taken in count.

I report it as a bug since there is no mention in the doc of the necessity for a function to return something to make SoapFault system work and __getLastResponse() work.

I first wanted to post it as a note in the doc but it says to not post bugs there.

Expected result:
----------------
__getLastResponse() returns the response and SoapFault's are thrown in the client

Actual result:
--------------
__getLastResponse() returns empty string and no SoapFault thrown in the client (SoapFault's are lost in nature)

Patches

Add a Patch

Pull Requests

Add a Pull Request

 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Apr 18 04:01:27 2024 UTC