Bypass CDN Cache for Website Testing in NetSuite

Bypassing CDN cache allows developers to view site updates immediately during testing and development without the interference of cached content.

·2 min read·View Oracle Docs

TL;DR

Bypassing the CDN cache is crucial for developers and testers working on websites within NetSuite. It enables immediate visibility of changes made to the site, ensuring updated content is reflected without interference from cached versions.

How Can You Bypass the CDN Cache?

As a developer, there are two primary methods to bypass the CDN cache during website development and testing:

  • Using a Sandbox Domain: You can create a domain associated with a sandbox account that does not have CDN caching enabled. This allows for testing the latest updates in a secure environment without affecting the production account.
  • Using a Subdomain: Set up a subdomain associated with your main production account but configured without CDN caching. The naming convention should follow the pattern development(substring).<domain>.<top-level domain>.
    • For example, if your domain is example.com, possible test domains could include:
      • development.example.com
      • development2.example.com
      • development-temp.example.com

To test your website changes, simply navigate to your specifically configured test domain. This ensures that any updates are visible without loading older cached versions of the site.

Why Is This Important?

Bypassing the CDN cache is particularly valuable when making frequent updates or modifications during the development cycle. It ultimately enhances testing efficiency and accuracy, enabling developers to validate website changes seamlessly before going live.

Who Should Use This Feature?

This functionality is essential for:

  • Developers working on website customizations and updates.
  • Testers validating the performance and appearance of changes made to the site.

Key Takeaways

  • You can bypass the CDN cache using a dedicated sandbox domain or a specifically named subdomain.
  • Using a non-cached domain allows for immediate viewing of updates during testing.
  • This method helps ensure accuracy and efficiency in website development processes.

Source: This article is based on Oracle's official NetSuite documentation.

Frequently Asked Questions (4)

What methods can I use to bypass CDN cache in NetSuite?
You can bypass the CDN cache by using a sandbox domain associated with a sandbox account without CDN caching, or by setting up a subdomain configured without CDN caching for your main production account.
How should I name my subdomain to bypass CDN cache?
The naming convention for your subdomain should follow the pattern development(substring).<domain>.<top-level domain>, such as development.example.com or development2.example.com.
Does bypassing the CDN cache affect the production account?
Bypassing the CDN cache using a sandbox domain or a non-cached subdomain does not affect the production account, as changes are made visible only in the testing environment.
Can both developers and testers benefit from the bypass CDN cache feature?
Yes, both developers and testers can benefit from bypassing the CDN cache, as it enhances testing efficiency and accuracy by ensuring immediate visibility of website updates.
Source: Bypass CDN Cache 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 General

View all General articles →