Edit report at https://bugs.php.net/bug.php?id=48524&edit=1
ID: 48524
Updated by: rdlowrey@php.net
Reported by: valer_crisan at yahoo dot com
Summary: Timeout setting is not considered on SOAP+HTTPS
calls
-Status: Open
+Status: Closed
Type: Bug
Package: SOAP related
-Operating System: Linux
+Operating System: *
-PHP Version: 5.2.9
+PHP Version: 5.2 - 5.6
-Assigned To:
+Assigned To: rdlowrey
Block user comment: N
Private report: N
New Comment:
This issue has been addressed by the resolution to Bug #41631 (of which this report is a duplicate):
https://bugs.php.net/bug.php?id=41631
The fix has been applied to the 5.4, 5.5, 5.6 and master branches and will appear in the following
forthcoming releases:
- 5.4.33
- 5.5.17
- 5.6.0-rc4
Previous Comments:
------------------------------------------------------------------------
[2014-08-06 14:29:20] m dot staab at complex-it dot de
It feels like I experience this problem on
Ubuntu 12.04.4 LTS
PHP 5.4.30-1+deb.sury.org~precise+1
------------------------------------------------------------------------
[2014-02-06 09:52:16] bhimraogadge at gmail dot com
I am facing the same issue. I have set 'default_socket_timeout' to 300 and expected the
timeout should occur not more than 300 sec. But the soap call went for even 6400 seconds.
Is the issue is resolved in higher version? I am using version 5.3.
Is there any work around for this bug?
------------------------------------------------------------------------
[2010-01-18 17:43:11] johnm04 at gmail dot com
To clarify my comment on [18 Jan 5:25pm UTC], timeouts for the WSDL portion of the process (as
distinct from the actual SOAP part) only partially work.
When the WSDL is a script which only has a long sleep() in it, and is accessed over httpS, the
connection does not timeout within a reasonable length of time.
------------------------------------------------------------------------
[2010-01-18 17:25:13] johnm04 at gmail dot com
I'm getting this issue on 5.2.0.
WSDL retrieval works fine in various network timeout related tests Host pingable but no apache
running, case where WSDL is a script with sleep(100000) and default_socket_timeout set both work.
However actual Soap endpoint (url provided in <service> section of WSDL - the script that does
the work being provided) does not behave appropriately in various scenarios:
1. Server is pingable, but no apache service running.
connection_timeout = 60
default_socket_timeout = 60
http / https both tested.
I'd expect a soap exception or some sort of warning after 60
seconds or so, but the client just sits there indefinitely.
2. Server is pingable and Soap server script is present but just sleep(100000)'s
connection_timeout = 60
default_socket_timeout = 60
http / https both tested.
Again I'd expect an exception of some sort or a warning but the
client does not return in any reasonable length of time.
If there's a more appropriate bug report for this comment or if a new report is needed
I'll stick it there.
------------------------------------------------------------------------
[2009-12-11 13:00:11] arekm at maven dot pl
5.2.11 and 5.3.1, too.
example on maing ssl reads and writes timeoutable in python m2crypto
http://cvs.fedora.redhat.com/viewvc/F-12/m2crypto/m2crypto-0.18-timeouts.patch?revision=1.1&view=markup
which means that it is possible to do similar thing in php
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=48524
--
Edit this bug report at https://bugs.php.net/bug.php?id=48524&edit=1