https://bugs.winehq.org/show_bug.cgi?id=40346
--- Comment #8 from Jeremy Newman jnewman@codeweavers.com --- (In reply to Michael Müller from comment #6)
I would suggest to revert the change until we have a proper solution though, otherwise we can basically skip building every second release. The whole caching doesn't seem to work as expected anyway. Otherwise we would still be able to download the removed packages, they were uploaded less than a month ago. Are you sure that the caching works for such big files?
We are not going to revert to the global default 1 hour TTL if that is what you are asking. Our hosting bill jumped dramatically since we started hosting all the wine and wine-staging files. We are taking these steps to reduce that.
The CDN does not have a maximum file size on cached files that I can see. They simply honor the "Expires" header we pass on the request to the origin.