Edit report at http://bugs.php.net/bug.php?id=48216&edit=1
ID: 48216
Comment by: pguy at vrcis dot com
Reported by: mark at everytruckjob dot com
Summary: PHP Fatal error: SOAP-ERROR: Parsing WSDL: Extra
content at the end of the doc
Status: Open
Type: Bug
Package: SOAP related
Operating System: CentOs 5.3
PHP Version: 5.3.0RC2
Block user comment: N
New Comment:
Experiencing the same behavior going against a web service hosted on an
Oracle
10g Application Server.
It's using chunked transfer encoding.
my PHP setup:
Downloaded php-5.3.3-nts-Win32-VC9-x86.zip today to my Windows 7 64-bit
PC,
renamed php.ini-development to php.ini, uncommented extension_dir,
extension=php_soap.dll, and soap.wsdl_cache_dir.
Ran php from the command line using a php file containing the script
with the
SoapClient.
Request headers:
GET /path/endpoint?WSDL HTTP/1.1
Host: oas.internal.local:80
Authorization: Basic dGVzdDp0ZXN0
Connection: close
Response headers:
HTTP/1.1 200 OK
Date: Thu, 30 Sep 2010 22:45:45 GMT
Server: Oracle-Application-Server-10g/10.1.2.0.2 Oracle-HTTP-Server
Cache-Control: private
Connection: close
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8
The body is broken into several chunks, all of which appear to have the
correct
sizes.
Interestingly, I tried one of the wsdl urls posted in an earlier comment
-
http://webapi.allegro.pl/uploader.php?wsdl - and it worked fine. I
noticed that
its body was just one chunk.
As others have noted, the wsdl that 5.3.3 is rejecting works just fine
in 5.2.x.
-Peter
Previous Comments:
------------------------------------------------------------------------
[2010-09-22 05:36:08] tonybrown at cox dot net
I downloaded the latest 5.3.3, running on Fedora 13, ran into this
problem, is there a good solution? I may need to fall back to
5.2.something because we require WSDL. If I can't parse a WSDL file, I'm
screwed, because the ICD prescribes it. I did get non-WSDL to work, but
I'm not yet sure if that will be acceptable. I can get the same high
level functionality, but then I won't be ICD-compliant. I am also
worried that if I fall back to 5.2.something I will then run into other
bugs that 5.3.3 might have fixed.
------------------------------------------------------------------------
[2010-08-08 13:28:06] nadavvin at gmail dot com
also happen in the newly PHP version 5.3.3
------------------------------------------------------------------------
[2010-08-08 13:25:35] nadavvin at gmail dot com
also happen in the newly PHP version 5.3,3
------------------------------------------------------------------------
[2010-07-27 13:17:59] derek dot ethier at humber dot ca
I'm experiencing the same issue with the following WSDL file:
https://qa.everbridge.net/ws3/services/WebServices3?wsdl
I'm using 5.2.13 on Windows Server 2008.
Here is the XML parsing error:
object(LibXMLError)#1 (6) {
["level"]=>
int(3)
["code"]=>
int(5)
["column"]=>
int(5)
["message"]=>
string(41) "Extra content at the end of the document
"
["file"]=>
string(56) "https://qa.everbridge.net/ws3/services/WebServices3?wsdl";
["line"]=>
int(537)
}
------------------------------------------------------------------------
[2010-04-29 19:08:59] eaf at oyatel dot no
Wow, this is bad, still not fixed in PHP 5.3.2.
Can this please be fixed for PHP 5.3.3?
------------------------------------------------------------------------
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/bug.php?id=48216
--
Edit this bug report at http://bugs.php.net/bug.php?id=48216&edit=1
