php.net |  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #66226 WSDL-based SOAP server fails to receive more than 32kb of data
Submitted: 2013-12-03 13:13 UTC Modified: 2024-08-26 18:05 UTC
Votes:1
Avg. Score:3.0 ± 0.0
Reproduced:0 of 1 (0.0%)
From: andreas dot lindemann at de dot bp dot com Assigned:
Status: Not a bug Package: SOAP related
PHP Version: 5.5.6 OS: Solaris
Private report: No CVE-ID: None
Welcome back! If you're the original bug submitter, here's where you can edit the bug or add additional notes.
If you forgot your password, you can retrieve your password here.
Password:
Status:
Package:
Bug Type:
Summary:
From: andreas dot lindemann at de dot bp dot com
New email:
PHP Version: OS:

 

 [2013-12-03 13:13 UTC] andreas dot lindemann at de dot bp dot com
Description:
------------
We have encountered an issue that when using a SOAP webservice where client/server are both PHP-based and using a WSDL, the server fails to receive more than a certain amount of data (tests showing the limit is 32768 bytes here) in a stdClass object.
The following test script will fail with around 40.000 bytes. If the "for" loop is reduced to let's say 20000 iterations, then the script will succeed and deliver the expected result.

Test script:
---------------
Server, Client and WSDL code can be found here (bug tool wouldn't accept the content):

http://pastebin.com/VcvqgS7z



Expected result:
----------------
Data written to testsoap.log.

Actual result:
--------------
Webserver reports HTTP 500, however there is no error in the PHP log.
In server.php, code after $server->handle(); will not be executed, indicating that the PHP script has aborted.
No data is written to the testsoap.log.


Patches

Pull Requests

History

AllCommentsChangesGit/SVN commitsRelated reports
 [2024-08-26 18:05 UTC] nielsdos@php.net
-Status: Open +Status: Not a bug
 [2024-08-26 18:05 UTC] nielsdos@php.net
Thank you for taking the time to report a problem with PHP.
Unfortunately you are not using a current version of PHP --
the problem might already be fixed. Please download a new
PHP version from http://www.php.net/downloads.php

If you are able to reproduce the bug with one of the latest
versions of PHP, please change the PHP version on this bug report
to the version you tested and change the status back to "Open".
Again, thank you for your continued support of PHP.

I tried reproducing this in various ways and was unable to, I believe this has been fixed in the meantime; or was related to a configuration issue with your webserver.
 
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sat Dec 21 18:01:29 2024 UTC