next: Add support for turning off preflight checks #87310
Conversation
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
Whilst very useful in a lot of workloads, if you know you will never have a redirect, it is a wasted request. This PR was mostly AI generated with Cursor, but I manually tested and added the Rust code.
nextjs-bot
added
Documentation
Collaborator
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What?
Adds support for turning off preflight HEAD requests.
Note I was struggling to test this locally, everything compiles okay, but I was struggling with getting the next build to be within another project. I tried both the tar and linking methods, but had issues with it saying next was outside the project. I am happy to test locally if someone could lend me pointers here.
Why?
For a lot of sites, this is useful. However, for many sites, this is a unneeded request.
How?
Adds a Next configuration option that turns off preflight HEAD requests for those cases.