Pierre Tomasina comments

Results 92 comments of


                                            Pierre Tomasina

Data read from socket doesn't match expected length

This could also explain our issue related to TLS handshake.

Data read from socket doesn't match expected length

Yes i've made some fix test. The max stream buffer size depend of the system and method used. We have to loop until the buffer is empty or the expected...

Data read from socket doesn't match expected length

Short update here, we have two possibilities to solve this issue, depending of how the PR 53 on `\Hoa\Socket` will be implemented.

@Hywan next step is to make real test with anothers Clients. Yesterday i've tried with [Go Client Gorilla](https://github.com/gorilla/websocket) but the support of TLS is not esay to enable. The Browser...

TLS Support

Huh ? Both ? It's web standard SSL handshake is one way, server side certificate. My patch fix TLS issue for let `Hoa\WebSocket\Client` work with `Hoa\WebSocket\Server` now we need make...

TLS Support

@rokha thanks for your feedback, issue is clearly related to our implementation of `Hoa\Http` beside `Hoa\WebSocket` the SSL Handshake fail. Let's encrypt is a good candidate for our test, i...

TLS Support

Hello @rokha, after couples research it seems no one really care about direct TLS encryption of websocket server because in real use case you will certainly have a Load balancer...

TLS Support

Encryption work between our Client and Server, but not with HTTPS Client.

Only one char read to buffer on secure connection

Hello @avo7 Thanks for this report, this issue is related to #77 It's good you came with fresh information. Can you share with us your HTML Client snippet ? You...