Refactor CrossOriginFilter with small perf improvements #4672
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
dennyac
force-pushed
the
refactor-cross-origin-filter
branch
from
99874e7
to
904cd38
Compare
Signed-off-by: Denny Abraham Cheriyan <[email protected]>
dennyac
force-pushed
the
refactor-cross-origin-filter
branch
from
904cd38
to
3c4ab14
Compare
|
Will look into the build issues and resolve it. |
Signed-off-by: Denny Abraham Cheriyan <[email protected]>
|
Fixed checkstyle violation |
gregw
approved these changes
Mar 16, 2020
gregw
pushed a commit
that referenced
this pull request
Mar 16, 2020
* Refactor CrossOriginFilter Signed-off-by: Denny Abraham Cheriyan <[email protected]> * Fix checkstyle violation Signed-off-by: Denny Abraham Cheriyan <[email protected]>
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.
Hi maintainers,
I've made a small change to split the list of origins into a set of origins (for exact match) and a list of patterns (for pattern match). This way for exact match we can check if the set contains the origin (instead of iterating through the list) and only iterate through the origins for pattern matching.
This change also creates patterns during the init phase, instead of creating a new Pattern object during each request
Functionality remains unchanged. Not sure if any tests need to be added, but do let me know if any specific tests are required.
Force pushed for adding signoff