mirror of
https://github.com/terribleplan/next.js.git
synced 2024-01-19 02:48:18 +00:00
4881cd346b
When running some tests, I noticed that Akamai was still caching the response for render errors for some reason. Honestly, I would've thought that `no-store, must-revalidate` would be enough to prevent the CDN from caching it. That being said, MDN's documentation on [Cache-Control] has a section called ["Preventing Caching"] and recommends also using the `no-cache` directive. Given the definitions provided for `no-cache` and `no-store`, I can't tell much of a difference between these two. But I _do_ know that, for whatever reason, Akamai seems to respect the `no-cache` value for this header. [Cache-Control]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control ["Preventing Caching"]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control#Preventing_caching |
||
|---|---|---|
| .. | ||
| build | ||
| lib | ||
| config.js | ||
| document.js | ||
| export.js | ||
| hot-reloader.js | ||
| index.js | ||
| next.js | ||
| on-demand-entry-handler.js | ||
| render.js | ||
| require.js | ||
| router.js | ||
| utils.js | ||