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

Better caching directives #160

Open
flakey5 opened this issue Nov 1, 2024 · 1 comment
Open

Better caching directives #160

flakey5 opened this issue Nov 1, 2024 · 1 comment

Comments

@flakey5
Copy link
Member

flakey5 commented Nov 1, 2024

We're serving mostly static and immutable content, but only caching it for 1 or 4 hours (depends on cache type) for successful responses.

I think we should change this so that content that doesn't change (i.e. release assets) are cached for a lot longer than assets that do change (i.e. some directories, index.json).

Specifically, I think they should be something like these:

  • for immutable content (release assets, metrics, ...), public, immutable, max-age=31536000, s-maxage=31536000
  • for the things that do change (index.json, directory listings, ...), public, max-age=86400, s-maxage=86400, must-revalidate
@flakey5
Copy link
Member Author

flakey5 commented Nov 17, 2024

cc @ovflowd

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

1 participant