Revalidate CDN Cache

CDN cache revalidation allows you to refresh cached content in your environment after modifying content or configuration. An environment may include multiple domains that share the same CDN settings. When you revalidate the cache, the CDN checks whether any content has changed since it was last cached. If updates are detected, the CDN fetches the latest content from the origin server and updates its cache. Otherwise, it continues serving the existing cached version. This ensures visitors always see the most up-to-date content.

Note: Each time you redeploy your environment, Launch automatically purges the CDN cache. This ensures that users always receive the most up-to-date content.

1. Contentstack account
2. Access to Launch for your organization

To revalidate the CDN cache for a website using URL path, you must provide the following:

1. Revalidation path

   The revalidation path is the URL path that you can revalidate across all the domains in your environment. For example, if you have an environment that consists of https://example.com, https://example.net, and https://example.org, and your revalidation path is /blog, then the CDN revalidates https://example.com/blog, https://example.net/blog, and https://example.org/blog.
   

2. Is Prefix

   The boolean value Is Prefix indicates whether you can revalidate only the exact path or also all the nested paths under it. For example, if your revalidation path is /blog and you set Is Prefix to true, then the CDN revalidates https://example.com/blog, and also all the pages under it, such as https://example.com/blog/post1, https://example.com/blog/post2, etc. If you set Is Prefix to false, then the CDN revalidates only https://example.com/blog. Similarly, CDN cache will also be revalidated for all other domains that are a part of the same environment.

Cache-Tags allow you to associate one or more tags with cached resources. These tags are included in the response headers, separated by commas.

Example:

Cache-Tag: product-123, product-456

Instead of purging dozens or hundreds of individual URLs when a resource changes, you can purge all content sharing the same tag with a single API call.

Launch treats duplicate Cache-Tags in a single purge request as a single operation. Duplicate tags are not reprocessed.

Hostnames allow you to selectively purge cached resources for specific domains.

If your site is configured with multiple domains, such as domain1.com, domain2.com, and domain3.com, but a change should only affect domain1.com and domain2.com, you can purge only those domains without affecting the rest.

Tip: For more targeted and flexible cache purging, purge cache using Cache-Tags or Hostnames.

Note: You can pass only one of the inputs.

To revalidate the CDN cache for an environment, you can use the Revalidate CDN Cache action in the Automate Launch connector.

Additional Resource: For detailed information on creating the Revalidate CDN Cache action in Automate, refer to the Launch Connector document.

• Revalidating a single page: To revalidate a single page on your website, for example, https://www.example.com/blog/my-blog-post, you can provide the path /blog/my-blog-post and set Is Prefix value to false.
• Revalidating an entire directory: To revalidate an entire directory of pages, you can provide the directory path and set Is Prefix value to true. For example, if you have a directory of blog posts at https://www.example.com/blog, you can provide the path as /blog and set Is Prefix to true.
• Revalidating nested paths of a category: If your website has nested paths (i.e., paths that contain other paths), you can use this feature to revalidate both the parent and child paths. For example, to revalidate the parent page https://www.example.com/category/my-category and the child page https://www.example.com/category/my-category/products, you can provide the path /category/my-category and set Is Prefix to true.
• Revalidating the entire site: To revalidate the cache of an entire website without doing a fresh deployment, you can provide the revalidation path as “/“ with Is Prefix set to true.

1. Set Cache-Tag header in your app (for example, Next.js):
   import { NextResponse } from 'next/server';
   export async function GET() {
     const data = await fetchBlogPost();
     const response = NextResponse.json(data);
     // Set Cache-Tag header
     response.headers.set("Cache-Tag", "blog-post-123");
     return response;
   }

2. Trigger purge by Cache-Tags using the revalidateCDNCache API via Automate:
   {
     "cacheTags": ["blog-post-123"]
   }

1. Trigger purge by hostnames using the revalidateCDNCache API via Automate:
   {
     "hostnames": ["domain1.com", "domain2.com"]
   }