fix: update path matching regex to be stricter to ensure no history leakage#839
Merged
tjholm merged 2 commits intonitrictech:mainfrom Jan 8, 2025
Merged
Conversation
HomelessDinosaur
requested review from
davemooreuws,
jyecusch,
raksiv and
tjholm
davemooreuws
requested changes
Jan 7, 2025
Co-authored-by: David Moore <4121492+davemooreuws@users.noreply.github.com>
davemooreuws
approved these changes
Jan 7, 2025
tjholm
approved these changes
Jan 8, 2025
Contributor
|
🎉 This PR is included in version 1.56.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
6 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.
Tested using the following paths:
Correctly associated each history path to belong to the correct API route. For reference: the regex looks like
^\/user\/[^/]+$for a path to match for/user/{name}.