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

Proposal: use the 'immutable' setting for cache headers #751

Open
martijnvt1981 opened this issue Oct 4, 2023 · 1 comment
Open

Proposal: use the 'immutable' setting for cache headers #751

martijnvt1981 opened this issue Oct 4, 2023 · 1 comment
Milestone

Comments

@martijnvt1981
Copy link

I think it'd be wise to add a more aggressive cache header, which would be able to eliminate unnecessary lookups (200-code requests). Please take a look at this article

Long story short, if you're absolutely sure the files stay exactly the same and you don't need any extra lookups, it'd be better to use a header like this: public, max-age=31560000, immutable. The immutable property will make sure the browser doesn't reach out to the origin to see if something newer is available.

This will surely speed up loading times! Please consider adding this cache header setting to the advanced settings section of the 'Browser cache' area.

@cssjoe cssjoe added this to the 2.7.7 milestone Sep 26, 2024
@cssjoe
Copy link
Member

cssjoe commented Sep 26, 2024

We can add another cache policy selection for "CSS & JS" and "Media and Other" in the Browser Cache settings. I wouldn't recommend the setting for "HTML & XML".

@cssjoe cssjoe modified the milestones: 2.7.7, 2.8.0 Oct 17, 2024
@cssjoe cssjoe modified the milestones: 2.8.0, 2.8.1 Nov 7, 2024
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

2 participants