Hi
On testing some more of the servers under my control i’ve managed to see both types of results. i.e. those that need a read of at least 1 byte of data and those that don’t (to display header info)
There are many differences between the environments on these servers but the one that seems to introduce this issue is when PHP is compiled with --with-curlwrappers
Consider the code
phpinfo(INFO_GENERAL);
Search the resulting webpage for “curl” if you find --with-curlwrappers listed in the Configure Command section of phpinfo then you’ll also see the problem that this thread is about.
Consider the following code
$streamOptions = array('http'=>array('method'=>"GET",'host'=>'google.com'));
$context = stream_context_create($streamOptions);
$handle = fopen('https://google.com', "rb", false, $context);
$meta = stream_get_meta_data($handle);
echo '<pre><strong>stream_get_meta_data</strong><br>';
print_r($meta);
die;
On a server WITHOUT php compiled with --with-curlwrappers i.e. what the developers of the plugin expect
stream_get_meta_data
Array
(
[wrapper_data] => Array
(
[0] => HTTP/1.0 301 Moved Permanently
... (data redacted here)
[32] => X-Frame-Options: SAMEORIGIN
)
[wrapper_type] => http
[stream_type] => tcp_socket/ssl
[mode] => r+
[unread_bytes] => 684
[seekable] =>
[uri] => https://google.com
[timed_out] =>
[blocked] => 1
[eof] =>
)
On a server WITH php compiled with --with-curlwrappers
stream_get_meta_data
Array
(
[wrapper_data] => Array
(
[headers] => Array
(
)
[readbuf] => Resource id #3
)
[wrapper_type] => cURL
[stream_type] => cURL
[mode] => rb
[unread_bytes] => 0
[seekable] =>
[uri] => https://google.com
[timed_out] =>
[blocked] => 1
[eof] =>
)
Note the differences in wrapper_type and stream_type
The wrapper_type is the important one as to the format of the returned wrapper_data
Ok Devs
I’ve given you a fix (admittedly not the prettiest code) and now i’ve given you the info on why it happens.
If i tidy my code and optimise it for both configurations do you think we can get it added to the source?
mh
