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
이 페이지는 현재 영어로만 제공되며 한국어 버전은 곧 제공될 예정입니다. 기다려 주셔서 감사드립니다.

Browser Cache TTL

Feature Introduction

The Client browser cache TTL is the cache duration of resources in the browser, which by default follows the origin's Cache-Control headers. You can control the cache duration of resources in the browser by configuring EdgeOne's browser cache TTL without modifying the origin configuration.
EdgeOne implements browser cache TTL by setting the Cache-Control response headers when responding to clients. The following configurations are supported:
Follow Origin: Follow the origin's Cache-Control; if the origin does not have Cache-Control, no changes will be made;
No Cache: Regardless of whether the origin carries Cache-Control, the browser will be controlled not to cache files;
Custom Time: Regardless of whether the origin carries Cache-Control, the max-age will be modified to the specified cache time.

You can control the cache duration of resources in the browser by adjusting the browser cache TTL, optimizing the cache strategy for different resources, and improving the loading speed of requested resources.

Directions

Scenario One: Configure browser cache TTL for all domains of the site

If you need to configure the same browser cache TTL for the whole connected site, or as a site-wide fallback configuration, please refer to the following steps:
1. Log in to the EdgeOne console and click Site List in the left sidebar.In the site list, click the target Site.
2. On the Site Details page, click Site Acceleration to enter the Global Configuration page. In the right-hand navigation bar, click Cache Configuration.
3. Find the Browser Cache TTL card, click Global Site Settings to modify it.

Default Configuration: Supports following the origin's Cache-Control; if the origin does not have Cache-Control, no caching will be done.

Scenario Two: Configure browser cache TTL for specific domains, paths, or file extensions, etc.

If you need to configure different browser cache TTLs for different domains, paths, or file extensions, such as not caching files with php/jsp/asp/aspx extensions for the www.example.com domain, and caching files with jpg/png/gif/bmp/svg/webp extensions for 1 hour, please refer to the following steps:
1. Log in to the EdgeOne console and click Site List in the left sidebar.In the site list, click the target Site.
2. IOn the site details page, click Site Acceleration to enter the global site configuration page, then click the Rule Engine tab.
3. On the rule engine management page, click Create rule and select Add blank rule.
4. In the rule editing page, first select the matching type as HOST, with the value of www.example.com as the outermost matching condition, and then click Add IF;

5. In the newly added IF condition, select the matching type as File extension, add php/jsp/asp/aspx extensions, click on Action, and in the pop-up operation list, select the operation as browser cache TTL, and configure it as No Cache.
6. Repeat the above steps, add another IF condition, add jpg/png/gif/bmp/svg/webp extensions, and configure it as cache for 1 hour.
7. After the configuration, the rule is as follows, click Save and Publish to complete the rule configuration.