Pldt 333 casino.Claim Your Free 999 Pesos Bonus Today

Resolved Rafal Lukawiecki
(@rafal-lukawiecki)

13 years, 10 months ago

Thanks for creating this plug-in, W3 Total Cache is a great addition to WordPress.

My query concerns my web site, https://rafal.net

I use CloudFront CDN, and I have added paths for a number of image files in “Custom File List”. I can see that they have all been uploaded to S3, and I have verified them from the CDN CNAME. Most of them are being served with the “cdn.rafal.net” host name, but no matter what I do, I am stuck with these five, which always seem to refer to the non-CDN site (look at the home page):

https://rafal.net/wp-content/plugins/qtranslate/flags/gb.png
https://rafal.net/wp-content/plugins/qtranslate/flags/pl.png
https://rafal.net/wp-content/plugins/share-and-follow/default/16/rss.png
https://rafal.net/wp-content/plugins/share-and-follow/default/16/twitter.png
https://rafal.net/wp-content/plugins/share-and-follow/default/16/sprite-16.png

Interestingly, one that belongs to the share-and-follow plug-in, does come from the CDN, so this issue is not completely dependent on the use of the qTranslate and Share-and-Follow plug-ins (https://cdn.rafal.net/wp-content/plugins/share-and-follow/images/blank.png).

I would be grateful for any suggestions.

PS. I have enabled/disabled W3TC several times, I have deleted and recreated the distribution and the bucket, I have used the “Force Overwriting” option, and I have emptied the “Upload Queue” errors a number of times. Each time, I have emptied the caches.

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

Thread Starter Rafal Lukawiecki
(@rafal-lukawiecki)

13 years, 10 months ago

For what it is worth, after a while, nothing is served from the CDN. The “Upload queue” fills with “Object already exists” errors, and the CDN entirely stops serving any purpose. Deleting the queue resolves this issue (but not the 5 images I mentioned above), but this seems only temporary.

Is there a solution to this problem? I have seen suggestions that W3 Total Cache is not designed to work well with Amazon Cloudfront because, apparently, it uses origin push. I have also seen suggestions to use a different CDN provider, but I did not see any explanation as to why this may be the case, or how to resolve it.

Many thanks to the community.

Thread Starter Rafal Lukawiecki
(@rafal-lukawiecki)

13 years, 10 months ago

I can see that this problem has been reported so many times, that it must be a known issue of W3 Total Cache. Unfortunately, I did not see it listed anywhere as a Frequently Asked Question, so I am not sure if this issue is being resolved for the upcoming version.

I wish Frederick luck resolving this bug, as it would be nice if W3 Total Cache worked with Amazon Cloudfront.

Thread Starter Rafal Lukawiecki
(@rafal-lukawiecki)

13 years, 10 months ago

I decided that since nobody can help me resolve this issue I will hardcode references to the CDN in my template for the files which are not being correctly picked up by W3 Total Cache.

Thanks, and sorry for that.

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

The topic ‘W3 Total Cache Not Serving Some Images from CDN’ is closed to new replies.