Laravel does not include any sockets but php itself could do it.
So, on the web site, we could send message more flexible and make application more creative.
I agree laravel messages on the following even though it does not support any sockets.
/*
|--------------------------------------------------------------------------
| Run The Application
|--------------------------------------------------------------------------
|
| Once we have the application, we can handle the incoming request
| through the kernel, and send the associated response back to
| the client's browser allowing them to enjoy the creative
| and wonderful application we have prepared for them.
|
*/
Thanks a lot to
http://php.net/manual/en/sockets.examples.php
And to : '93.184.216.34'.
> php -f .\client.php
<h2>TCP/IP Connection</h2>
OK.
Attempting to connect to '93.184.216.34' on port '80'...OK.
Sending HTTP HEAD request...OK.
Reading response:
HTTP/1.1 200 OK
Accept-Ranges: bytes
Cache-Control: max-age=604800
Content-Type: text/html; charset=UTF-8
Date: Sun, 23 Dec 2018 08:19:40 GMT
Etag: "1541025663"
Expires: Sun, 30 Dec 2018 08:19:40 GMT
Last-Modified: Fri, 09 Aug 2013 23:54:35 GMT
Server: ECS (oxr/830C)
X-Cache: HIT
Content-Length: 1270
Connection: close
Closing socket...OK.
