From: Cygwin nghttp2 Maintainer <Brian.Inglis@SystematicSW.ab.ca>
To: Cygwin Announcements <cygwin-announce@cygwin.com>
Subject: Updated: nghttp2, libnghttp2{_14, -devel}, {python{37, 38}, mingw64-{x86_64, i686}}-nghttp2 1.45.1
Date: Sun, 26 Sep 2021 06:21:59 -0600 [thread overview]
Message-ID: <20210926062159.495-1-Brian.Inglis@SystematicSW.ab.ca> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1444 bytes --]
The following packages have been upgraded in the Cygwin distribution:
* nghttp2 1.45.1
* libnghttp2_14 1.45.1
* libnghttp2-devel 1.45.1
* python37-nghttp2 1.45.1
* python38-nghttp2 1.45.1
* mingw64-x86_64-nghttp2 1.45.1
* mingw64-i686-nghttp2 1.45.1
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:
https://nghttp2.org/
or the repo README:
https://github.com/nghttp2/nghttp2#readme
Please see below or read /usr/share/doc/nghttp2/ChangeLog after
installation for complete details of changes:
https://nghttp2.org/blog/
nghttp2 v1.45.1 Sep 21st, 2021 10:13 pm
Build
This release fixes packaging issues which lack some configuration
files in tar archives.
Nghttp2 v1.45.0 Sep 20th, 2021 5:56 pm
Lib
Stricter checks for :method: and :path pseudo header fields are
introduced.
Build
nghttp2 applications can be compiled with OpenSSL v3.0.0.
Fix warning about systemd when cmake is used.
Added build options to enable HTTP/3 and eBPF.
Nghttpx
The experimental HTTP/3 support has been added.
“dnf” (= “do not forward”) parameter is added to backend option
H2load
The experimental HTTP/3 support has been added.
SSLKEYLOGFILE environment variable support has been added.
reply other threads:[~2021-09-26 12:26 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=20210926062159.495-1-Brian.Inglis@SystematicSW.ab.ca \
--to=brian.inglis@systematicsw.ab.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).