improve and extend hpke-config endpoint cache-control headers

divviup / janus

Experimental implementation of the Distributed Aggregation Protocol (DAP) specification.

Mozilla Public License 2.0

54 stars 15 forks source link

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

Open jbr opened 1 year ago

jbr commented 1 year ago

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 https://github.com/divviup/divviup-ts/issues/410

divergentdave commented 1 year ago

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 commented 1 year ago

Likely relevant to #2147

branlwyd commented 2 months ago

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.