Fixing regexes#163
Closed
shushpanchik wants to merge 1 commit intowesbos:masterfrom
shushpanchik:patch-06-regexe
Closed
Fixing regexes#163shushpanchik wants to merge 1 commit intowesbos:masterfrom shushpanchik:patch-06-regexe
shushpanchik wants to merge 1 commit intowesbos:masterfrom
shushpanchik:patch-06-regexe
Conversation
Owner
|
Thanks - will be keeping it the same as the videos for consistency - I do have some other videos on escaping data. I guess you could xss yourself here :) |
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
2 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.
Putting unescaped user input into regex is a bad idea #1 - for example, typing . into search field will create weird result
Replacing substring with a user input is a bad idea #2 - it's not respecting letter case