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.53
Date: Sat, 13 May 2023 22:23:06 -0600 [thread overview]
Message-ID: <20230513222306.11655-1-Brian.Inglis@Shaw.ca> (raw)
The following packages have been upgraded in the Cygwin distribution:
* nghttp2 1.53
* libnghttp2_14 1.53
* libnghttp2-devel 1.53
* mingw64-x86_64-nghttp2 1.53
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 previous 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/
1.53 May 10th, 2023
lib
* libnghttp2 uses ngtcp2/sfparse to parse Structured Field Values.
build
The following dependencies have been updated:
* ngtcp2
* nghttp3
* OpenSSL (quictls)
* BoringSSL
third-party
* Bumped mruby to 3.2.0.
nghttpx
* Sends NEW_TOKEN on path change.
* Fixes numeric hostname verification in peer certificate.
* When quitting, waits for all worker processes to stop.
Previously, we just exit the event loop when the last process exits.
But because of the bug, it does not work as intended.
* Logs a correct PID on fork.
* Waits for new worker process to be ready before sending graceful
shutdown event to existing worker processes to avoid down time during
configuration reload.
* Fixes bug that causes 400 response after HTTP upgrade failure.
reply other threads:[~2023-05-14 4:25 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=20230513222306.11655-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).