Commit graph

506 commits

Author SHA1 Message Date
Sydney
0e536e04d9
Rename http_server response delay to not shadow log timestamp format (#506) 2024-06-22 14:34:34 -04:00
George Wang
0b9f50b5f0 Release 4.0.9 2024-06-12 18:32:52 -04:00
LiteSpeed Tech
c4f359fcb0
Update README.md 2024-05-28 23:42:55 -04:00
George Wang
aa3b438a67 Release 4.0.8 2024-03-12 17:46:16 -04:00
George Wang
f416a13afe Release 4.0.7 2024-02-28 19:05:41 -05:00
George Wang
851b0b0a57 update README. 2024-02-27 14:18:19 -05:00
George Wang
e8a78e300e Update docker build. 2024-02-27 14:17:30 -05:00
George Wang
c8cb6aa3e2 Release 4.0.6 2024-02-23 18:40:48 -05:00
George Wang
9c877a4177 Release 4.0.5 2024-02-07 12:32:13 -05:00
George Wang
515f453556 Release 4.0.4 2024-01-09 17:42:07 -05:00
George Wang
46c448d865 Release 4.0.4 2024-01-08 22:43:47 -05:00
Sijie Yang
9d9cde9734
Add -A option to specify congestion control algorithm for tools (#487) 2024-01-04 18:51:24 -05:00
George Wang
612a868772 Update cirrus-ci freebsd image from 12.1 to 13.2. 2024-01-04 13:13:11 -05:00
George Wang
0fa020998c remove html_sytle = /default.css . 2024-01-04 12:44:59 -05:00
George Wang
80738b914b explicitly load sphinx_rtd_theme module. 2024-01-04 12:40:56 -05:00
George Wang
f15fcff5d4 add "sphinx_rtd_theme" extension. 2024-01-04 12:27:15 -05:00
George Wang
5ed1d4cab5 explicitly set html_theme = "sphinx_rtd_theme" 2024-01-04 11:59:56 -05:00
George Wang
422496a10c add .readthedocs.yaml 2024-01-04 11:40:06 -05:00
George Wang
1163af9c41 Release 4.0.3 2023-12-26 10:23:22 -05:00
George Wang
a18ccca39e Release 4.0.2 2023-12-19 22:48:06 -05:00
Mickael Cerisier
b81a3fb15f
Fix spam of ping network frames. (#478)
After some time without activity (only keepalive), the ping frame was send in loop.
2023-10-07 10:04:01 -04:00
wangfuyu
95bc8f9663
Fix handshake hole assert failed and coredump (#479)
Co-authored-by: wangfuyu <ivanfywang@gmail.com>
2023-10-07 10:02:56 -04:00
Saigut
8890b98bb0
Update http_client.c (#474)
Add the '-B Header bypass' parameter description in the Usage of http_client
2023-09-04 08:48:03 -04:00
Hadi Frohar
c7dfaca894
prepare next advisory tick debug only when debug is enabled (#472)
Co-authored-by: hadif <hadif@checkpoint.com>
2023-08-09 17:56:33 -04:00
Hadi Frohar
836b0deadb
fix freeing frame before handling (#463)
Co-authored-by: hadif <hadif@checkpoint.com>
2023-06-23 12:20:30 -04:00
Hadi Frohar
cdb206d29f
HTTP/1.1 conversion host name fix (#466)
Co-authored-by: hadif <hadif@checkpoint.com>
2023-05-31 16:45:24 -04:00
George Wang
8fb7e2c02c Release 4.0.1 2023-05-31 16:37:47 -04:00
George Wang
1b113d192f Release 4.0.1 2023-05-18 23:33:51 -04:00
George Wang
e6987284fd Release 4.0.1 2023-05-15 14:17:23 -04:00
George Wang
2fb39e3567 Release 4.0.1 2023-05-15 00:27:34 -04:00
George Wang
3586b1e691 Release 4.0.0 2023-03-14 16:23:18 -04:00
George Wang
fbde61944b Release 4.0.0 2023-03-14 16:15:17 -04:00
George Wang
3db190c9cc Release 4.0.0 2023-03-14 14:16:13 -04:00
LiteSpeed Tech
5d469f6494
Update README.md 2023-03-14 14:06:12 -04:00
George Wang
5cf9266173 Release 4.0.0 2023-03-14 14:04:18 -04:00
George Wang
79880b469a Release 4.0.0 2023-03-14 13:29:13 -04:00
George Wang
b373fe5220 Release 3.3.1 2023-01-26 11:19:06 -05:00
Kent Ross
839893419c
Fix: do not use private openssl function to copy cert chain (#449)
Re: https://bugs.chromium.org/p/boringssl/issues/detail?id=558#c1

Since a recent change that puts boringssl's public API more in line with OpenSSL, there is a constness mismatch in the function type of `copy_X509` that may cause compilation failures.

As it turns out, the function we are using there (`sk_deep_copy`) is documented as a private API. We could use `sk_X509_deep_copy`, casting away the const in `copy_X509` to increment the refcount, but the existing function `X509_chain_up_ref` does exactly what we want here.
2023-01-19 17:33:24 -05:00
George Wang
b340210fcf Release 3.3.0 2023-01-04 15:30:57 -05:00
George Wang
48365d5741 Release 3.3.0 2023-01-04 15:21:42 -05:00
wangfuyu
b5efa50a5a
m) optimize new conn logic (#443)
1) on_new_conn only be called after handshake_ok
2) on_conn_closed only be called by ietf_full_conn_ci_destroy

Co-authored-by: wangfuyu <ivanfywang@gmail.com>
2022-12-14 11:30:34 -05:00
linsichen206
850b0a3d10
fix potential memory leak (#441)
Co-authored-by: linsc <linsc@wangus.com>
2022-12-07 14:23:43 -05:00
linsichen206
0fdfb125d7
fix memory leak when gquic handshake (#438)
Co-authored-by: linsc <linsc@wangus.com>
2022-11-27 10:34:18 -05:00
linsichen206
1a4edfcdc6
fix memory leak when gquic50 decrypt packet (#430)
* fix memory leak when gquic50 decrypt packet
fix a suspicious memory leak in gquic and iquic

* drop some redundant checking.

Co-authored-by: linsc <linsc@wangus.com>
2022-11-18 09:21:43 -05:00
wangfuyu
755143fe4a
Fix: http_server might not send MAX_STREAMS to increase limits if client cancel stream prematurely. (#435)
RFC9000 3.5.
A STOP_SENDING frame requests that the receiving endpoint send a RESET_STREAM frame. An endpoint that receives a STOP_SENDING frame MUST send a RESET_STREAM frame if the stream is in the "Ready" or "Send" state. If the stream is in the "Data Sent" state, the endpoint MAY defer sending the RESET_STREAM frame until the packets containing outstanding data are acknowledged or declared lost. If any outstanding data is declared lost, the endpoint SHOULD send a RESET_STREAM frame instead of retransmitting the data.

RFC9000 19.4. RESET_Frames
An endpoint uses a RESET_STREAM frame (type=0x04) to abruptly terminate the sending part of a stream.

Co-authored-by: wangfuyu <wangfuyu@gmail.com>
2022-11-17 21:34:57 -05:00
Simon Karan G
05698c94dc
fix typo (#429)
squic_engine_settings -> lsquic_engine_settings
2022-11-03 10:56:42 -04:00
George Wang
3bbf683f25 Release 3.2.0 2022-10-20 12:02:57 -04:00
George Wang
0e32849de5 Release 3.2.0 2022-10-20 11:47:58 -04:00
George Wang
a5347f2374 Merge branch 'master' of github.com:litespeedtech/lsquic 2022-10-19 18:35:42 -04:00
George Wang
4702105acb Update ls-qpack to v2.5.0 2022-10-19 18:34:53 -04:00