Release 2.26.2

- [BUGFIX] Do not drop incoming data when STOP_SENDING is received.
- [BUGFIX] Receipt of STOP_SENDING should not cause read-reset.
- [BUGFIX] Allow stream writes after receiving RESET.
- [BUGFIX] Typo in stream: ANDing enum with wrong flag.
- [BUGFIX] Reset elision: do not use zero as special stream ID value,
  for zero is a valid stream ID in IETF QUIC.
- [API] Add optional on_conncloseframe_received() callback.
- Use zero error code in RESET stream sent in response to STOP_SENDING.
This commit is contained in:
Dmitri Tikhonov 2020-12-23 09:06:05 -05:00
parent efa7f95dff
commit 292abba1f8
11 changed files with 165 additions and 33 deletions

View file

@ -1294,7 +1294,7 @@ the engine to communicate with the user code:
signals the user to stop reading, writing, or both.
Note that resets differ in gQUIC and IETF QUIC. In gQUIC, `how` is
always 2; in IETF QUIC, `how` is either 0 or 1 because on can reset
always 2; in IETF QUIC, `how` is either 0 or 1 because one can reset
just one direction in IETF QUIC.
This callback is optional. The reset error can still be collected

View file

@ -26,7 +26,7 @@ author = u'LiteSpeed Technologies'
# The short X.Y version
version = u'2.26'
# The full version, including alpha/beta/rc tags
release = u'2.26.1'
release = u'2.26.2'
# -- General configuration ---------------------------------------------------