We released nghttp2 v1.2.1.
We released v1.2.0 in Aug 9, but immediately after the release, we found some stability issues in nghttpx. We have done some hard work to fix them, and here is the v1.2.1 release.
Since most of the interesting stuff was done in v1.2.0, we also describe the changes in v1.2.0 in this blog post.
Previously, nghttp2 library only allow one outgoing in-flight SETTINGS frame. Now its limitation was gone, and application can issue multiple SETTINGS frame as it wants.
Previously, nghttp2 library allows incoming dynamic table size update in the middle of compressed header block. But RFC 7541 clearly states that it is restricted to the beginning of the header block. Now nghttp2 checks this restriction strictly. nghttp2 library also strictly checks whether peer sends dynamic table size update in response to header table change in SETTINGS.
Tom Harwood offered the patch to improve English text in tutorial documentation. Now they should be more readable.
nghttpx gets many advanced features in this release (and ironically (or inevitably?), it was the cause of the instability issue). Now it supports sharing session cache and TLS ticket keys among multiple nghttpx instance using memcached. We use OpenSSL, and basically it does not support asynchronous session cache lookup, but we use the same trick invented by Kazuho Oku in his awesome h2o project. If memcached based TLS ticket key sharing is not used, nghttpx generates TLS ticket keys internally as usual. From this release, it now generates new key every 1 hour, and its life time is 12 hours.
--tls-ticket-key-cipher option to change the cipher to
encrypt session ticket. Currently, AES-128-CBC and AES-256-CBC are
supported. Previously, we did not have this option, and cipher is
always AES-128-CBC. Because of limitation in current OpenSSL
implementation, we cannot use AES-GCM for ticket encryption at the
Previously nghttpx HTTP/2 backend connection did not enable any TLS resumption. Now it is enabled.
Previously, by default, nghttpx rewrote Host (or :authority) header
field for backend request using backend server’s address. This was
done because apache and nginx do this by default. But we have heard
that in most of the use case for nghttpx, users disable this feature
--no-host-rewrite. So we decided to not to rewrite Host
header field by default. Instead, we added
--host-rewrite option to
We fixed bug in nghttpd that it sent response body even if status code was 304.
Nora Shoemaker sent us a patch to add connection rate based execution. See #299 for the intended use case.