vakata/websocket issues and pull requests

#24 - Use SERVER with TLS cert e pk

Issue - State: open - Opened by AntonioRiccelli77 about 1 year ago

#23 - Incoming msgs larger than Base::$fragmentSize break communication in Chrome and Edge

Issue - State: closed - Opened by smindel over 1 year ago - 2 comments

#22 - Server::connected() doesn't shut down the socket if Server::callbacks['validate'] returns false.

Issue - State: closed - Opened by smindel over 1 year ago - 2 comments

#21 - Error with your example

Issue - State: closed - Opened by Ganktimebaby almost 2 years ago - 1 comment

#20 - PHP Fatal error: Uncaught vakata\websocket\WebSocketException: Bad response in /Users/17tech/wwwroot/test_workman/vendor/vakata/websocket/src/Client.php:56

Issue - State: closed - Opened by zhangrenjie almost 3 years ago - 1 comment

#19 - Bad response

Issue - State: closed - Opened by alexolliveira over 3 years ago - 1 comment

#18 - Update Server.php

Pull Request - State: closed - Opened by MichaelAben almost 4 years ago

#17 - Added support for local private key

Pull Request - State: closed - Opened by MichaelAben about 4 years ago

#16 - Websocket Client connect errors

Issue - State: closed - Opened by mruz over 4 years ago

#15 - fix for empty cookies and php strict mode

Pull Request - State: closed - Opened by rtcoder over 6 years ago

#14 - strict types, fixed silence operators, code sorting, connection class, abstract server, abstract client

Pull Request - State: closed - Opened by Byter09 almost 7 years ago - 4 comments

#13 - PHP 7, cleanup, small improvements

Pull Request - State: closed - Opened by Byter09 almost 7 years ago - 3 comments

#12 - Additional new functionality

Issue - State: closed - Opened by Byter09 almost 7 years ago - 5 comments

#11 - Upgrade to PHP 7.*

Issue - State: closed - Opened by Byter09 almost 7 years ago - 2 comments

#10 - Quickfix for PHP 7+ compatibility

Pull Request - State: closed - Opened by Byter09 almost 7 years ago - 2 comments

#9 - RFC 6455 close frame not up to specification

Issue - State: closed - Opened by mmowbray about 8 years ago

#8 - Cannot drop connection to a client

Issue - State: closed - Opened by mmowbray about 8 years ago - 1 comment

#7 - can't receive unix signals while reading

Issue - State: closed - Opened by sctt over 8 years ago - 1 comment

#6 - Timeout

Issue - State: closed - Opened by mruz over 8 years ago - 1 comment

#5 - wss

Issue - State: closed - Opened by mruz over 8 years ago - 14 comments

#4 - Websocket invalid frame header

Issue - State: closed - Opened by mruz over 8 years ago - 3 comments

#3 - Broken pipe

Issue - State: closed - Opened by mruz over 8 years ago - 6 comments

#2 - Server, disconnect after callback

Pull Request - State: closed - Opened by mruz over 8 years ago

#1 - Should be the tick running as first callback?