Added caching of x509 public keys and toolkit public keys#8
Open
clibequilibrium wants to merge 3 commits intoMarplex:mainfrom
Open
Added caching of x509 public keys and toolkit public keys#8clibequilibrium wants to merge 3 commits intoMarplex:mainfrom
clibequilibrium wants to merge 3 commits intoMarplex:mainfrom
Conversation
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.
This PR introduces necessary caching mechanism for Cloudflare network. x509 public keys are now cached using max-age returned from the initial request. And toolkit public keys are cached using Cache API.
Please note, without such caching eventually Google starts to throttle those fetches and in some cases would result in Auth taking more than 20 seconds. I am having some conversations with Firebase staff about it but it seems that Google just doesn't like CF network frequently fetching the keys.