
BTW, there are more you can do with cURL. Lately, I was testing HTTP/3 using cURL with the default shipped version on CentOS, but that didn’t work. Issue #1645328 by Liam Morland, darvanen, shravan sonkar, andregp, mandar.Looking to build the latest cURL from the source?ĬURL shipped with the OS may not be up-to-date, and if you need the newest version for a particular requirement, then you need to build from the source.Issue #3291780 by longwave, xjm: guzzlehttp/guzzle 6.5.8 requires guzzlehttp/psr7 ^1.9.htaccess, web.config, robots.txt, or default settings.php files in this release, so updating custom versions of those files is not necessary if your site is already on the previous release. Review the instructions for managing Guzzle updates without drupal/core-recommended. Site owners who do not use drupal/core-recommended should take care to ensure they do not accidentally update to Guzzle 7 when running composer updates. Since the above change to guzzlehttp/psr7 requires a minor-level package update, sites will not be able to update the dependency themselves as outlined in this week's PSA.

The latest guzzle versions also require guzzlehttp/psr7 1.9 or higher (up from 1.8.5), so that package is updated as well. Important update informationĭrupal core now requires guzzlehttp/guzzle 6.5.8 or higher (up from 6.5.7), or 7.4.5 or higher (up from 7.4.4). If you are upgrading from Drupal 8, read upgrading a Drupal 8 site to Drupal 9, 9.0.0 release notes, and the 9.4.0 release notes before upgrading to this release. The Security Team believes it is unlikely Drupal core or contributed modules are affected, but this release updates the dependency as a security hardening.ĭrupal 9.4.x will receive security coverage until June 2023.

Guzzle has released two security advisories: Learn more about Drupal 9.ĭrupal uses the third-party Guzzle library for handling HTTP requests and responses to external services. This is a patch (bugfix) release of Drupal 9 and is ready for use on production sites.
