#48524 [Com]: Timeout setting is not considered on SOAP+HTTPS calls

2010-01-18 Thread johnm04 at gmail dot com
 ID:   48524
 Comment by:   johnm04 at gmail dot com
 Reported By:  valer_crisan at yahoo dot com
 Status:   Open
 Bug Type: SOAP related
 Operating System: Linux
 PHP Version:  5.2.9
 New Comment:

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(10) 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(10)'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.


Previous Comments:


[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.1view=markup

which means that it is possible to do similar thing in php



[2009-09-14 12:36:08] maximchick at gmail dot com

5.2.10 the bug still here



[2009-09-14 10:00:05] maximchick at gmail dot com

Found the same behaviour: when connecting to SOAP server over http,
default_socket_timeout works as expected, but with HTTPS client hangs
forever.

stream_context_create with timeout and connection_timeout options for
SSL wrapper also not works.



[2009-09-09 11:03:27] sjo...@php.net

See also bug #41631



[2009-07-07 17:58:03] akomasinski at gmail dot com

I am seeing the same issue on PHP 5.3.0 on windows and linux.  The
issue seems to be exactly as described.



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/48524

-- 
Edit this bug report at http://bugs.php.net/?id=48524edit=1



#48524 [Com]: Timeout setting is not considered on SOAP+HTTPS calls

2010-01-18 Thread johnm04 at gmail dot com
 ID:   48524
 Comment by:   johnm04 at gmail dot com
 Reported By:  valer_crisan at yahoo dot com
 Status:   Open
 Bug Type: SOAP related
 Operating System: Linux
 PHP Version:  5.2.9
 New Comment:

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.


Previous Comments:


[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(10) 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(10)'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.1view=markup

which means that it is possible to do similar thing in php



[2009-09-14 12:36:08] maximchick at gmail dot com

5.2.10 the bug still here



[2009-09-14 10:00:05] maximchick at gmail dot com

Found the same behaviour: when connecting to SOAP server over http,
default_socket_timeout works as expected, but with HTTPS client hangs
forever.

stream_context_create with timeout and connection_timeout options for
SSL wrapper also not works.



[2009-09-09 11:03:27] sjo...@php.net

See also bug #41631



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/48524

-- 
Edit this bug report at http://bugs.php.net/?id=48524edit=1