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

improve and extend hpke-config endpoint cache-control headers #1926

Open
jbr opened this issue Sep 15, 2023 · 3 comments
Open

improve and extend hpke-config endpoint cache-control headers #1926

jbr opened this issue Sep 15, 2023 · 3 comments

Comments

@jbr
Copy link
Contributor

jbr commented Sep 15, 2023

This may involve sending last-modified-at, an etag (trillium-caching-headers can handle this), a longer max-age, and/or a stale-while-revalidate.

pairs well with divviup/divviup-ts#410

@divergentdave
Copy link
Contributor

Note that last-modified-at would require a new database column at the task level. We would also have to update this timestamp when deleting (or demoting/making invisible) a public key.

@jbr
Copy link
Contributor Author

jbr commented Oct 19, 2023

Likely relevant to #2147

@branlwyd
Copy link
Member

I support an ETag; I don't think we should prioritize last-modified-at or any other header that requires us to track additional data in our datastore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants