IPX ignores `s-maxage` when `max-age` is present in the HTTP source `cache-control` header

[arpadgabor]

IPX ignores `s-maxage` when `max-age` is present in the HTTP source `cache-control` header

[pi0]

Hi, dear @flapili, and thanks for explaining your issue.

It is not a breaking change but it is not something I think we could have enabled by default. s-maxage cache-control directive instructs CDN proxies how long they can keep a resource cached. IPX is not a reverse caching proxy to do so. So if reverse proxy explicitly requests max-age is zero, it should be respected and checked every time. s-max-age could be used if for example IPX caches the HTTP response (we might in the future)

For a quick solution, i have added a new option for http.ignoreCacheControl (can be configured for nuxt image v1 stable) via 4690342 this allows you to opt-out from infering cache-control header altogether and you can explicitly override maxAge.

We could also support an option like http.useSMaxAge but since it is not same semantics for directive, i consider it unsafe to be included but still open to support via another opt-in configuration if you really think would be needed in your case.

[flapili]

I have exactly the same issue ? did you get it working without a lot of hack in source code directly ? if not I'll try to make a RP

[arpadgabor]

@flapili nope, I patched ipx to fix it in the meantime. Hopefully we can get this fix in the v2 roadmap.

[flapili]

@Atinux and others maintainers does that is a big breaking change in your opinion ?