public inbox for
 help / color / mirror / Atom feed
From: "Cygwin nghttp2 Maintainer" <>
Subject: [ANNOUNCEMENT] Updated: nghttp2, libnghttp2{_14, -devel}, {python{38, 39}, mingw64-{x86_64, i686}}-nghttp2 1.49
Date: Sat, 27 Aug 2022 21:51:43 -0600	[thread overview]
Message-ID: <> (raw)

The following packages have been upgraded in the Cygwin distribution:

* nghttp2			1.49
* libnghttp2_14			1.49
* libnghttp2-devel		1.49
* python38-nghttp2		1.49
* python39-nghttp2		1.49
* mingw64-x86_64-nghttp2	1.49
* mingw64-i686-nghttp2		1.49

HTTP/2 and its header compression algorithm HPACK implementation.
The framing layer of HTTP/2 is implemented as a reusable library.
Also included are an HTTP/2 client, server, proxy, load test and
benchmarking tool, and Python modules.

For more information see the project home page:

or the repo README:

Please see below or read /usr/share/doc/nghttp2/ChangeLog after
installation for complete details of changes:

v1.49	Aug 22nd, 2022


* This release adds nghttp2_check_header_value_rfc9113 which complains
  leading and trailing white spaces. The library now uses this function
  instead of nghttp2_check_header_value when checking HTTP header fields.


* libnghttp2_asio has been moved to its own repository and got new
  maintainer. libnghttp2_asio related code in nghttp2 repository will
  not get any updates and be removed at the end of 2022.


* Python bindings have been deprecated, and will not get any updates and
  be removed at the end of 2022 due to the maintenance issues.


* Randomizing backend server selection has been added again.

* The broken PROXY-protocol when TLS is used has been fixed.

* nghttpx now removes trailing white spaces from HTTP header fields to
  align with RFC 9113.

                 reply	other threads:[~2022-08-28  3:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).