Releases: litespeedtech/lsquic
Releases · litespeedtech/lsquic
RFC compliance, memory bug fixes and fine tunings
- More strict RFC compliance.
- Minimize packet generated when send STREAM_BLOCKED frame
- Fix memory management bugs.
- Fix memory leak in unit tests.
Optimize STREAM_BLOCKED frame generation
- Avoid putting STREAM_BLOCKED frame in a separate packet.
Fix send_ctl, logging, CID storage
- Fix send_ctl bug.
- Make log ID consistent
- Reduce memory usage for storing CIDs.
QUICv2, Version Negotiation, handshake/interop improvements
- Add support for QUICv2 (RFC9369).
- Add support for version negotiation (RFC9368).
- Retry packet for address validation.
- Improve handshake under high packet loss/corruption.
- Improve QUIC interop results
Fix blocked header stream, packet resize
- Fix blocked header encoding stream due to connection flow control congestion.
- Fix qeh_write_headers bug for Windows.
- Fix corner case for packet resizing.
Fix PATH validation, STOP_SENDING and memory leaks
- Improve path validation logic to avoid sending padded packet to unverified peer, follow 3X anti-amplification rule.
- Optimize application callback when STOP_SENDING frame is received.
- Improve new connection callback logic.
- Improve handling of a closed connection.
- Update BoringSSL to the most recent version.
- Fix memory leaks in gquic handshake and packet handling.
- Update ls-qpack to 2.5.1, ls-hpack to 2.3.1 to address compiler warnings
Fix decoder, memory leak and assert failure
- Update ls-qpack to 2.5.0 to address a decoder bug
- Assertion failure if poison packet was acked
- Fix packet_in pool memory leak
Fix test binaries
- Clear connection context in on_conn_closed() callback.
Fix use-after-free, memory leak and corner cases.
- Update ls-qpack to 2.4.0 to address a use-after-free bug
- Address a few corner cases that trigger assert failures.
- Properly handle unexpected large packet for gQUIC.
- Fix memory leak in shared hash interface
- Fix IPv6 MTU detection
- Fix the wrong size used in packet regeneration.
Fix memory leak
- Fix memory leak in processing stream frames (issue #368)