-
Notifications
You must be signed in to change notification settings - Fork 56
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
fix(fs-router) check for routes with / first, then without #2258
Merged
cromoteca
merged 8 commits into
main
from
fix/2244/file-router-the-view-for-the-root-path-is-never-found-in-Java-view-registry
Mar 27, 2024
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
39c79d7
Check for routes with / first, then without
cromoteca 766a204
Merge branch 'main' into fix/2244/file-router-the-view-for-the-root-p…
cromoteca c17a4b0
Merge branch 'main' into fix/2244/file-router-the-view-for-the-root-p…
cromoteca 341848b
Use `endsWith`
cromoteca b049890
Merge branch 'main' into fix/2244/file-router-the-view-for-the-root-p…
cromoteca 63f55d9
Further simplify checks
cromoteca bb170c8
Merge branch 'main' into fix/2244/file-router-the-view-for-the-root-p…
taefi 230bdd0
Merge branch 'main' into fix/2244/file-router-the-view-for-the-root-p…
taefi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just bypassing here: Did you consider security here? I remember some CVEs in the recent past which originated from security confusion based on trailing slash..
Additionally there is this recent Spring Framework Change to keep in mind: spring-projects/spring-framework#28552
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code doesn't actually change which content is rendered. Its purpose is to try to give the same view permission response that you would get on the client where the navigation is handled by the React Routed.
By doing some manual testing, I've seen that when two routes are present which are only different on the trailing slash, React Router always renders the one with the slash (e.g. you cannot see
/about
if/about/
exists). But it is also forgiving:/about/
will show the view associated to/about
if an exact match is not there.We don't have this information here, since the new File Router only stores the path items (e.g.
["about"]
). Also, the root path is stored as""
, but it must match"/"
.This PR modifies the code that tries to find the route that React Router would render given a path. In that sense, it should not open any additional security breach.