Priming the cache worldwide

Follow

Nikhilesh Jasuja

• June 01, 2020 06:00
• Edited

When content changes, we use the Fastly API to purge the cache for that piece of content using cache tags/keys. This is useful. Is there a way to then immediately prime the cache in all POPs with the updated content?

 

0

• 

  Shohei Maeda

  • June 01, 2020 06:16

  Hi Nikhilesh Jasuja,

  Unfortunately, there isn't a way to do that but our shielding feature can dramatically improve your cache hit ration if you haven't considered it yet.

  See also:

  https://support.fastly.com/hc/en-us/community/posts/360040169071-Fastly-and-Cache-Warming

  0

  Comment actions Permalink
• 

  Nikhilesh Jasuja

  • June 04, 2020 08:20
  • Edited

  Thanks Shohei.

  This is actually very helpful. Here's my new config:

  1. The application (origin) sets Surrogate-Control: max-age=2592000, stale-while-revalidate=604800, stale-if-error=604800
  2. The origin also sets Surrogate-Key: key1 key2 key3
  3. When the page needs to be purged, the app makes a curl request: curl --silent -X POST -H 'Fastly-Soft-Purge:1' -H 'Fastly-Key:MY_KEY' https://api.fastly.com/service/ServiceID/purge/key1

  However, this does not do the job. After the soft purge when I request the content, Fastly is not serving me stale content. It is making a request to the origin to get fresh content to serve.

  If you'd like to try a URL to test it, you can use https://www.diffen.com/difference/Abiotic_vs_Biotic

  0

  Comment actions Permalink

Please sign in to leave a comment.