Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creative signature validation keys are now cached in JavaScript. #5922

Merged
merged 4 commits into from Oct 31, 2016
Merged

Creative signature validation keys are now cached in JavaScript. #5922

merged 4 commits into from Oct 31, 2016

Conversation

glevitzky
Copy link
Contributor

Keys are now cached in a global variable so that multiple requests are not sent out for the same set of keys.

…for caching in JS the validation keys, and also for re-fetching the keys if the first attempt at verification fails.
@lannka lannka self-assigned this Oct 31, 2016
@lannka lannka merged commit 174ec5f into ampproject:master Oct 31, 2016
@glevitzky glevitzky deleted the dev-key-cache branch October 31, 2016 22:44
Lith pushed a commit to Lith/amphtml that referenced this pull request Dec 22, 2016
…project#5922)

* Factored out signature verification into its own method. Added logic for caching in JS the validation keys, and also for re-fetching the keys if the first attempt at verification fails.

* Fixed types.

* Accidentally reverted to lifecycleReporter when merging.
Lith pushed a commit to Lith/amphtml that referenced this pull request Dec 22, 2016
…project#5922)

* Factored out signature verification into its own method. Added logic for caching in JS the validation keys, and also for re-fetching the keys if the first attempt at verification fails.

* Fixed types.

* Accidentally reverted to lifecycleReporter when merging.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants