---
schema_version: "1"
id: 38202a2263b423e6db69355d907e3a53787fbfc40f391d3bf3545b0044647d75
title: eCDN Caching and Cache Fingerprinting
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/cc/264-0-0/b2c_ecdn_caching_and_fingerprinting.md
canonical_url: https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_caching_and_fingerprinting.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 9f64db188b8cff1afe767e76006b4fb60cfc9b49ff363d45b59ce19c61794e5f
description: B2C Commerce eCDN caches static storefront content on edge servers, which are servers located close to your shoppers, and refreshes it automatically using a fingerprint value in each content asset's URL. Understand how caching and fingerprinting work before you clear the cache or add cache rules for dynamic content.
products:
  - Commerce
  - B2C Commerce
release: "264"
---
# eCDN Caching and Cache Fingerprinting

B2C Commerce eCDN caches static storefront content on edge servers, which are servers located close to your shoppers, and refreshes it automatically using a fingerprint value in each content asset's URL. Understand how caching and fingerprinting work before you clear the cache or add cache rules for dynamic content.

[Which Salesforce Commerce Product Do I Have?](https://help.salesforce.com/s/articleView?id=commerce.comm_what_product.htm&language=en_US)

Because every cached asset has its own unique URL, and B2C Commerce generates a new URL whenever you upload new content, you don't need to manually purge the CDN cache. The one exception is environment replication, which clears the cache of static content as part of the process.

- **Static content** is cached by default and refreshed automatically through fingerprinting. To force an update before the cache interval expires, see [Refresh a Static Asset in the eCDN Cache](https://help.salesforce.com/s/articleView?id=cc.b2c_clear_ecdn_cache_task.htm&release=264.0.0&type=5 "To show an updated static storefront asset before its B2C Commerce eCDN cache interval expires, upload the new version. B2C Commerce assigns the asset a new fingerprint and URL, so eCDN retrieves it. You don't need to clear the eCDN cache or file a support ticket.").
- **Dynamic content** (HTML pages and JSON responses) isn't cached by default. To make dynamic content eligible for edge caching, and to selectively invalidate the content by tag or path from Business Manager, see [eCDN Cache Rules and Cache Purge](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_cache_rules_and_purge_overview.htm&release=264.0.0&type=5 "Cache rules control which content is eligible for caching at the eCDN edge, and cache purge selectively invalidates cached content by tag or path. Both capabilities are available in Business Manager for your B2C Commerce storefront.").

## How Static Caching and Fingerprinting Work for B2C Commerce eCDN

- eCDN uses the `Cache-Control` header to determine how long a file stays in cache. After the time to live (TTL) expires, eCDN retrieves the updated resource. If no cache headers are set, eCDN applies a default TTL of 30 days.
- The web adapter builds pages using static assets from both eCDN and web tier cache sources. Regardless of where an asset is cached, B2C Commerce assigns every static content asset a unique fingerprint value. For example, consider this URL:
    
    `https://www.samplecustomer.com/dis/dw/image/v2/XXXX_PRD/on/demandware.static/-/Sites-customer-main-product/default/dwabb3a337/images/hi-res/shoes.jpg?sw=200&sh=200&sm=fit&sfrm=png`
    
    The value `dwabb3a337` is the asset's fingerprint, a unique identifier for that specific version of the asset.
- Although cache updates happen on the interval you set, you can still update an asset held in static cache before that interval expires, without clearing the cache or filing a support ticket. See [Refresh a Static Asset in the eCDN Cache](https://help.salesforce.com/s/articleView?id=cc.b2c_clear_ecdn_cache_task.htm&release=264.0.0&type=5 "To show an updated static storefront asset before its B2C Commerce eCDN cache interval expires, upload the new version. B2C Commerce assigns the asset a new fingerprint and URL, so eCDN retrieves it. You don't need to clear the eCDN cache or file a support ticket.").

- **[Refresh a Static Asset in the eCDN Cache](https://help.salesforce.com/s/articleView?id=cc.b2c_clear_ecdn_cache_task.htm&release=264.0.0&type=5)**  
    To show an updated static storefront asset before its B2C Commerce eCDN cache interval expires, upload the new version. B2C Commerce assigns the asset a new fingerprint and URL, so eCDN retrieves it. You don't need to clear the eCDN cache or file a support ticket.
- **[eCDN Cache Rules and Cache Purge](https://help.salesforce.com/s/articleView?id=cc.b2c_ecdn_cache_rules_and_purge_overview.htm&release=264.0.0&type=5)**  
    Cache rules control which content is eligible for caching at the eCDN edge, and cache purge selectively invalidates cached content by tag or path. Both capabilities are available in Business Manager for your B2C Commerce storefront.

#### See Also

- [Caching Strategies for Salesforce B2C Commerce](https://developer.salesforce.com/docs/commerce/commerce-solutions/guide/caching-strategies-sk.html)