public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: "Cygwin curl Maintainer" <Brian.Inglis@Shaw.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: curl/libcurl4/-devel/-doc, mingw64-x86_64-curl 8.1.1
Date: Sat, 27 May 2023 23:37:07 -0600	[thread overview]
Message-ID: <20230527233707.45605-1-Brian.Inglis@Shaw.ca> (raw)

The following packages have been upgraded in the Cygwin distribution:

* curl			8.1.1
* libcurl4		8.1.1
* libcurl-devel		8.1.1
* libcurl-doc		8.1.1
* mingw64-x86_64-curl	8.1.1

Command line tool and Library supporting transferring files with
URL syntax, using FTP, FTPS, HTTP, HTTPS, SCP, SFTP, TFTP, TELNET, DICT, and
FILE, SSL certificates, HTTP POST, HTTP PUT, FTP uploading, HTTP form
based upload, proxies, cookies, user+password authentication (Basic,
Digest, NTLM, Negotiate...), file transfer resume, proxy tunneling and a
busload of other useful tricks.

For more information see the project home page:

	https://curl.se/

As there are multiple components and many changes each release please
see below or read /usr/share/doc/curl/RELEASE-NOTES after installation;
for complete details of changes since the previous Cygwin release see:

	/usr/share/doc/curl/CHANGES
or
	https://curl.se/changes.html


curl and libcurl 8.1.1		2023-05-23

Public curl releases:		 218
Command line options:		 251
curl_easy_setopt() options:	 302
Public functions in libcurl:	  91
Contributors:			2875

Planned upcoming removals include:

* gskit
* NSS
* support for space-separated NOPROXY patterns
* support for the original legacy mingw version 1

  See https://curl.se/dev/deprecate.html for details

This release includes the following known bugs:

* see docs/KNOWN_BUGS (https://curl.se/docs/knownbugs.html)

This release includes the following bugfixes:

 o cf-socket: completely remove the disabled USE_RECV_BEFORE_SEND_WORKAROUND [12]
 o checksrc: disallow spaces before labels [16]
 o cmake: avoid `list(PREPEND)` for compatibility [24]
 o cmake: repair cross compiling [10]
 o configure: fix --help alignment [9]
 o configure: generate a script to run the compiler [11]
 o curl_easy_getinfo: clarify on return data types [15]
 o docs: document that curl_url_cleanup(NULL) is a safe no-op [4]
 o hostip: move easy_lock.h include above curl_memory.h [14]
 o http2: double http request parser max line length [8]
 o http2: increase stream window size to 10 MB [22]
 o http2: upload improvements [21]
 o lib: fix conversion warnings with gcc on macOS
 o lib: rename struct 'http_req' to 'httpreq' [23]
 o ngtcp2: fix compiler warning about possible null-deref [3]
 o ngtcp2: proper handling of uint64_t when adjusting send buffer [1]
 o os400: update chkstrings.c [2]
 o runtests: handle interrupted reads from IPC pipes
 o runtests: use the correct fd after select [20]
 o sectransp.c: make the code c89 compatible [17]
 o select: avoid returning an error on EINTR from select() or poll() [5]
 o test425: fix the log directory for the upload
 o url: provide better error message when URLs fail to parse [18]
 o urlapi: allow numerical parts in the host name [7]
 o vquic.c: make recvfrom_packets static, avoid compiler warning [6]


                 reply	other threads:[~2023-05-28  5:38 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=20230527233707.45605-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).