CDN Caching
Starting September 2025, CDN caching will be required for all websites associated with NetSuite production accounts. See Enable CDN Caching to turn on CDN caching before the deadline and avoid performance issues with your site.
You can optimize your website and decrease page-loading time by caching data and site assets on the Content Delivery Network (CDN) available with Commerce web stores. After you set up a CDN cache, data and site assets that are reused across your web store are always cached. Caching lets reused data and assets be read quickly, which boosts site performance.
NetSuite SuiteCommerce uses a state-of-the-art CDN to protect you and your users from internet threats such as DDoS attacks, aggressive bots, and other fraudulent activities. NetSuite has set up and fine-tuned a wide range of protective measures for SuiteCommerce, including rate limiting, bot management, web application firewall, IP reputation management, and geo-blocking according to Oracle policy. A team of network and security engineers monitors and updates these measures 24/7.
To learn more about CDN Caching, refer to the following sections:
Items Cached
The following items are cached by the CDN:
-
All image files in the file cabinet, using file extensions such as, .gif, .jpg, .bmp, and .png, as well as static file system images that might be referenced from default site templates.
-
The response output from the Item Search API. For example, a request to the Item Search API that returns a list of items.
-
The response output of executed SuiteScript hosted outside the file cabinet, if it sets response headers indicating the content can be cached. This refers to SuiteScript associated with SSP applications.
-
SSP files
Files in the file cabinet that you sell as download items aren’t cached by the CDN.
CDN Caching Times
How long a type of content stays cached in the CDN also affects how quickly returning customers see updated content.
|
Type of Content |
Example |
How long is it Cached? |
|---|---|---|
|
Static Content |
Images, CSS |
7 days |
|
Scripts |
Scripts that aren't dependent on the session |
2 hours |
|
Content Delivery |
page.ss |
5 minutes |
You can use the Cache Invalidation Request form to clear the CDN cache, but the browser cache isn't affected. For example, when you invalidate a URL, new customers see new content right away. Customers who reload the page without using the cache, for example, by using the Ctrl +F5 keys, also see new content right away. But returning customers who reload the page normally keep seeing old content until it expires in their browser cache.
If CDN's enabled, static content in the browser cache automatically expires every two hours. This means that if visitors return to the website more than two hours after their last visit, they must request fresh data from the CDN cache. If the static data in the CDN cache was refreshed, either manually or automatically, during those two hours, visitors get the new website content from the CDN cache.
Types of Domains to Use with CDN Caching
The following domain types allow CDN caching:
-
Web Store Only
-
Checkout Only
-
Single Domain for Web Store and Checkout
-
Hosted Web Pages
To use CDN caching with a web store domain, the domain must be associated with a SuiteCommerce or SuiteCommerce Advanced website. CDN caching can't be used with SiteBuilder sites.
For Hosted Web Pages, the domain isn't associated with a website, but you must use an account with SuiteCommerce or SuiteCommerce Advanced.
For more information about types of domains, see Set Up Domains for Web Stores.
Limiting Cache
As you build your Commerce web store, it's important to see your changes in real time. After you set up CDN caching, you can use tools and strategies to make sure you're seeing the latest website content. For more information, read the following topics:
-
Bypass CDN Cache – Use this strategy to set up a subdomain for testing changes to your website.
-
Cache Invalidation Request – Learn how to invalidate the cache for the whole domain or for specified URLs.
-
Find URLs for Cache Invalidation – Learn how to locate specific URLs for cache invalidation requests. This topic also includes guidelines for sending cache invalidation requests for different types of website updates, such as banners and style sheets.