|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #64589 SOAP arrays with non-sequentially indexed keys ignored
Submitted: 2013-04-05 09:32 UTC Modified: 2013-04-10 20:09 UTC
Avg. Score:4.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: Assigned: dmitry (profile)
Status: Not a bug Package: SOAP related
PHP Version: 5.5.0beta1 OS: Linux
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:
42 + 47 = ?
Subscribe to this entry?

 [2013-04-05 09:32 UTC]
When passing a non-sequentially numerically indexed array to a SOAPClient method, it gets ignored as "empty".

Test script:

Expected result:

Actual result:


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2013-04-06 15:44 UTC]
-Status: Open +Status: Assigned -Assigned To: +Assigned To: dmitry
 [2013-04-09 10:43 UTC]
-Status: Assigned +Status: Not a bug
 [2013-04-09 10:43 UTC]
This is the expected behavior.

The value you are passing in brokenStrings does not conform to WSDL specification (it can't be transferred without data lose). You may use Apache Map extension to pass array with indexes.
 [2013-04-10 20:09 UTC]
I understand the reasoning that the data cannot be transferred without data loss.

But I'd like to get notified about that the data I want to send cannot be sent and will be ignored - an E_WARNING for example. Currently, I also suffer a data loss - and it goes unnoticed.
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Thu Jun 20 22:01:29 2024 UTC