You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I added this as an option in #81818 as a solution for users with corporate firewalls that MITM TLS traffic.
Reqwest 0.13.x now uses rustls-platform-verifier by default, which doesn't have the tradeoffs that rustls-native-certs had. We should now pick up and work with system certs by default, and we no longer depend on shipping our own blob of trusted PKI roots! (though wasmer still pulls this in...)
This PR was generated with Opus + OpenCode, but there was a ton of manual iteration to get it working on CI.
TLS Provider
reqwest now defaults to aws-lc-rs instead of ring. This causes a few problems:
On Windows, this requires cmake and NASM. There's a prebuilt NASM blob we can use, but it still appears to need cmake. We could install this in CI, but I don't want to make Windows development any more complicated than it already is.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I added this as an option in #81818 as a solution for users with corporate firewalls that MITM TLS traffic.
Reqwest 0.13.x now uses
rustls-platform-verifierby default, which doesn't have the tradeoffs thatrustls-native-certshad. We should now pick up and work with system certs by default, and we no longer depend on shipping our own blob of trusted PKI roots! (though wasmer still pulls this in...)This PR was generated with Opus + OpenCode, but there was a ton of manual iteration to get it working on CI.
TLS Provider
reqwestnow defaults toaws-lc-rsinstead ofring. This causes a few problems:We just use this for fetching Google Fonts, so it's not worth it: Fall back to using
ringon these platforms.CI Testing
Manually triggered a build-and-release job so that it tries to build for the whole platform matrix: https://github.com/vercel/next.js/actions/runs/20936098900
Manual Testing
Followed the test plan in #81818