w3 Total Cache and Amazon Cloudfront

  • Resolved aparnawd

    (@aparnawd)


    3 years, 6 months ago

    Hi,

    The domain of our wordpress website is pointed to Cloudfront. Hence all the pages except Admin Dashboard are loaded from Cloudfront.

    We are planning to use w3 Total Cache’s Amazon Cloudfront Setting’s. I basically want to know what all changes will be there after setting this up. And also in which all scenarios invalidations will occur?

    Will there be invalidations for Custom Post page urls when we update any content related to that custom post type?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @aparnawd

    Thank you for your inquiry and I am happy to help!
    Just to confirm, you pointed your domain to Cloudfron which means that the website will be delivered from the CF. Are you trying to set up FSD CDN in W3 Total Cache?
    Thanks!

    Thread Starter aparnawd

    (@aparnawd)

    Hi,

    Thanks for your reply. Yeah I want to know how invalidations happen in FSD CDN. Also this feature is available in the Non Pro version right?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @aparnawd

    When you point yoru domain to Cloudfront, it means that your entire website will be served from the CF. Cloudflare doesn’t charge for “request”, but for invalidation path, and since your entire website is served from the CF there should be no invalidations.
    The FSD CDN option in W3 Total Cache is a Pro feature, so you need to upgrade to Pro to be able to use it.
    Thanks!

    Thread Starter aparnawd

    (@aparnawd)

    Hi Marko,

    If I go for Pro option and use the FSD CDN, will there be any validation for dynamic content pages?

    There is a custom post type top page url that needs to be invalidated whenever the content of that post gets updated. Is that possible?

    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @aparnawd

    This should happen automatically, and yes W3TC does send the invalidations.
    If you want all posts of a custom post type to be purged when one post is edited, then there may not be an option for that and you would have to purge by URL or all.
    You should also add custom posts type in Peroformance>Page Cache>Purge Policy>Additional pages:
    The list should use URI paths, for example: /category/page

    If you dont want this to be done manually, you can always enable the option: “Only purge CDN manually” in Performance>CDN.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘w3 Total Cache and Amazon Cloudfront’ is closed to new replies.