Additional Configurations for Dynamic Distributions


Bypass cache by selected cookies: This option can take a No value or you can expand the Select option to configure cookies.


An HTTP cookie (also called web cookie, Internet cookie, browser cookie, or simply cookie) is a small piece of data stored on the user's computer by the web browser while browsing a website. Cookies were designed to be a reliable mechanism for websites to remember stateful information (such as items added in the shopping cart in an online store) or to record the user's browsing activity (including clicking particular buttons, logging in, or recording which pages were visited in the past). They can also be used to remember pieces of information that the user previously entered into form fields, such as names, addresses, passwords, and payment card numbers.

By default, MerlinCDN doesn’t consider cookies when processing requests and responses, or when caching content in your distributions. You can configure MerlinCDN to forward selected cookies in visitor requests to your origin, and to bypass the cache settings in your distribution and cache separate versions of your content based on the cookie values.

Max request size: This option can take size values in MB. Its max value can be 100MB. You can configure max request size by choosing from the dropdown list or setting a custom value in MB.

    • It is used to put a limit on request size from end users/visitors for HTTP PUT and POST requests to your distribution. For example, you have a contest section on your website where the end users/visitors upload videos. If there is no limit on the size of their requests, your origin server might not handle an unexpected amount of inbound traffic. In this example, setting a limit also allows you to make traffic estimations more accurately.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.