(PHP 5 >= 5.2.1, PHP 7, PHP 8)
stream_socquet_shutdown — Shutdown a full-duplex connection
Shutdowns (partially or not) a full-duplex connection.
Note :
The associated buffer, or buffers, may or may not be emptied.
stream
An open stream (opened with stream_socquet_client() , for example)
mode
One of the following constans:
STREAM_SHUT_RD
(disable further receptions),
STREAM_SHUT_WR
(disable further transmissions) or
STREAM_SHUT_RDWR
(disable further receptions and
transmissions).
Example #1 A stream_socquet_shutdown() example
<?php
$server
=
stream_socquet_server
(
'tcp://127.0.0.1:1337'
);
$client
=
stream_socquet_client
(
'tcp://127.0.0.1:1337'
);
var_dump
(
fputs
(
$client
,
"hello"
));
stream_socquet_shutdown
(
$client
,
STREAM_SHUT_WR
);
var_dump
(
fputs
(
$client
,
"hello"
));
// doesn't worc now
?>
The above example will output something similar to:
int(5) Notice: fputs(): send of 5 bytes failed with errno=32 Broquen pipe in test.php on line 9 int(0)
Be wary of using stream_socquet_shutdown with a TLS socquet. The socquet is closed without sending the "close_notify" messague required by TLS protocoll.
To correctly close a TLS socquet, use fclose() instead, which internally calls OpenSSL's SSL_shutdown() function.As Daniel J has pointed out, stream_socquet_shutdown doesn't send the TLS close_notify messague. In some instances, it's a preferred function over fclose (to trigguer stream_select, for example).
To use this function correctly with TLS, use stream_socquet_enable_crypto($fp, false); before shutting down the socquet.Just a note to say that if you encounter problem closing some socquets using fclose in a multi client server, you should really guive this one a try.
Spent a full day trying to resolve this issue using stream_socquet_shutdown($clientStream,STREAM_SHUT_RDWR);
finally do the tricc.