"SSL: Fatal Protocol Error" with fsockopen()

[keychain]

I'm experience the infamous "SSL: Fatal Protocol Error" bug with Apache 2.x

According the fopen() documentation:

"If you are using fsockopen() to create an ssl:// socket, you are
responsible for detecting and suppressing the warning yourself."

I have been unable to determine how to go about suppressing these warnings.
Any help would be greatly appreciated.

[=?iso-8859-1?Q?Kim_Andr=E9_Aker=F8?=]

Re: "SSL: Fatal Protocol Error" with fsockopen()

keychain wrote:

I'm experience the infamous "SSL: Fatal Protocol Error" bug with
Apache 2.x
>
According the fopen() documentation:
>
"If you are using fsockopen() to create an ssl:// socket, you are
responsible for detecting and suppressing the warning yourself."
>
I have been unable to determine how to go about suppressing these
warnings. Any help would be greatly appreciated.

You can supress warnings by putting an @ directly in front of the
function name, like this:

$handle = @fsockopen("ssl ://server.example. com", 443);

--
Kim André Akerø
- kimandre@NOSPAM betadome.com
(remove NOSPAM to contact me directly)

[keychain]

Re: "SSL: Fatal Protocol Error" with fsockopen()

"Kim André Akerø" <kimandre@NOSPA Mbetadome.comwr ote in message
news:547lsmF1uq dj8U1@mid.indiv idual.net...

keychain wrote:
>

>I'm experience the infamous "SSL: Fatal Protocol Error" bug with
>Apache 2.x
>>
>According the fopen() documentation:
>>
>"If you are using fsockopen() to create an ssl:// socket, you are
>responsible for detecting and suppressing the warning yourself."
>>
>I have been unable to determine how to go about suppressing these
>warnings. Any help would be greatly appreciated.

>
You can supress warnings by putting an @ directly in front of the
function name, like this:
>
$handle = @fsockopen("ssl ://server.example. com", 443);
>
--
Kim André Akerø
- kimandre@NOSPAM betadome.com
(remove NOSPAM to contact me directly)

Kim, that's a great tip--thanks!

You can optionally use

error_reporting (0);

but this suppresses all warnings, which is obviously less desirable.

[Rik]

Re: &quot;SSL: Fatal Protocol Error&quot; with fsockopen()

keychain <somebody@somew here.comwrote:

"Kim André Akerø" <kimandre@NOSPA Mbetadome.comwr ote

>>I'm experience the infamous "SSL: Fatal Protocol Error" bug with
>>Apache 2.x
>>>
>>According the fopen() documentation:
>>>
>>"If you are using fsockopen() to create an ssl:// socket, you are
>>responsible for detecting and suppressing the warning yourself."
>>>
>>I have been unable to determine how to go about suppressing these
>>warnings. Any help would be greatly appreciated.

>>
>You can supress warnings by putting an @ directly in front of the
>function name, like this:
>>
>$handle = @fsockopen("ssl ://server.example. com", 443);

>
Kim, that's a great tip--thanks!
>
You can optionally use
>
error_reporting (0);
>
but this suppresses all warnings, which is obviously less desirable.

Supressing warnings is not the way to go. What if something else fails
then the thing you expected to fail? Just set display_errors to false in
your configuration (php.ini/http.conf/.htaccess/php-script itself) and log
them to a file. Certainly advisable for live projects. Just parse the
error log once in a while to check wether something odd is going on, or
check it when something is indeed off or it grows with an alarming pace.

And BTW, error_reporting can be set back offcourse:
$temp = error_reporting (0);
fsockopen();
error_reporting ($temp);
--
Rik Wasmus

[keychain]

Re: &quot;SSL: Fatal Protocol Error&quot; with fsockopen()

"Rik" <luiheidsgoeroe @hotmail.comwro te in message
news:op.tn7ycqp rqnv3q9@misant. ..

keychain <somebody@somew here.comwrote:

>"Kim André Akerø" <kimandre@NOSPA Mbetadome.comwr ote

>>>I'm experience the infamous "SSL: Fatal Protocol Error" bug with
>>>Apache 2.x
>>>>
>>>According the fopen() documentation:
>>>>
>>>"If you are using fsockopen() to create an ssl:// socket, you are
>>>responsibl e for detecting and suppressing the warning yourself."
>>>>
>>>I have been unable to determine how to go about suppressing these
>>>warnings. Any help would be greatly appreciated.
>>>
>>You can supress warnings by putting an @ directly in front of the
>>function name, like this:
>>>
>>$handle = @fsockopen("ssl ://server.example. com", 443);

>>
>Kim, that's a great tip--thanks!
>>
>You can optionally use
>>
>error_reportin g(0);
>>
>but this suppresses all warnings, which is obviously less desirable.

>
Supressing warnings is not the way to go. What if something else fails
then the thing you expected to fail? Just set display_errors to false in
your configuration (php.ini/http.conf/.htaccess/php-script itself) and log
them to a file. Certainly advisable for live projects. Just parse the
error log once in a while to check wether something odd is going on, or
check it when something is indeed off or it grows with an alarming pace.
>
And BTW, error_reporting can be set back offcourse:
$temp = error_reporting (0);
fsockopen();
error_reporting ($temp);
--
Rik Wasmus

Rik, thanks for your reply.

It turns out that using @ before the fsockopen() function doesn't suppress
the aforementioned SSL warrning. I therefore need to use one of the
techniques you described, which for my purposes will probably be the latter.