Images not being cached. The prop minimumCacheTTL is ignored and instead set to max-age=0.

[abdielou]

Describe the bug
The NextImage minimumCacheTTL is being ignored and replaced by max-age=0. By default it should be 60. Any overrides at next.config.js, as specified by the docs, are also ignored.

To Reproduce
Steps to reproduce the behavior:

1. Install a fresh tailwind-nextjs-starter-blog
2. Build and serve: npm i; npm run build; npm run serve;
3. Navigate to any page with images eg: /blog/guide-to-using-images-in-nextjs
4. Open the Dev Tools and inspect the image's Response Headers.
5. Validate the image's Cache-Control header.

Expected behavior
Image response headers should have a default Cache-Control with max-age=60 or as defined by minimumCacheTTL.

Instead, max-age=0 is returned, therefore disabling cache optimizations.

Screenshots
This is the Cache-Control being returned by sample images at /blog/guide-to-using-images-in-nextjs.

But it should have a default value of 60 or as defined by minimumCacheTTL.

Here's an example from a clean next js installation.

System Info (if dev / build issue):

• Deployed at Vercel

Browser Info (if display / formatting issue):

• Browser: Chrome

[daaain]

I can confirm this is still happening with a website created on 2022 December 14 at 23:12:22 GMT using @pliny/cli

[daaain]

This is still happening even after figuring out that I have to use direct image URLs rather than reference type links in Markdown (see this commit) to get them wrapped as Next Image.