Edge Acceleration
  • Site Acceleration
    • Overview
    • Quickly Import and Export Site Configuration
    • Access Control
      • Token Authentication
    • Smart Acceleration
    • File Optimization
      • Smart Compression
    • Network Optimization
      • HTTP/2
      • HTTP/3(QUIC)
        • Overview
        • Enable HTTP/3
        • QUIC SDK
          • SDK Overview
          • SDK Download and Integration
          • Sample Code
            • Android
            • iOS
          • API Documentation
            • Android
            • iOS
      • IPv6 Access
      • Maximum Upload Size
      • WebSocket
      • Client IP Geolocation Header
      • Client IP Geographical Location
      • gRPC
    • URL Rewrite
      • Access URL Redirection
      • Origin-Pull URL Rewrite
    • Modifying Header
      • Modifying HTTP Response Headers
      • Modifying HTTP Request Headers
    • Custom Error Page
    • Request and Response Actions
      • Processing order
      • Default HTTP Headers of Origin-Pull Requests
      • Default HTTP Response Headers
    • Media Services
      • Audio and Video Pre-pulling
      • Just-in-Time Image Processing
      • Just-in-Time Media Processing
      • VOD Media Origin
  • L4 Proxy
    • Overview
    • Creating an L4 Proxy Instance
    • Modifying an L4 Proxy Instance
    • Disabling or Deleting an L4 Proxy Instance
    • Batch Configuring Forwarding Rules
    • Obtaining Real Client IPs
      • Obtaining Real TCP Client IPs via TOA
      • Obtaining Real Client IPs Through Protocol V1/V2
        • Overview
        • Method 1: Obtaining Real Client IPs Through Nginx
        • Method 2: Parsing Real Client IPs on Application Server
        • Format of Real Client IPs Obtained Through Proxy Protocol V1/V2
      • Transmitting Client Real IP via SPP Protocol
  • Edge DNS
    • Hosting DNS Records
      • Modifying DNS Servers
      • Configuring DNS Records
      • Advanced DNS Configuration
    • Domain Connection
      • Adding A Domain Name for Acceleration
      • Ownership Verification
      • Modifying CNAME Records
    • Domain alias
      • Overview
      • Configuration Guide
      • Batch Connecting SaaS Domain Names
      • Configuring Alias Domain Names for Disaster Recovery
    • Traffic Scheduling
      • Traffic Scheduling Management
    • Origin Configuration
      • Origin-pull configuration
        • Configuring Origin-Pull HTTPS
        • Host Header Rewrite
        • Controlling Origin-pull Requests
        • Redirect Following During Origin-Pull
        • HTTP/2 Origin-Pull
        • Range GETs
      • Load Balancing
        • Overview
        • Quickly Create Load Balancers
        • Health Check Policies
        • Viewing the Health Status of Origin Server
        • Related References
          • Load Balancing-Related Concepts
          • Introduction to Request Retry Strategy
      • Origin Group Configuration
      • Related References
        • ld Version Origin Group Compatible Related Issues
      • Collect EdgeOne origin-pull node IP
  • Edge Cache
    • Overview
    • EdgeOne Cache Rules
      • Content Cache Rules
      • Cache Key Introduction
      • Vary Feature
    • Cache Configuration
      • Custom Cache Key
      • Node Cache TTL
      • Status Code Cache TTL
      • Browser Cache TTL
      • Offline Caching
      • Cache Prefresh
    • Clear and Preheat Cach
      • Cache Purge
      • URL Pre-Warming
    • How to improve the Cache Hit Rate of EdgeOne
  • Rules Engine
    • Overview
    • Supported Matching Types and Actions
    • Rule Management
    • variables
Docs Overview/
Edge Acceleration/
Edge Cache/
Clear and Preheat Cach/
URL Pre-Warming/

URL Pre-Warming

Function Introduction

When a business releases new resources, the client's first request for these resources may encounter a situation where there is no cache on EdgeOne, resulting in an inability to respond immediately and the need to follow the origin to obtain. The cache pre-warming function allows resources to be cached on EdgeOne in advance. In this way, even if the client requests for the first time, it can be directly responded from the cache of EdgeOne without the need to follow the origin. The implementation of cache pre-warming is to submit the URLs that need to be pre-warmed, and then cache the resources that match these URLs from the origin to EdgeOne in advance, thereby improving the acceleration effect and mitigating the pressure on the origin.

Quota Description

Different billing plans have different quotas, please refer to: Comparison of EdgeOne Plans.

Usage Scenarios

You may need to use this function in the following scenarios:
Newly released content: When your business releases new content or updates existing content, you want to ensure that this content is immediately available on EdgeOne, so that client users can access the latest content for the first time, reducing the delay when accessing for the first time. For example, before the game business officially releases a new version of the installation package or upgrade package, the installation package resources can be preheated to EdgeOne. After the official release, users can directly obtain the installation package resources from the node when requesting to download these installation packages, improving the download speed.
Large-scale event operations: Before large-scale events, you want to ensure that the key resources of the event have been cached on EdgeOne, which helps to ensure that when the event starts, client users can quickly access the required content, reducing the delay and congestion caused by high traffic.
Expected traffic peaks: If you expect a significant increase in website traffic during a specific period (e.g., holiday promotions, news releases, etc.), you can use the cache pre-warming function to ensure that key resources have already been cached on the edge nodes. This helps to disperse the pressure of origin-pull requests during peak periods and improve the access speed of client users.
Note:
When preheating resources, simulated requests will be made to retrieve the corresponding resources from the origin. If there are many preheating tasks submitted, more origin-pull requests will be generated, and the bandwidth of the origin will increase.
If the preheated resources conflict with the node cache, that is, if EdgeOne has cached identical resources and they have not expired, they will still be valid and will not be overwritten by the preheated resources. If the identical resources have changed, you can purge the corresponding node cache before preheating.
A maximum of the first 10,000 records can be displayed for cache pre-warming history query. If more records are needed, it is recommended to narrow down the query scope or click Export Records at the bottom of the list. Currently, up to 500,000 records can be exported.

Directions

Scenario One: Prefetch cache by inputting content

If you have less content to preheat and it is convenient to input the content directly in the input box, please follow the steps below:
1. Log in to the EdgeOne console, In the left sidebar menu, click Prefetch URLs.
2. On the Prefetch URLs page, select the corresponding site, enter the respective resource content, and click OK.

3. Switch to the History Record tab to view the history records within a specified time range (within one month).

Scenario Two: Batch import Prefetch cache content by uploading files

If you have more content to preheat or have already placed the content in a file, you can choose to upload the file:
1. Log in to the EdgeOne console, In the left sidebar menu, click Prefetch URLs.
2. On the Prefetch URLs page, select the corresponding site, choose the "Upload File" method, and after uploading, click OK.

3. Switch to the History Record tab to view the history records within a specified time range (within one month).

Related References

How long does it take for cache purge and cache pre-warming to take effect after submitting content?