|
php.net | support | documentation | report a bug | advanced search | search howto | statistics | random bug | login |
PatchesPull RequestsHistoryAllCommentsChangesGit/SVN commits
[2004-10-05 14:45 UTC] thetaphi@php.net
[2004-10-05 14:50 UTC] derick@php.net
[2004-10-05 15:02 UTC] thetaphi@php.net
[2004-12-01 19:23 UTC] dmitry@php.net
[2004-12-01 19:48 UTC] thetaphi@php.net
[2007-02-15 09:15 UTC] lsmith@php.net
[2007-02-15 15:12 UTC] dmitry@php.net
[2007-02-23 01:00 UTC] php-bugs at lists dot php dot net
|
|||||||||||||||||||||||||||||||||||||
Copyright © 2001-2025 The PHP GroupAll rights reserved. |
Last updated: Sat Nov 01 07:00:01 2025 UTC |
Description: ------------ I get the error message "Error Fetching http body, No Content-Length, connection closed or chunked data [faultcode]" when try to communicate with Sybase EAServer via SOAP. When redirecting the web services via a Proxy-Plugin in an iPlanet webserver everything works ok. It seems that EAServer sends some bad encoded HTTP body. When changing the SOAP extension code to only support HTTP/1.0, everything works. How about introducing an additional option to SoapClient named "http_version" that can be set to 1.1 or 1.0 (default 1.1). At this time "1.1" is hardcoded into php_http.c. When 1.0 is on, "Connection:" should be assumed as "close". Something other: If the extension CURL is used, why not use CURL for sending SOAP requests? Reproduce code: --------------- <h1>SOAP Test</h1> <?php $ws=new SoapClient("http://ws.pangaea.de:8084/ws/services/WebServices?wsdl",array('trace'=>TRUE)); try { $res=$ws->metadata("10.1594/PANGAEA/206854"); } catch (SoapFault $sf) { echo "<pre>".print_r($sf)."</pre>"; } echo "<h2>Request</h2><pre>".htmlspecialchars($ws->__getLastRequest())."</pre><h2>Response</h2><pre>".htmlspecialchars($ws->__getLastResponse())."</pre>"; echo "<h2>Decoded</h2><pre>"; print_r($res); ?> </pre> Expected result: ---------------- no SoapFault