Home » Web Services » SOAP » Bug #1868
Behaves strange on a "100" HTTP-Response
Details
| Submitted | 2004-07-14 08:43 UTC |
|---|---|
| From | stephan at wentz dot it |
| Assigned | yunosh |
| Status | No Feedback |
| Package | SOAP |
| PHP Version | 4.3.7 |
| OS | Linux |
| Roadmaps | (Not assigned) |
Comments
[2004-07-14 08:43 UTC] stephan at wentz dot it
Description:
------------
The Webservice i needed to access answered with this header:
<snip>
HTTP/1.1 100 Continue
HTTP/1.1 200 OK
Date: Tue, 15 Jun 2004 10:43:55 GMT
Server: Microsoft-IIS/6.0
COMMERCE-SERVER-SOFTWARE: Microsoft Commerce Server 2002, Enterprise Edition
X-AspNet-Version: 1.1.4322
COMMERCE-SERVER-SOFTWARE: Microsoft Commerce Server 2002, Enterprise Edition
Set-Cookie: Commerce2002_TestPersistentCookie=TestCookie; expires=Wed,
16-Jun-2004 10:43:55 GMT; path=/
Set-Cookie: Commerce2002_TestSessionCookie=TestCookie; path=/
Cache-Control: private, max-age=0
Content-Type: text/xml; charset=utf-8
Content-Length: 450
</snip>
SOAP only parsed the first HTTP/1.1-Header and got confused afterwards.
SOAP should use HTTP_Request for this, it seems to be fixed there...
See: http://marc.theaimsgroup.com/?l=pear-general&m=108731741321824&w=2
Reproduce code:
---------------
-
Expected result:
----------------
Should parse until a valid Response is found.
Actual result:
--------------
see above