v5 - Use strict routing#3454
Merged
Merged
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
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.
/fooand/foo/are now treated as different routes.Removed
Removed the normalizePath() method and all path normalization from the Router. Route paths are now used exactly as provided by the caller, with no leading-slash prepending, trailing-slash stripping, or double-slash collapsing.
'/foo'/foo'/foo'/foo/'/foo/'/foo/'/foo'/FOO'foo'(no leading slash)/fooTrailing slash handling with strict routing
This section explains how to handle trailing slashes depending on your use case.
Option 1: Accept both with a single definition (FastRoute optional segments)
Use FastRoute's optional segment syntax
[/]to define a single route that matches both:Option 2: Define both routes explicitly
If you want both
/fooand/foo/to work with different handlers:Option 3: Redirect or rewrite trailing slashes via middleware
For GET requests a permanent redirect (
301) is fine. For other request methods like POST or PUT the browser will change the second request to GET. To avoid this, remove the trailing slash silently and pass the rewritten URI to the next handler.Register it early, before
RoutingMiddleware: