ID: 36749 Updated by: [EMAIL PROTECTED] Reported By: robertg2 at hope dot ac dot uk -Status: Assigned +Status: Closed Bug Type: SOAP related Operating System: Windows XP & Suse 10 PHP Version: 5.1.2 Assigned To: dmitry New Comment:
Fixed in CVS HEAD and PHP_5_1. Please verify with Novell Bordermanager. Previous Comments: ------------------------------------------------------------------------ [2006-03-19 15:31:14] robertg2 at hope dot ac dot uk Using a default install of Squid 2.5STABLE10-5 instead of Novell BorderManager for the proxy makes the SoapFault disappear. The only real difference in the response from Squid is the fact that it is HTTP/1.0. Using a default install of tinyproxy 1.6.3 - http://tinyproxy.sourceforge.net/ - makes the SoapFault reappear. The response from tinyproxy is in HTTP/1.1, like BorderManager's. So... the rule so far is: if PHP Soap is set to use a web proxy, and the proxy returns a response of type HTTP/1.1 with no Content-Length header, this SoapFault will occur. ------------------------------------------------------------------------ [2006-03-18 22:30:16] [EMAIL PROTECTED] Dmitry, please take a look at it. ------------------------------------------------------------------------ [2006-03-18 22:12:16] robertg2 at hope dot ac dot uk Checked it out - the other services contain a 'Content-Length' HTTP header in the response to the soapcalls. The amazon.com ItemLookup service referred to in this report does not. ------------------------------------------------------------------------ [2006-03-18 21:10:36] [EMAIL PROTECTED] How do I know that? If you can check it out - please do it and tell us. ------------------------------------------------------------------------ [2006-03-18 20:56:28] robertg2 at hope dot ac dot uk That is correct. I don't pretend to have a full grasp of the problem, but may I suggest/speculate/guess that those web services that work through the proxy for me either use chunked data or specify a value in the Content-length header in their response(s). ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/36749 -- Edit this bug report at http://bugs.php.net/?id=36749&edit=1
