Edit report at http://bugs.php.net/bug.php?id=49295&edit=1
ID: 49295
Updated by: felipe@php.net
Reported by: frase at cs dot wisc dot edu
Summary: stream_socket_client() fails on SSL+async
-Status: Open
+Status: Assigned
Type: Bug
Package: OpenSSL related
Operating System: win32 only - Win 2000 Pro SP4
PHP Version: 5.2.11, 5.3.1
Assigned To: srinatar
Previous Comments:
------------------------------------------------------------------------
[2010-01-25 20:31:57] frase at cs dot wisc dot edu
This bug was "suspended automatically" by the bug system because "no
feedback was provided for this bug for over a week," although it seems
to me the feedback required is from a PHP developer, not from me.
Nonetheless, here's some feedback to reopen it: I'd still love to see
this fixed. :)
------------------------------------------------------------------------
[2009-12-19 01:00:00] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2009-12-11 01:09:59] pajoye@php.net
Having read the backlog, will you work on that or completely give up on
this bug (saw that you unassigned this bug)?
------------------------------------------------------------------------
[2009-09-16 18:22:57] srinatar@php.net
as i mentioned to you last time, our openssl implementation is
incorrectly using file based sockets instead of openssl provided 'BIO'
for underlying communication. this will require re-implementation of
some of php's openssl implementation.
this should be an issue only on windows.
------------------------------------------------------------------------
[2009-09-04 13:21:10] frase at cs dot wisc dot edu
I'm sure this is expected, but the bug remains in 5.2.11RC2.
I also noticed another clue: I mentioned previously that SSL+ASYNC works
once (but not asynchronously) after starting Apache, and then fails and
throws warnings. It turns out any SSL socket connection will cause
future SSL+ASYNC attempts to do this, even if the first one was SYNC.
So to get SSL+ASYNC to connect, it must be the very first SSL socket
opened since Apache started.
------------------------------------------------------------------------
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/bug.php?id=49295--
Edit this bug report at http://bugs.php.net/bug.php?id=49295&edit=1