NetSuite Changelog
CommercePerformanceeCommerceBest Practices

CDN Caching Times and Content Update Impact

CDN caching times affect how quickly returning customers see updated content, with varying durations for static content, scripts, and page delivery.

·2 min read·2 views·View Oracle Docs

Caching within a Content Delivery Network (CDN) is crucial for how quickly returning customers can view updated content on your site. CDN caching times vary by content type and significantly influence user experience.

What Are CDN Caching Times?

CDN caching times determine how long different types of content remain accessible from the cache before they are refreshed. Below is a breakdown of common content types and their respective caching durations:

Type of ContentExampleHow Long is it Cached?
Static ContentImages, CSS7 days
ScriptsNon-session scripts2 hours
Content Deliverypage.ss5 minutes

Cache Invalidation and Browser Cache Behavior

You can utilize the Cache Invalidation Request form to clear the CDN cache. However, it is important to realize that this action does not affect the browser cache. Here’s how it works:

  • When you invalidate a URL, new users immediately see the updated content.
  • Users reloading the page with a hard refresh (Ctrl + F5) will also see the latest content.
  • Returning visitors, however, will continue to see the old content stored in their browser cache until it expires.

Automatic Expiration of Browser Cache

If the CDN is enabled, the static content in the browser cache automatically expires every two hours. This means that if visitors return after this duration, they are required to fetch fresh data from the CDN cache. If the static data has been updated in that time frame, users will receive the latest version once they request it from the CDN.

Understanding CDN caching and its implications is essential for providing a smooth experience for users, especially returning customers. Proper management of these caching rules can ensure your content delivery is efficient and up-to-date.

Frequently Asked Questions (4)

How does CDN caching affect static content like images and CSS in NetSuite?
In a CDN, static content such as images and CSS is cached for 7 days. This means that returning users may still see the old version of static content until the cache is refreshed after this duration.
How can I force the CDN to deliver updated content immediately in NetSuite?
You can use the Cache Invalidation Request form to clear the CDN cache, which will immediately display updated content to new users and users performing a hard refresh. However, this action does not affect the browser cache for returning users until it naturally expires.
What is the difference between CDN cache and browser cache expiration in NetSuite?
CDN caching affects the duration content stays in the CDN before requiring a refresh, while browser cache expiration determines how long cached content is kept by the user's browser. With CDN enabled, browser cache for static content expires every two hours, ensuring returning visitors can access updates if the CDN cache has fresh data.
Does browser cache expiration impact users who have seen prior versions of the content?
Yes, returning visitors may continue to see cached (old) content from their browser until the browser cache naturally expires, which is every two hours if CDN is enabled. After expiration, they will receive updated content as fetched from the CDN.
Source: CDN Caching Times — Oracle NetSuite Help Center. This article was generated from official Oracle documentation and enriched with additional context and best practices.

Was this article helpful?

More in Commerce

View all Commerce articles →