|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #38005 SoapFault faultstring doesn't follow encoding rules
Submitted: 2006-07-04 13:00 UTC Modified: 2006-07-10 07:42 UTC
From: afalak at poczta dot onet dot pl Assigned: dmitry (profile)
Status: Closed Package: SOAP related
PHP Version: 5CVS-2006-07-04 (CVS) OS: Windows 2000
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 !
Your email address:
Solve the problem:
49 + 36 = ?
Subscribe to this entry?

 [2006-07-04 13:00 UTC] afalak at poczta dot onet dot pl
When encoding is set for both SoapClient and SoapServer (i.e. ISO-8859-1) parameters are encoded automatically. But this doesn't apply to SoapFault. Including any national character in fault string causes an error "Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in ..."

Reproduce code:
$client = new SoapClient('a.wsdl'
		,array('encoding'	=> 'ISO-8859-1')
$res = $client->Test();

function Test() {
return new SoapFault('Test', 'This is our fault: ?');
$server = new SoapServer('a.wsdl', array('encoding' => 'ISO-8859-1'));

//not important for this error

Expected result:
Soap exception with message being SoapFault's parameter

Actual result:
Fatal error: Uncaught SoapFault exception: [Client] looks like we got no XML document in ...


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2006-07-10 07:42 UTC]
Fixed in CVS HEAD and PHP_5_2.
PHP Copyright © 2001-2023 The PHP Group
All rights reserved.
Last updated: Tue Jan 31 23:03:42 2023 UTC