Ugh, that’s no good. Sounds like you haven’t found a good alternative, which was going to be my next question :).
I started to think of other alternatives. We use nginx in front so caching isn’t an issue, but if we ever want to horizontally scale the server farm then there’s going to need to be some sort of asset replication. This is obviously off topic :), but part of the big picture.
I’m starting to think something like https://www.gluster.org/ would be worth looking at to help with asset (images, themes, etc) replication.
Have you thought of anything different outside the box?
Bump.
I’ve decided to go ahead and manually update the assets in s3 to have a Cache Control header, which fixes the issue. But I believe W3 total cache should be doing this.
I’ve verified that media assets, etc, which I would like to stay cached in the browser are setup.
– Set cache control header, cache with max-age(“public, max-age=EXPIRES_SECONDS”) (checked)
– Set entity tag ( ETag ) checked
