Area: Episerver DXC Service
Applies to versions: Not applicable

CDN recommendations

This topic describes how CDN is used within the Episerver Digital Experience Cloud services, and provides general recommendations for how to configure caching specifically for CDN environments.

In this topic

How it works

The purpose of a content delivery network or content distribution network (CDN) is to ensure high availability when serving content to visitors. A CDN consists of a globally distributed network of proxy servers deployed in multiple data centers. CDNs deliver content from the fastest and closest server available. 

The CDN has its own URL pointing to the original URL. The visitor navigates to something like www.customer.com. The request goes to the CDN, which in turn goes to the origin URL for non-cached data. The request returns to the CDN, which caches the content. 

By reducing the number of server requests to geographically dispersed locations, more requests can be managed and provided from edge servers closest to the visitor location, resulting in a faster browsing experience. The cache hit ratio describes the percentage of requests the CDN could answer from its own cache.

The CDN stores a copy of your objects and, upon request, objects are served from these caches. The CDN servers are designed to cache content according to the cache rules you define in the HTTP cache headers for your web application. It is critical that these caching rules are correctly set for your solution to scale properly.

CDNs and web applications

Setting up a CDN is fairly easy and, even with minor configuration work, you can get better performance. You should develop your application with the CDN in mind from the start, and add proper cache headers based on what you want to achieve. This way, when you hook up the CDN, it will work automatically.

You should control the cache settings in the web application rather than writing overriding rules in the CDN, because this can quickly get quite complex. However, there may be situations where rules are needed, such as when special configurations are required, or if you do not want to do a deployment with these changes.

General recommendations

Evaluate whether frequently-requested objects can be cached. Static objects can be stored indefinitely in the caches. For cloud-based solutions, you should ensure that resources like static and resized images, Javascript and CSS files, and scripts are cached by the intermediary proxies, such as those provided by a CDN.

In most cases, you can include a version identifier in the path to the resources. If an object changes, the version identifier updates the URL to it, and the change is immediately reflected. The best way to control the cache for assets is to use unique file names for every deployment. Example: site-1.0.css in the first deploy, and site-1.1.css in the second deploy. This ensures that the CDN uses the latest CSS file right after deployment.

If you cannot use version identifiers for frequently-requested objects, you can set a maximum lifespan for an object. This is one of the values that are typically set in the cache-control described below. Priority should be version identifier plus indefinite caching first, and no version identifier plus maximum lifespan second

Configuring cache headers

Using the correct cache headers in your application ensures that you get the most out of the CDN service, regardless of whether you want to just cache static content, or text/HTML. You can use Last-Modified, cache-control settings, ETags, or a combination of these, to determine whether content has changed.


There are many HTTP header settings, but cache-control is one of the most important ones because this setting defines the time for which a cached object should remain cached. 

A CDN monitors the cache headers in the response settings:

  • If the response has the setting cache-control: no-cache, then the CDN will not cache the content.
  • If the response has the setting cache-control: public, then the CDN caches the content.

    Note: Cache-control must be set to public  (not private, which means that only the browser is allowed to cache the content).

Typical values:

  • max-age=$seconds. Determines the lifespan for an object.
  • must-revalidate. Tells the cache to strictly follow maximum lifespan information.
  • public. Allowed to be cached by intermediaries.
  • private. Can be cached, but only by the browser.

Note: You should not set cache to public on page requests if the page has private information, such as a cart page in e-commerce.

Example: Caching an object for a maximum of 20 minutes.

Cache-Control: public, max-age=1200, must-revalidate

Caching of static content

Use as long max-age as possible, at least for static content, to minimize the trips to the web server. In web.config, there are specific sections for setting cache headers for static content. You can see an example of settings when you install an Episerver site through Visual Studio.

The tag <staticContent> and the subtag <clientCache> set cache headers in the HTTP response. In the following example, static files are cached for one day. The <staticContent> section controls caching for the files that are part of the web application code and cannot be changed by editors.

The <caching> tag and its subsettings controls the IIS cache is cached in the web server by IIS. This will not interfere with the cache headers in the HTTP response, so removing the <caching> tag will not make a difference to the cache in the CDN.

Example: Configuring cache headers for static content.

         <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="1.00:00:00" />
            <add extension=".gif" policy="DontCache" kernelCachePolicy="CacheUntilChange"/>
            <add extension=".png" policy="DontCache" kernelCachePolicy="CacheUntilChange"/>
            <add extension=".js" policy="DontCache" kernelCachePolicy="CacheUntilChange"/>
            <add extension=".css" policy="DontCache" kernelCachePolicy="CacheUntilChange"/>
            <add extension=".jpg" policy="DontCache" kernelCachePolicy="CacheUntilChange"/>
            <add extension=".jpeg" policy="DontCache" kernelCachePolicy="CacheUntilChange"/>

Overriding SetCachePolicy

If you use SetMaxAge, this sets cache-control to public. The following example sets the max-age using a TimeSpan of one hour that is converted automatically to 3600 seconds.

public class StartPageController : PageControllerBase
    public ActionResult Index(StartPage currentPage)

        return View(currentPage);

If you use SetExpires, this sets cache-control to public, and Expires to your selected date and time.

public class StartPageController : PageControllerBase
    public ActionResult Index(StartPage currentPage)

        return View(currentPage);

Using ETags

The ETag or entity tag is a part of the HTTP protocol determining cache validation, and is best used for static content, such as files, uploaded assets, and pages without output caching. For requests to resources composed from dynamic content objects such as a landing page, using ETags is not recommended.

You can combine ETags with other settings. You can use both Cache-Control "max-age" and ETags to fine-tune cache management and optimize performance. You can also use only ETags, if you have specific caching control requirements.


  • Static deployed files such as CSS
    Set the expire date for as long time interval as possible, then update the URL to include a version number that changes when new static files are uploaded. 
  • Uploaded assets such as images
    ETags are good for this. However, do not set expire times that are longer than the editors can wait for a file to be updated because editors may be confused if they upload a new image with the same name, and the cache still shows the old image.
  • Custom API controllers and "normal" HTML
    Normally, you should not cache dynamic content, but it may be useful in some cases. Only cache if you do not have personalized content. If an API is cached, make sure all variables are pulled from the URI rather than headers to avoid displaying incorrectly cached information, and test thoroughly before going live. Do not cache administrative or confidential information.

Disabling ETags

If you need to disable ETag headers from the HTTP response, do this by adding a setEtag="false" attribute setting to the web.config file under the application root directory, as in the following example.

<clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="1.00:00:00" setEtag="false" />

Caching levels for query strings

The default cache layer setting in DXC Service for query strings is "Standard", meaning that a different resource is delivered each time the query string changes. 

SSL requirements

Proper encryption practices are necessary to prevent bad actors from accessing data. The CDN used in DXC service includes web encryption based on TLS (Transport Layer Security)/SSL (Secure Sockets Layer) protocols, for communication with other services over HTTP (HTTPS).

The service includes a default certificate provided by Episerver, but you can replace this with your own. If you replace the certificate, the following requirements apply:

  • The certificate must be valid (not expired), issued by a trusted Certificate Authority (not self-signed), and the DNS must be correct.
  • The certificate files (certificate and key) should be PEM-encoded.

Versioned URLs for assets

When the application is deployed to DXC environment, there can be some lag-time for assets to update when replacing them in the CMS, due to the asset still being cached in CDN or browsers.

One solution to overcome this is versioning URLs to assets. See https://github.com/bjuris/EPiServer.CdnSupport for an (unsupported) example of how to accomplish this.

Related topics

Do you find this information helpful? Please log in to provide feedback.

Last updated: Apr 08, 2019