This MR contains the following updates:
|requests (source, changelog)||
Versions of Requests between v2.3.0 and v2.30.0 are vulnerable to potential forwarding of
Proxy-Authorizationheaders to destination servers when following HTTPS redirects.
When proxies are defined with user info (https://user:pass@proxy:8080), Requests will construct a
Proxy-Authorizationheader that is attached to the request to authenticate with the proxy.
In cases where Requests receives a redirect response, it previously reattached the
Proxy-Authorizationheader incorrectly, resulting in the value being sent through the tunneled connection to the destination server. Users who rely on defining their proxy credentials in the URL are strongly encouraged to upgrade to Requests 2.31.0+ to prevent unintentional leakage and rotate their proxy credentials once the change has been fully deployed.
Users who do not use a proxy or do not supply their proxy credentials through the user information portion of their proxy URL are not subject to this vulnerability.
⚠️ Added support for urllib3 2.0. ⚠️
This may contain minor breaking changes so we advise careful testing and reviewing https://urllib3.readthedocs.io/en/latest/v2-migration-guide.html prior to upgrading.
Users who wish to stay on urllib3 1.x can pin to
- Requests now defers chunked requests to the urllib3 implementation to improve standardization. (#6226)
- Requests relaxes header component requirements to support bytes/str subclasses. (#6356)
- Requests now supports charset_normalizer 3.x. (#6261)
- Updated MissingSchema exception to suggest https scheme rather than http. (#6188)
If you want to rebase/retry this MR, click this checkbox.
This MR has been generated by Renovate Bot.