Skip to content
This repository has been archived by the owner on Apr 3, 2019. It is now read-only.

Allow caching of /.well-known/browserid #597

Closed
rfk opened this issue Feb 28, 2014 · 4 comments
Closed

Allow caching of /.well-known/browserid #597

rfk opened this issue Feb 28, 2014 · 4 comments

Comments

@rfk
Copy link
Contributor

rfk commented Feb 28, 2014

Because otherwise the verifier will have to fetch it for every validation; we want to add some verifier-side caching per https://bugzilla.mozilla.org/show_bug.cgi?id=977922

We currently serve it with header Cache-Control: no-cache. A good place to start might be copying persona.org, which services its support document with Cache-Control: public, max-age=10.

@gene1wood
Copy link
Member

I've confirmed that the cache-control is being set by node, not nginx so this change will need to happen in the app

@mostlygeek
Copy link

@dannycoates is "10000" an arbitrary value or does it have some sort of significance?

@dannycoates
Copy link
Contributor

max-age=10 is what persona.org uses, arbitrary but changeable.

@mostlygeek
Copy link

Oh, that's in milliseconds. OK yah even living in the cache for 10 seconds would drop our traffic usage down by a lot!

rfk pushed a commit that referenced this issue Oct 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants