How do I tell whether user access has hit the EdgeOne cache?
EdgeOne identifies whether a request hit the cache via EO-Cache-Status.
Open in browser
Curl command
Open the console in the browser and access the request URL (such as https://example.com/test.webp). Check the response header. If the value of EO-Cache-Status is HIT, the cache is hit.
For Mac/Linux OS, you can use curl command to verify (such as curl https://example.com/test.webp -i). Check the response header. If the value of EO-Cache-Status is HIT, the cache is hit.
How to handle cross-origin errors when prefetching?
Since resources are prefetched through URLs, cross-origin headers are not required. When a cross-origin request is initiated, the request fails because these headers are not present in the cache.
To enable cross-origin support for your resources when prefetching, you can customize the HTTP response header in EdgeOne.
How long does it take for Cache Purge and Cache Pre-Warming to take effect after each content submission?
Cache Purge：
Type
Single Submission quantity
Effective Time
URL
1-5000 URLs
5-50 minutes
Directory
1-1000 directories
5-220 minutes
Hostname
1-1000 Hostname
5-220 minutes
Cache-Tag
1-100 Cache-Tag
5-10 minutes
All Cache
-
5-220 minutes
Cache Pre-Warming:
Type
Single Submission quantity
Effective Time
URL
1-5000 URLs
5-30 minutes
Note：
1. When the cache TTL configured for a file is less than 5 minutes, it is suggested not to use the purge tool, but to wait for the timeout update.
2. The actual total time for any type of cache purge mainly depends on the quantity of submitted content, the more content, the longer the waiting time.
3. The actual total time for cache pre-warming mainly depends on the file size, the larger the file, the longer the waiting time. The pre-warming effective time for more large files (≥100MB) may be extended, exceeding 30 minutes.
