#42387 [Opn]: Streams layer has no error notification facility

From: Date: Tue, 18 Sep 2007 12:58:13 +0000
Subject: #42387 [Opn]: Streams layer has no error notification facility
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-117646@lists.php.net to get a copy of this message
ID: 42387 User updated by: chad at herballure dot com -Summary: Error notification callback not called Reported By: chad at herballure dot com Status: Open -Bug Type: Documentation problem +Bug Type: Feature/Change Request Operating System: Linux PHP Version: 5.2.4RC2 New Comment: In that case, there needs to be a way to get errors from the streams layer in userspace. I need to _handle errors_, and the documentation is irrelevant if the capability is lacking. (The only alternative I see is using an error_handler to parse the warning string, which is easily broken by locale or strings changes. I quit using streams and switched to cURL as a workaround, although I'd really prefer streams.) Updating summary/category to reflect the problem I'd like to see fixed. Previous Comments: ------------------------------------------------------------------------ [2007-08-23 10:27:35] jani@php.net It's not an error callback, it's notification callback. Try this and you'll see what it actually does: <?php function stream_err() { $args = func_get_args(); var_dump($args); } $ctx = stream_context_create(array('http'=>array('method'=>"GET",'header'=>"Accept-language: en\r\nCookie: foo=bar\r\n"))); $ret = stream_context_set_params($ctx, array('notification'=>'stream_err')); $fp = fopen('http://www.example.com', 'r', false, $ctx); ?> The streams documentation really needs some loving care.. :) ------------------------------------------------------------------------ [2007-08-22 18:34:48] chad at herballure dot com Description: ------------ The streams API doesn't appear to actually call the error callback. This is definitely true if the connection fails, or if the expected hostname doesn't match the SSL certificate. In the latter case, there is no reliable way of detecting the error. The reproduce code is a cut-down version of a test script being run through the CLI, while I figure out the streams API. I get the same behavior from 5.2.3 and 5.2.4RC2. Reproduce code: --------------- <?php $HOST_NAME = 'secureservicesonline.com'; $CA_DIR = '/etc/ssl/certs'; // change this if needed function stream_err() { $args = func_get_args(); echo("[stream_err, args="); print_r($args); // which are undocumented, btw echo("]\n"); } $ctx = stream_context_create(array('ssl'=>array('verify_peer' => true, 'CN_match' => "$HOST_NAME.invalid", 'capath'=>$CA_DIR))); $ret = stream_context_set_params($ctx, array('notification'=>'stream_err')); var_dump($ret); $errno = $errstr = null; $fp = stream_socket_client("ssl://$HOST_NAME:443", $errno, $errstr, 30, STREAM_CLIENT_CONNECT, $ctx); var_dump($errno); var_dump($errstr); if( $fp !== false ) { fclose($fp); } ?> Expected result: ---------------- [stream_err, args=Array ( ...... )] Actual result: -------------- PHP Warning: stream_socket_client(): Peer certificate CN=`secureservicesonline.com' did not match expected CN=`secureservicesonline.com.invalid' in /.../https_client.php on line 52 Warning: stream_socket_client(): Peer certificate CN=`secureservicesonline.com' did not match expected CN=`secureservicesonline.com.invalid' in /.../https_client.php on line 52 ------------------------------------------------------------------------ -- Edit this bug report at http://bugs.php.net/?id=42387&edit=1

« previous php.bugs (#117646) next »