Title: CloudFront FSD &#8211; Cache Header setting and preloading cloudfront
Last modified: July 11, 2024

---

# CloudFront FSD – Cache Header setting and preloading cloudfront

 *  Resolved [jamesdev](https://wordpress.org/support/users/jamesdev/)
 * (@jamesdev)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/cloudfront-fsd-cache-header-setting-and-preloading-cloudfront/)
 * What’s the correct way to disable the cache-control header to Cloudfront caches
   in all cases? If I run “curl -I [http://example.com&#8221](http://example.com&#8221);
   I always get “X-Cache: Miss from cloudfront” and “Cache-Control: no-store, no-
   cache, must-revalidate”. I’ve tried with Browser Cache settings “Set expires 
   header” on and off. I’ll get a cache hit from the browser but not from terminal.
   From the browser. the cloudfront cache also seems to expire quite quickly (10-
   20 minutes despite a 3600 expire time).
 * Also, is there a way to preload cloudfront cache? I tried using the page cache
   cron but this didn’t seem to have an effect.
 * Thanks

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

 *  Plugin Contributor [Marko Vasiljevic](https://wordpress.org/support/users/vmarko/)
 * (@vmarko)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/cloudfront-fsd-cache-header-setting-and-preloading-cloudfront/#post-17885895)
 * Hello [@jamesdev](https://wordpress.org/support/users/jamesdev/)
 * Thank you for reaching out and I am happy to help!
   I am not quite sure I understand
   the questions and what you are trying to achieve. W3 Total Cache sets the Cache
   control header in the Browser Cache settings, and once set, the headers and the
   caching is in effect. If those are disabled, and you can still see some headers,
   it meanst those are not coming from the W3 Total Cache, so either server configuration
   or some custom rules are applied in this case.Meaning, you should check the AWS
   configuration and your server configuration for any cache control rules (apache
   or nginx depends on what you are using)
 * You can only preload the W3 Total Cache created cache. When using FSD the cached
   files are served (html pages) which need to be fetched from the server.
   Thanks!
 *  Thread Starter [jamesdev](https://wordpress.org/support/users/jamesdev/)
 * (@jamesdev)
 * [1 year, 10 months ago](https://wordpress.org/support/topic/cloudfront-fsd-cache-header-setting-and-preloading-cloudfront/#post-17895826)
 * Thanks for the assist. After some testing, it looks like it’s an advert plugin
   that uses PHP sessions which adds the Cache-Control:
 *     ```wp-block-code
       Cache-Control: no-store, no-cache, must-revalidatePragma: no-cacheExpires: Thu, 19 Nov 1981 08:52:00 GMT
       ```
   
 * I’m investigating now if there’s anyway to adjust PHP settings so that it doesn’t
   break the CF caching
    -  This reply was modified 1 year, 10 months ago by [jamesdev](https://wordpress.org/support/users/jamesdev/).

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

The topic ‘CloudFront FSD – Cache Header setting and preloading cloudfront’ is closed
to new replies.

 * ![](https://ps.w.org/w3-total-cache/assets/icon-256x256.png?rev=1041806)
 * [W3 Total Cache](https://wordpress.org/plugins/w3-total-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/w3-total-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/w3-total-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/w3-total-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/w3-total-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/w3-total-cache/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [jamesdev](https://wordpress.org/support/users/jamesdev/)
 * Last activity: [1 year, 10 months ago](https://wordpress.org/support/topic/cloudfront-fsd-cache-header-setting-and-preloading-cloudfront/#post-17895826)
 * Status: resolved