Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter poliarc

    (@poliarc)

    OK, thanks for helping narrow down the cause – though I’m not convinced its an invalidation problem because we haven’t uploaded any new attachments, nor updated any plugins, nor manually purged the CDN, and as mentioned the charges are S3 request-tier1, which is PUT, COPY, POST, and LIST requests to the S3 bucket not invalidations on CloudFront – as far as I understand it… I’m obviously not a guru on such things, things 😉

    Appreciate your time & suggestions.

    Thread Starter poliarc

    (@poliarc)

    Hi Marko –

    Correct: W3 Total Cache w/ CDN active using “Amazon CloudFront Over S3”. We are no longer using any other offload plugin. I just mentioned that as reference / comparison base for the big increase in S3 cost due to millions of Request-Tier1 requests from S3 once we did activate the CDN option in W3 total cache. Sites that get very little traffic are getting 250,000+ S3 requests per day from the W3 Total Cache plugin when nothing is being uploaded or changed on the website.

    Since that Request-Tier1 type includes LIST (as well as PUT, COPY, & POST), we thought we had narrowed it down to being a result of the “Export changed files automatically” option making thousands of LIST requests a day to compare files and/or the issue that seems to remain that max-age and expiration headers aren’t being passed when the CDN is set to “Amazon CloudFront Over S3”, but shutting that option off didn’t solve it, unfortunately. (even though LIST still “feels” like it’s the cause since we’re definitely not adding any new attachments or files yet getting the huge numbers on S3)

    It’s the same issue as the other post I referenced in the first post that was closed due to no new replies and hoping there’s been a solution / recommendation since then (other than deactivating the CDN option).

    Thanks for your time. Much appreciated.

Viewing 2 replies - 1 through 2 (of 2 total)