feat: optimize parsing invalid chars #10
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
Image refs with many and long subdomains that have invalid characters in the image reference cause the regex engine to get bogged down and could become a regular expression denial of service attack. For example `docker.artifactory.us.foo.mycompany.com/bar/node?18` takes >4mins to parse and return as an invalid reference. With the updates in this change set the whole test set runs in 2ms.
|
Thanks for contributing. I haven't worked with Python for a long time, so there might be a delay in updating to PyPI. Sorry for any inconvenience. |
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.
Image refs with many and long subdomains that have invalid characters in the image reference cause the regex engine to get bogged down and could become a regular expression denial of service attack.
For example
docker.artifactory.us.foo.mycompany.com/bar/node?18takes >4mins to parse and return as an invalid reference. With the updates in this change set the whole test set runs in 2ms.