docs: handle trailing slash behaviour for all URLs#6254
Merged
matthewelwell merged 1 commit intomainfrom Nov 7, 2025
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
matthewelwell
requested review from
robertnorrie
and removed request for
a team
robertnorrie
approved these changes
Nov 7, 2025
emyller
approved these changes
Nov 7, 2025
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
3 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.
Changes
The PR here #6252 removed a load of 'duplicates', but actually they were working around the fact that the default configuration in vercel doesn't handle trailing slash re-routing. This PR means that any URL with a trailing slash will be re-routed to the naked URI (i.e. strip the trailing slash).
How did you test this code?
Tested via preview:
/clients/and/clients,/clients/ios/and/clients/ios) to confirm that the redirects work as expected now