-
Notifications
You must be signed in to change notification settings - Fork 86
fix: enforce a single edge entrypoint for next edge handler #2866
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
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
📊 Package size report 0%↑
Unchanged files
🤖 This report was automatically generated by pkg-size-action |
2e0b97a
to
179a473
Compare
mrstork
commented
Apr 22, 2025
384fde1
to
cc24880
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
There exist next site configurations that generate multiple edge handlers with potentially overlapping path patterns. This can cause multiple edge handler executions for a single request, thus causing middleware to be run multiple times for a single request, and finally also multiple lambda invocations for a given request. These changes ensure we only generate a single next runtime edge handler for a given site.
Fixes FRB-1736
Fixes FRB-580
Fixes #2470
Tests
Built locally and deployed a site with the following components
Can also run
./run-local-test.sh test/e2e/middleware-responses
on this branch to validate two set-cookie headers are not being added to the response