Clear eCDN Cache

B2C Commerce stores static storefront content in eCDN cache or the web tier static content cache.

All content cached by eCDN is served using a unique URL. Cache purging a CDN on top of URLs from B2C Commerce isn’t necessary, because the system updates the URL when uploading new content. Aside from replicating environments to clear the cache of any static content, no action is required.

When working with eCDN cache, keep the following in mind:

To clear eCDN cache:

  1. Upload the updated asset to your storefront POD.
    When an asset is updated on the POD, the system generates a new fingerprint value for that asset. Changing the fingerprint also changes the URL of the updated asset. When your storefront requests the updated static asset, the URL request returns a miss in eCDN and web tier cache. This response occurs because the fingerprint is different, and the CDN doesn’t recognize the new and old asset as the same. The missed request with the new fingerprint is then directed to the POD, the asset is then retrieved and cached with the new URL.
    Note: All content assets in cache are refreshed, excluding the old content updated in this process. The update content is assigned a new fingerprint that results in a new URL for the asset.
  2. Refresh your site in the browser and confirm that the updated asset appears as expected.

If the updated asset doesn’t appear in your browser after updating content, you can manually invalidate the Application Tier cache. Though it’s rare, the asset not appearing means that something went wrong with the cache clearing process.

  1. Clear the cache:
    • To clear the Business Manager Site cache, navigate to Administration > Sites > Manage Sites > Business Manager Site > Cache, and click Invalidate where applicable.
    • To invalidate the cache for a specific site, navigate to Administration > Sites > Manage Sites > Site Name > Cache and click Invalidate where applicable.
  2. Refresh the site in your browser, and confirm that the updated asset appears as expected.
X Privacy Update: We use cookies to make interactions with our websites and services easy and meaningful, to better understand how they are used. By continuing to use this site you are giving us your consent to do this. Privacy Policy.