From: "Cygwin nghttp2 Maintainer" <Brian.Inglis@Shaw.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: libnghttp2{_14,-devel}, {mingw64-x86_64-,}nghttp2 1.52
Date: Mon, 20 Feb 2023 19:50:14 -0700 [thread overview]
Message-ID: <20230220195014.49962-1-Brian.Inglis@Shaw.ca> (raw)
The following packages have been upgraded in the Cygwin distribution:
* nghttp2 1.52
* libnghttp2_14 1.52
* libnghttp2-devel 1.52
* mingw64-x86_64-nghttp2 1.52
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.
NOTE:
Support for previously deprecated Python bindings, modules, and
documentation has been dropped from this release onwards.
For more information see the project home page:
https://nghttp2.org/
or the repo README:
https://github.com/nghttp2/nghttp2#readme
See link or text below for recent changes; after installation for
complete details of changes read /usr/share/doc/nghttp2/ChangeLog.
https://nghttp2.org/blog/
V1.52 2023-02-13
Doc
sphinx_rtd_theme has been removed from the repository and archive.
Build
* The following dependencies have been updated:
- ngtcp2
- nghttp3
- OpenSSL(quictls)
- BoringSSL
- libbpf
* CMake build now checks core and extra components to find libevent.
Python
* The deprecated Python bindings has been removed.
Libnghttp2_asio
* The deprecated libnghttp2_asio has been removed.
Third-party
* llhttp and neverbleed have been updated.
Nghttpx
* This release fixes the bug that stalls TLS connection.
Integration
* This release adds more http3 integration tests.
reply other threads:[~2023-02-21 2:52 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230220195014.49962-1-Brian.Inglis@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).