Log message:
Changes 1.4.0:
This release includes number of fixes for libnghttp2. We briefly explain notable \
bug fixes here. Previously, libnghttp2 ignored CONTINUATION frames if preceding \
HEADERS frame contained padding. The appearance of CONTINUATION is rare these \
days, but padding is used in some services already, and we may see CONTINUATION \
somewhere too. The second and third bugs are SETTINGS and HPACK dynamic table \
size related bugs. The second bug is that previously libnghttp2 did not shrink \
to minimum size of requested dynamic table size contained in SETTINGS frame sent \
from local endpoint if it contains several SETTINGS_HEADER_TABLE_SIZE. Now it is \
corrected, and libnghttp2 shrinks to the minimum size. The third bug is that due \
to the ambiguous text in RFC 7540 and 7541, we interpreted that if receiver \
received SETTINGS containing SETTINGS_HEADER_TABLE_SIZE, it always has to send \
dynamic table size update in the next compressed header block. But it turns out \
that it is not the intention of the
specification author. The intended behaviour is the receiver is required to send \
dynamic table size update only when it really changed maximum dynamic table \
size. Depending on the SETTINGS_HEADER_TABLE_SIZE and the current maximum \
dynamic table size, the table size may not change.
|