DRUPAL CORE UPDATE VULNERABILITY UPGRADE

Users unable to upgrade may consider an alternative approach to use your own redirect middleware, rather than ours. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.7 or 7.4.4. Affected Guzzle 7 users should upgrade to Guzzle 7.4.4 as soon as possible. We now always strip it, and allow the cookie middleware to re-add any cookies that it deems should be there. Prior to this fix, only cookies that were managed by our cookie middleware would be safely removed, and any `Cookie` header manually added to the initial request would not be stripped. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, or on making a request to a server which responds with a redirect to a a URI to a different host, we should not forward the `Cookie` header on. In affected versions the `Cookie` headers on requests are sensitive information. Guzzle is an open source PHP HTTP client. Alternately users may simply disable redirects all together if redirects are not expected or required. Users unable to upgrade may consider an alternative approach which would be to use their own redirect middleware.

Prior to this fix, `https` to `http` downgrades did not result in the `Authorization` header being removed, only changes to the host. This is much the same as to how we don't forward on the header if the host changes. On making a request using the `https` scheme to a server which responds with a redirect to a URI with the `http` scheme, we should not forward the `Authorization` header on. In affected versions `Authorization` headers on requests are sensitive information.

Drupal core update vulnerability