major version pinning is not suitable for production - cache is too long with up to 14 days of cache about jsdelivr HOT 5 OPEN

Hey, have you tried the purge API? It should work well in this case: https://github.com/jsdelivr/jsdelivr#purge-cache

from jsdelivr.

hey @MartinKolarik, purging doesn't help since jsdelivr is also setting response max time headers of 7 days. hence, the browser will cache a link for 7 days in addition to jsdelivr caching 7 days. The worst case result is a close to 14 days cache.

I updated the issue. The solution seems obvious. Reduce the caching time for version pinned modules to 12/24 hours.

from jsdelivr.

Quick note: the CDN cache time is only 12 hours already, as indicated by s-maxage. The problem in your case is indeed likely the client cache.

from jsdelivr.

Good remark. In that case, the problem seems mostly jsdelivr purging-related.

Lowering the JSDelivr cache time to 12 hours for major versions seems beneficial as we can't, and therefore jsdevlivr too, require developers to set up CI/CD to purge (too long) JS deliver caches.

Would lowering the JSDelivr cache time from 7 days to 12 hours for major/minor versions be okay for JSDelivr?

from jsdelivr.