Update regex pattern documentation for denied paths in README#42
Open
mybuddyandrew wants to merge 1 commit into
Open
Update regex pattern documentation for denied paths in README#42mybuddyandrew wants to merge 1 commit into
mybuddyandrew wants to merge 1 commit into
Conversation
Member
|
Thanks for the PR @mybuddyandrew. Three examples feels about right, but perhaps we can capture some more variety? I'm thinking examples where there's an ID in the middle of a path, or perhaps all paths ending in "/new". |
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.
Improve Documentation for Regex Patterns in 'Mission Control - Web'
This pull request updates the documentation related to regex patterns used for blocking specific routes in 'Mission Control - Web'. The enhancements include:
/admin/.*), specific controller actions (e.g.,/users/edit), and API routes under a specific version (e.g.,/api/v1/.*). These examples provide clear guidance on how to effectively configure the middleware to deny access to unwanted paths.#41 (comment)