ec4df71352
In a previous PR (#34075), the ISR behavior was introduced to the Image Optimization API, however it changed the cache-control header to always set maxage=0. While this is probably the right behavior (the client shouldn't cache the image), it introduced a regression for users who have CDNs in front of a single Next.js instance (as opposed to [multiple Next.js instances](https://nextjs.org/docs/basic-features/data-fetching/incremental-static-regeneration#self-hosting-isr)). Furthermore, the pros of client-side caching outweight the cons because its easy to change the image url (add querystring param for example) to invalidate the cache. This PR reverts the cache-control behavior until we can come up with a better long-term solution. - Fixes #35987 - Related to #19914 - Related to #22319 - Closes #35596 |
||
|---|---|---|
| .. | ||
| advanced-features | ||
| api-reference | ||
| api-routes | ||
| basic-features | ||
| guides | ||
| migrating | ||
| routing | ||
| authentication.md | ||
| deployment.md | ||
| faq.md | ||
| getting-started.md | ||
| going-to-production.md | ||
| manifest.json | ||
| testing.md | ||
| upgrading.md | ||