This repository has been archived by the owner on Jan 8, 2024. It is now read-only.
server: Ensure trigger names are valid paths #4660
Merged
Conversation
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
Prior to this commit, a user could create a bad HTTP path with a trigger name like `../bad`. This commit fixes that behavior by validating the given trigger name matches our expected valid path tokens.
briancain
added
pr/no-changelog
briancain
removed
the
pr/no-changelog
paladin-devops
approved these changes
May 3, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Prior to this commit, a user could create a bad HTTP path with a trigger name like
../bad. This commit fixes that behavior by validating the given trigger name matches our expected valid path tokens.With this fix: