Skip to main content
Prefetch requests files from the origin and stores them in CDN cache before visitors request them, so edge locations can serve the content without fetching it from the origin on the first request. A CDN resource is required.
Prefetch causes CDN servers to request the listed files from the origin, which increases origin load and traffic.
Prefetch is recommended for files larger than 200 MB and smaller than 5 GB. Each request is limited to 100 paths, and one prefetch request is allowed per CDN resource per minute.
1

Open Prefetch

In the Gcore Customer Portal, navigate to CDN > Prefetch.
2

Select the CDN resource

Select the resource whose origin holds the files. The dropdown shows each option as CNAME and ID.
3

Enter file paths

Enter one path per line without a domain, starting with a slash: /path/file1.jpg.
Prefetch form with resource dropdown and path field
4

Submit the prefetch request

Click Prefetch.
5

Confirm the files are cached

Prefetch processing time depends on the number and size of the files — allow time for the operation to complete before testing.To verify, request a listed path from the CDN hostname and inspect the Cache response header on the first request from your test location:
  • Cache: HIT on the first request means prefetch already populated that edge location.
  • Cache: MISS on the first request followed by Cache: HIT on the next means the first request filled the cache. That edge was not populated by prefetch — either prefetch has not yet completed, or that location was not reached.
To replace files that are already in cache, purge those files, then prefetch.