Configuring Cache
EdgeOne Pages uses edge networks to cache your static resource content worldwide, which is closer to users than storing on the origin server. This can reduce server load and improve website performance, thereby increasing your website's access speed.
Browser Cache
To provide your users with a high-quality access experience, Pages applies differentiated handling to the browser cache policy for static files:
Files with hash (such as main.a1b2c3.js): set max-age=31536000 (one year) to achieve long-term cache.
Files without hash (such as index.html): set max-age=0 to underwrite content freshness.
You can overwrite Pages' default rule by configuring headers in edgeone.json. For the method, see edgeone.json-headers.
Edge Cache
Pages' default settings are optimized for edge caching of static resources. These resources are cached on EdgeOne nodes after the first request, with a maximum cache time of three months. Meanwhile, edge cache is automatically invalidated after each new deployment, ensuring users always retrieve the latest content. Therefore, in most cases, you should avoid setting caching logic for static resources on EdgeOne nodes.
You can also configure edge cache time for different resources based on business needs, optimize edge cache policy for different resources, and enhance loading speed of requested resources. For the method, see edgeone.json cache.
Warning:
As long as the project triggers a new deployment, edge cache will automatically invalidate to ensure users can access the latest content.
