perf(oauth2) remove needless use of regex for artificial endpoints #2806
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
We can use a more performant JITable string find to search for the exposed endpoints, based on the given logic. Doing so avoids the PCRE overhead and saves expression cache space in the VM.
thibaultcha
approved these changes
Aug 14, 2017
thibaultcha
added
the
pr/ready (but hold merge)
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.
Summary
We can use a more performant JITable string find to search for the exposed endpoints, based on the given logic. Doing so avoids the PCRE overhead and saves expression cache space in the VM.
Full changelog
string_findinstead ofngx.re.findfor artificial endpoint search