Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Learn how Edge Cache Expiration determines caching behavior and freshness for dynamic content at CDN edge servers.
The Edge Cache Expiration feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It defines how the CDN caches objects at the edge and how long cached responses remain valid before refreshing from the origin. You can configure cache modes that rely on Panel-defined TTL values, defer to origin headers, or disable caching entirely for dynamic workloads.
For configuration details, cache modes, and examples, refer to the main documentation: Learn more in the Edge Cache Expiration documentation.
Learn how Browser Cache Rules define how long dynamic content remains cached in the visitor’s browser.
The Browser Cache Rule feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It controls browser-side caching by defining cache duration, cache modes, and rule priorities for different URL patterns, directories, or file types. These rules determine how browsers store and revalidate dynamic content, independent of CDN edge caching behavior.
For configuration details, rule types, and examples, refer to the main documentation: Learn more in the Browser Cache Rule documentation.
Learn how Stale Cache enables serving previously cached dynamic content when the origin becomes temporarily unavailable.
The Stale Cache feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It allows CDN edge servers to deliver the last cached version of an object when the origin fails to respond or returns specific error codes. You can define which origin conditions—such as timeouts, invalid headers, or 5xx errors—trigger stale delivery. This improves availability for dynamic workloads during short-term origin instability.
For configuration details, supported triggers, and examples, refer to the main documentation: Learn more in the Stale Cache documentation.
The Disallow Cookie-Based Cache feature in the Medianova Cloud Panel allows you to prevent caching for requests containing specific cookie values. By defining multiple key-value pairs, you can control how the cache behaves when certain cookies are present, ensuring that caching policies align with your requirements.
Prevent Caching for Specific Cookies: When enabled, this feature allows you to specify cookie key-value pairs that should bypass caching. Requests containing these cookies will not be cached, ensuring dynamic and personalized content delivery.
Support for Multiple Key-Value Pairs: You can define multiple cookie key-value pairs to tailor caching behavior for a variety of scenarios. This provides flexibility in managing caching for complex applications with diverse user interactions.
Enable the Feature: Toggle the Disallow Cookie-Based Cache option to "On" in the panel.
Define Cookie Key-Value Pairs:
Enter the cookie key in the provided field.
Enter the corresponding cookie value.
Navigate to the CDN Resources section in the left-hand menu of the Medianova Cloud Panel.
Select the relevant resource.
Click on the Caching tab.
Scroll down to the Disallow Cookie-Based Cache section.
Important Notes
Granular Control: This feature ensures that requests containing specified cookies bypass the cache, enabling precise control over cache behavior for dynamic content.
Multiple Key-Value Pairs: You can define as many key-value pairs as necessary to accommodate your application's caching needs.
By configuring the Disallow Cookie-Based Cache settings, you can optimize cache management for scenarios requiring personalized or dynamic content delivery, ensuring seamless and accurate user experiences.
The Cookie-Base Cache feature in the Medianova Cloud Panel enables caching decisions based on specific cookies. This feature allows you to define multiple cookie values, ensuring that content caching aligns with different user sessions and dynamic content requirements.
Cache Based on Specific Cookies: When enabled, this feature ensures that caching behavior is determined by the presence and values of specified cookies. This is particularly useful for personalizing content or delivering dynamic resources based on user-specific data.
Support for Multiple Cookies: You can define multiple cookies to fine-tune caching strategies for diverse user interactions. Each cookie value can influence how the cache is managed for specific scenarios.
Navigate to the CDN Resources section in the left-hand menu of the Medianova Cloud Panel.
Select the relevant resource.
Click on the Caching tab.
Scroll down to the Cookie-Based Cache section.
Important Notes
Dynamic Content Optimization: This feature helps deliver personalized or session-specific content by adjusting caching behavior based on user cookies.
Multiple Cookie Values: Define as many cookie values as necessary to address the caching needs of your application.
By configuring the Cookie-Based Cache settings, you can ensure a seamless user experience while optimizing caching for dynamic and personalized content delivery.
Learn how ETag Verification ensures cached dynamic content remains consistent with the origin.
The ETag Verification feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It compares the ETag value returned by the origin with the ETag of the cached object and refreshes the cache when a mismatch occurs. This ensures the CDN serves the most up-to-date version of dynamic content and prevents stale objects from being delivered to end users.
For configuration details, validation behavior, and examples, refer to the main documentation: Learn more in the.
Learn how Error Status Code Cache Expiration defines caching duration for error responses in dynamic workloads.
The Error Status Code Cache Expiration feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It allows you to define custom cache durations for specific HTTP error codes so the CDN can temporarily store repeated error responses, reducing unnecessary load on the origin. Each status code can have its own TTL, and caching can be enabled or disabled per code based on your requirements.
For configuration details, supported behaviors, and examples, refer to the main documentation: Learn more in the .
Use the + button to add additional key-value pairs as needed.
Submit Changes: After entering the required cookie key-value pairs, click the Submit button to save and apply your changes.
Toggle the feature to "On."
Define cookie key-value pairs:
Enter the cookie key and value in the respective fields.
Use the + button to add more key-value pairs.
Click Submit to apply the changes.
Toggle the feature to "On."
Define cookie values:
Enter the cookie key in the respective field.
Use the + button to add more cookies.
Click Submit to apply the changes.
Learn how Shared Cache defines whether dynamic content is cached independently or shared across accounts.
The Shared Cache feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It determines whether CDN edge nodes use an isolated cache namespace for your account (Default) or a shared cache namespace across multiple accounts that use the same Domain Cache Key (Share). When shared mode is enabled, identical content is cached once and reused across participating accounts, improving efficiency and reducing redundant origin requests.
For configuration details, cache modes, and examples, refer to the main documentation: Learn more in the Shared Cache documentation.
Learn how Query String Caching defines cache key behavior for dynamic URLs containing query parameters.
The Query String Caching feature for Dynamic Content Acceleration operates the same way as in Static Content Delivery. It determines how the CDN evaluates query parameters when generating cache keys, allowing you to cache each query string variant separately, ignore specific parameters, or build cache keys using only selected values. These configurations provide granular control over caching behavior for dynamic endpoints, APIs, and personalized content.
For configuration details, caching modes, and examples, refer to the main documentation: Learn more in the Query String Caching documentation.
Learn how Mobile Device Cache creates device-specific cache variations for dynamic content.
The Mobile Redirect feature in the Medianova Cloud Panel allows for the redirection and caching of content based on the device type (mobile or desktop). This functionality is designed to optimize the delivery of content by providing device-specific responses, ensuring that mobile users receive content tailored for their devices while desktop users are directed to the standard version of the site.
This feature helps improve both performance and user experience by customizing content delivery depending on whether the user is on a mobile or desktop device.
Device-Specific Redirection: The Mobile Redirect feature enables you to redirect users based on the device they are using, either a mobile device or a desktop. This ensures that mobile users are directed to a mobile-optimized version of the site, while desktop users continue to access the standard desktop version.
Optimized Mobile Content Delivery: When enabled, mobile-specific content can be cached separately for faster delivery to mobile users. This ensures that mobile users receive a tailored experience, improving load times and performance on mobile devices.
Enabling Mobile Redirect: The Mobile Redirect feature can be activated by toggling the setting to On. Once activated, the system will begin redirecting traffic based on device type.
Force User-Agent:
When the Force User-Agent option is set to On, the system automatically adds the query parameter ?mobile=true to requests from mobile User-Agents. This allows the backend to identify the request as originating from a mobile device.
In the Medianova Cloud Panel, navigate to the CDN Resources section from the left-hand menu.
Select the relevant resource that you want to configure.
Click on the Caching tab to access the caching settings.
Scroll down to the Mobile Redirect section and toggle the setting to On.
Important Notes
Mobile-Specific Caching: Enabling Force User-Agent will result in separate caching for mobile content, ensuring faster delivery of mobile-optimized resources.
Redirection Control: You have full control over the redirection behavior, including whether to keep or drop the original URI path and whether to redirect mobile or desktop users.
Redirection URL: It is important to specify a valid URL for the Mobile Redirect URL to ensure the redirection works as intended.
By configuring the Mobile Redirect feature, you ensure that users on mobile devices are served optimized content while desktop users are directed to the appropriate version of the site. This helps improve the overall user experience by tailoring content delivery to the device type.
The Header Value-Based Cache feature in the Medianova Cloud Panel allows you to control caching behavior based on specific header values. By defining the type (deny or allow), along with the header and its corresponding value, you can precisely determine whether content should be cached.
Control Caching with Header Values: This feature enables caching rules to be influenced by specific header values, allowing for flexible and dynamic cache management.
Deny or Allow Caching: You can specify whether to deny or allow caching based on the presence of a particular header value.
Navigate to the CDN Resources section in the left-hand menu of the Medianova Cloud Panel.
Select the relevant resource.
Click on the Caching tab.
Scroll down to the Header Value-Based Cache section.
Important Notes
Precise Cache Control: This feature ensures that caching behavior is determined by specific header values, providing granular control over cache management.
Single Rule Definition: You can define one header value-based caching rule at a time. Additional rules can be added later if needed.
By configuring the Header Value-Based Cache settings, you can optimize caching for scenarios where header values dictate whether content should be cached, ensuring efficient content delivery and personalized user experiences.
The MNUID Cookie-Based Cache feature in the Medianova Cloud Panel enables caching decisions based on the MNUID cookie. By specifying the cookie's expiry time, you can control how long the cached content remains valid for users with the MNUID cookie.
Cache Based on MNUID Cookie: This feature ensures that caching behavior is determined by the presence of the MNUID cookie, optimizing cache management for personalized user sessions.
The Header-Base Cache feature in the Medianova Cloud Panel enables caching decisions based on specific HTTP headers. By defining multiple header key-value pairs, you can control how content is cached depending on the request headers, allowing for advanced caching strategies tailored to your application's needs.
Cache Based on HTTP Headers: When enabled, this feature allows caching behavior to be determined by specific HTTP header key-value pairs, ensuring dynamic and personalized content delivery.
Enabling this setting also ensures that mobile content is cached separately, optimizing delivery and performance for mobile users.
Default Setting: The Force User-Agent option is Off by default. When turned On, it triggers the caching of mobile-specific content and enables faster delivery.
Important: When Force User-Agent is On, the following settings will not be visible:
Mobile Redirect Keep Path
Mobile Redirect Type
Mobile Redirect URL
Additional Settings (Visible only when Force User-Agent is Off): If Force User-Agent is turned Off, the following additional configuration options become available:
Mobile Redirect Keep Path: Determines how the URI path is handled during the redirection process.
Keep: Retains the original URI path when redirecting users to the mobile or desktop version of the site.
Drop: Removes the URI path during redirection. This option is useful if you want to redirect users to a different URL without keeping the original path.
Mobile Redirect Type: Specifies the direction of the redirection:
Desktop to Mobile: Redirects desktop users to the mobile version of the site.
Mobile to Desktop: Redirects mobile users to the desktop version of the site.
Mobile Redirect URL: Defines the URL to which users will be redirected. This is a required field when configuring mobile redirects. You must specify a valid URL for the redirection to function correctly.
Submitting Changes: After configuring the desired settings, click the Submit button to save and apply the changes. This will activate the mobile redirection and caching settings based on your configuration.
If Force User-Agent is set to Off, configure the following options:
Select either Keep or Drop for the Mobile Redirect Keep Path option.
Choose the appropriate Mobile Redirect Type (Desktop to Mobile or Mobile to Desktop).
Enter the Mobile Redirect URL for the target redirection.
Click Submit to apply the changes.
Enable the Feature: Toggle the Header Value-Based Cache option to "On" in the panel.
Define Header Caching Rules:
Type: Select whether to deny or allow caching based on the header value.
Header: Enter the HTTP header name.
Value: Enter the corresponding header value.
Submit Changes: After filling in the fields, click the Submit button to save and apply your changes.
Cookie Expiry Time Configuration: Define the expiry time (in seconds) for the MNUID cookie to control the validity period of cached content.
Navigate to the CDN Resources section in the left-hand menu of the Medianova Cloud Panel.
Select the relevant resource.
Click on the Caching tab.
Scroll down to the MNUID Cookie-Based Cache section.
Enable the Feature: Toggle the MNUID Cookie-Based Cache option to "On" in the panel.
Set Cookie Expiry Time:
Enter the expiry time (in seconds) for the MNUID cookie in the provided field.
Submit Changes: After setting the expiry time, click the Submit button to save and apply your changes.
Important Notes
Granular Cache Control: This feature allows you to fine-tune cache validity for users with the MNUID cookie, ensuring efficient and personalized content delivery.
Cookie Expiry Management: The specified expiry time determines how long the cached content remains valid for requests containing the MNUID cookie.
By configuring the MNUID Cookie-Based Cache settings, you can enhance caching strategies for user sessions relying on the MNUID cookie, improving performance and user experience.
Support for Multiple Headers: You can define multiple header key-value pairs to fine-tune caching rules for diverse request scenarios.
Navigate to the CDN Resources section in the left-hand menu of the Medianova Cloud Panel.
Select the relevant resource.
Click on the Caching tab.
Scroll down to the Header-Base Cache section.
Toggle the feature to "On."
Define header key-value pairs:
Enter the header key and value in the respective fields.
Use the + button to add more header key-value pairs.
Click Submit to apply the changes.
Important Notes
Granular Control: This feature ensures that requests with specific HTTP headers influence caching decisions, enabling more precise cache management.
Multiple Header Key-Value Pairs: Define as many header key-value pairs as necessary to meet the caching requirements of your application.
By configuring the Header-Base Cache settings, you can optimize caching strategies for requests that vary based on HTTP headers, improving both performance and user experience.
