ID: 48182 Updated by: srina...@php.net Reported By: frase at cs dot wisc dot edu -Status: Feedback +Status: Closed Bug Type: OpenSSL related Operating System: * PHP Version: 5.2.11RC1 Assigned To: srinatar New Comment:
This bug has been fixed in SVN. Snapshots of the sources are packaged every three hours; this change will be in the next snapshot. You can grab the snapshot at http://snaps.php.net/. Thank you for the report, and for helping us make PHP better. the original reported issue is now resolved in all platforms. however, the bug submitter is noticing the same script behaving differently on windows. and has filed a separate bug to track this (#49295). hence, closing this as fixed in svn . Previous Comments: ------------------------------------------------------------------------ [2009-08-19 13:54:53] frase at cs dot wisc dot edu It is exactly the same script that produces this new error for me on Windows. However as you request, I have opened a new bug#49295 for this behavior. ------------------------------------------------------------------------ [2009-08-19 03:35:30] srina...@php.net i was able to verify this successfully by compiling php 5.2.11 rc1 (did not use the rc1 candidate build) on windows and run the below script that you attached as part of this bug report. now, if you have a different test script that is causing this issue then i would suggest that you should better file a separate bug and attach this new test case. this way , we can track different issues separately rather than overloading this bug. ------------------------------------------------------------------------ [2009-08-18 13:40:41] frase at cs dot wisc dot edu The new problem could be unrelated, it is definitely different behavior than before. I've reported it here only because it still only affects ssl:// socket connections opened asynchronously -- tcp sockets open fine (both sync and async), and ssl sockets open fine synchronously. Also, I have a new clue. The very first attempt (ssl+async) on a freshly booted Apache server works fine. It is only on the second and subsequent attempts that the new warnings appear and the socket won't open. When I restart Apache, it works one more time. This is Windows 2000 Professional SP4, Apache 2.2.11, with the posted PHP 5.2.11RC1-Win32-VC6 binary (threadsafe, and apparently including OpenSSL 0.9.8k) configured as an Apache module (not CGI). Hope that helps. ------------------------------------------------------------------------ [2009-08-18 02:11:12] srina...@php.net thanks for verifying it. let me try this again with php 5.2.11rc1 and see why it is happening (again). ------------------------------------------------------------------------ [2009-08-14 13:56:38] frase at cs dot wisc dot edu To clarify, I tested the posted patch by recompiling 5.3.0 on Ubuntu Linux, and the fix worked. I was not able to test the patch in 5.2.10 on Windows as I have no suitable build environment. The posted 5.2.11RC1 binaries (under Apache 2.2.11) now exhibit this new problem. ------------------------------------------------------------------------ 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/48182 -- Edit this bug report at http://bugs.php.net/?id=48182&edit=1
