LiteSpeed Tech
LiteSpeed Tech
Good. that is helpful. As you can see, lsquic call `SSL_do_handshake()` at ``` #9 0x000055555558cdba in iquic_esfi_handshake (enc_sess=0x555555ad0010) at ../src/liblsquic/lsquic_enc_sess_ietf.c:1905 ``` and check the return and call `SSL_get_error()`, handle the...
SSL_ERROR_WANT_READ is not a real/fatal error, just the SSL need to read more data to complete the handshake. All SSL handshake will go through this to complete the handshake. Looks...
Yes, it is a memory leak, you can try the following patch ``` diff --git a/src/liblsquic/lsquic_stock_shi.c b/src/liblsquic/lsquic_stock_shi.c index b6807cf8..61f36140 100644 --- a/src/liblsquic/lsquic_stock_shi.c +++ b/src/liblsquic/lsquic_stock_shi.c @@ -42,8 +42,6 @@ struct hash_elem...
It is in release v3.1.2 already, assume it has been fixed.
Not supported yet.
Maybe need some improvements on the client side. Pull request are welcome.
I think it has been taken care of in https://github.com/litespeedtech/lsquic/blob/b46a5b19bb372d531b567bf899452149c533eb87/src/liblsquic/lsquic_engine.c#L1906-L1910
No further update, I assume it is a false positive.
I think you have find the answer. It is the way it works. Since the stateless reset token is saved in memory, not in a persistent storage, restart server will...
Currently there is no public API to access the statistics, maybe can move `struct conn_stats` out of lsquic_conn.h, into lsquic.h, and add a few API functions to access it.