Configuring Cache
EdgeOne Maker caches your static resource content globally using the edge network. Compared to storing resources on the origin server, this places them closer to users, which reduces server load and improves website performance, thereby increasing your website's access speed.
Browser Cache
To provide your users with a high-quality access experience, Makers apply differentiated handling to the browser caching 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 override Makers' default rules by configuring headers in edgeone.json. For specific configuration methods, refer to edgeone.json-headers.
Edge Cache
Makers' 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 duration of three months. Additionally, the edge cache is automatically invalidated after each new deployment, ensuring users always obtain the latest content.
Warning:
The edge cache is automatically invalidated whenever a new deployment is triggered for the project, ensuring users can access the latest content.
