By configuring the browser cache validity, you can customize client browser cache policies to reduce origin-pull rate.
When a request comes, if the requested resource is cached on the browser, it will be returned directly. If no, the request will be forwarded to CDN cache nodes. If the resource still cannot be found on the cache node, the request will be forwarded to the origin server.
Log in to the CDN console, select Domain Management on the left sidebar, click Manage on the right of a domain name to enter its configuration page. Open the Cache Configuration tab to find the Browser Cache Validity Configuration section.
Click Add Rule to add browser cache validity rules for specified file type, file directory, file path, and homepage.
Cache-Controlheader of the origin server. If the origin server does not have a CC header or its CC header is
no-cache/no-store/private, the browser will not cache resources.
no-cache/no-store/private, the browser cache validity rules will be applied; otherwise, the browser will not cache resources.
If no rule is configured or matches requests, the default policies will be applied:
Cache-Controlwill be followed.
Cache-Control, then the resource cache validity on the browser will be 600 seconds.
When there are node cache validity rules configured (configuration guide: Node Cache Validity Configuration (New)) or matched:
Cache-Control, then the browser will not cache resources.
Cache-Control, then the browser cache will follow
Contact our sales team or business advisors to help your business.
Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.
Was this page helpful?