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.

Sign up for GitHub

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

Jump to bottom

Support for changing the Cache-Control header sent by the GET API #56

Closed
mildbyte opened this issue Aug 17, 2022 · 0 comments · Fixed by #422
Closed

Support for changing the Cache-Control header sent by the GET API #56

mildbyte opened this issue Aug 17, 2022 · 0 comments · Fixed by #422

Comments

@mildbyte
Copy link
Contributor

mildbyte commented Aug 17, 2022 •
edited
Loading

(followup to #20)

The current default is not sending any cache-control headers at all, which means that the browser/CDNs will lean towards more caching. (from my basic testing, it seems like Cloudflare caches for 2h at least: https://developers.cloudflare.com/cache/about/edge-browser-cache-ttl/)

Possible settings:

  • how soon to revalidate with an If-None-Match (maxage?)
  • sending s-maxage as well as maxage (the former seems to influence CDNs)

Some reference: https://jakearchibald.com/2016/caching-best-practices/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Enable specifying the GET endpoint cache-control header via config splitgraph/seafowl
1 participant
@mildbyte