b123942694
In a previous PR (#27200), we added `minimumCacheTTL` to configure the time-to-live for the cached image. However, this was setting the `max-age` header. This PR ensures that `minimumCacheTTL` doesn't affect browser caching, only the upstream header can affect browser caching. This is a bit safer in case the developer accidentally caches something that shouldn't be and the cache needs to be invalidated. Simply delete the `.next/cache/images` directory. - Related to #19914 - Related to #22319 |
||
---|---|---|
.. | ||
advanced-features | ||
api-reference | ||
api-routes | ||
basic-features | ||
migrating | ||
routing | ||
authentication.md | ||
deployment.md | ||
faq.md | ||
getting-started.md | ||
going-to-production.md | ||
manifest.json | ||
upgrading.md |