Images served by next do not have cache-control set

I’ve noticed that Next does not set any cache-control headers when serving images generated by this plugin. Given that many CDNs use these headers to determine whether or not to cache an image, it seems like this renders the point of the content hashes moot.

[sincraianul]

This issue can easily be fixed without overriding the built-in server and losing its benefits. In your next.config.js:

const withPlugins = require('next-compose-plugins');
const optimizedImages = require('next-optimized-images');

module.exports = withPlugins([
  [optimizedImages, {
    imagesFolder: 'chunks/images'
  }]
]);

The ‘trick’ here is that Next.js slaps a Cache-Control: public, max-age=31536000, immutable header on whatever is in the .next/static/chunks folder, which is fortunate (and appropriate). 🎉

[cyrilwanner]

Thank you very much for this workaround @sincraianul! Yes, I will make this the default folder with the next major version.