tencent cloud

Cloud Object Storage

Release Notes and Announcements
Release Notes
Announcements
Product Introduction
Overview
Features
Use Cases
Strengths
Concepts
Regions and Access Endpoints
Specifications and Limits
Service Regions and Service Providers
Billing
Billing Overview
Billing Method
Billable Items
Free Tier
Billing Examples
Viewing and Downloading Bill
Payment Overdue
FAQs
Getting Started
Console
Getting Started with COSBrowser
User Guide
Creating Request
Bucket
Object
Data Management
Batch Operation
Global Acceleration
Monitoring and Alarms
Operations Center
Data Processing
Content Moderation
Smart Toolbox
Data Processing Workflow
Application Integration
User Tools
Tool Overview
Installation and Configuration of Environment
COSBrowser
COSCLI (Beta)
COSCMD
COS Migration
FTP Server
Hadoop
COSDistCp
HDFS TO COS
GooseFS-Lite
Online Tools
Diagnostic Tool
Use Cases
Overview
Access Control and Permission Management
Performance Optimization
Accessing COS with AWS S3 SDK
Data Disaster Recovery and Backup
Domain Name Management Practice
Image Processing
Audio/Video Practices
Workflow
Direct Data Upload
Content Moderation
Data Security
Data Verification
Big Data Practice
COS Cost Optimization Solutions
Using COS in the Third-party Applications
Migration Guide
Migrating Local Data to COS
Migrating Data from Third-Party Cloud Storage Service to COS
Migrating Data from URL to COS
Migrating Data Within COS
Migrating Data Between HDFS and COS
Data Lake Storage
Cloud Native Datalake Storage
Metadata Accelerator
GooseFS
Data Processing
Data Processing Overview
Image Processing
Media Processing
Content Moderation
File Processing Service
File Preview
Troubleshooting
Obtaining RequestId
Slow Upload over Public Network
403 Error for COS Access
Resource Access Error
POST Object Common Exceptions
API Documentation
Introduction
Common Request Headers
Common Response Headers
Error Codes
Request Signature
Action List
Service APIs
Bucket APIs
Object APIs
Batch Operation APIs
Data Processing APIs
Job and Workflow
Content Moderation APIs
Cloud Antivirus API
SDK Documentation
SDK Overview
Preparations
Android SDK
C SDK
C++ SDK
.NET(C#) SDK
Flutter SDK
Go SDK
iOS SDK
Java SDK
JavaScript SDK
Node.js SDK
PHP SDK
Python SDK
React Native SDK
Mini Program SDK
Error Codes
Harmony SDK
Endpoint SDK Quality Optimization
Security and Compliance
Data Disaster Recovery
Data Security
Cloud Access Management
FAQs
Popular Questions
General
Billing
Domain Name Compliance Issues
Bucket Configuration
Domain Names and CDN
Object Operations
Logging and Monitoring
Permission Management
Data Processing
Data Security
Pre-signed URL Issues
SDKs
Tools
APIs
Agreements
Service Level Agreement
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

Setting CDN Cache Purge

PDF
Modo Foco
Tamanho da Fonte
Última atualização: 2024-10-24 18:44:41

Overview

CDN cache purge is a data purge feature provided by COS based on the SCF service. It can automatically purge the data cached on CDN edge nodes. After you add a trigger rule for a bucket, when a file is updated to the bucket, the SCF function preconfigured by COS will be automatically triggered to purge the cached data.
Note:
If you added a cache purge rule for your bucket in the COS console, the resulting purge function will also appear in the SCF console. Do not delete this function; otherwise, your rule may not take effect.
Regions where SCF is available support CDN cache purge, including Guangzhou, Shanghai, Beijing, Chengdu, Hong Kong (China), Singapore and Silicon Valley. For more supported regions, see Serverless Cloud Function.
CDN cache purge may fail due to factors such as unstable network connection. In these cases, you can click View Log for the function created in the COS console to enter the SCF console and view the error log details for troubleshooting.
The CDN cache purge feature depends on the SCF service, which provides a free tier. Excessive usage will be billed at SCF prices. For more information, see Pricing. For this feature, the more often you purge the cache, the more invocations you will need to use.

Directions

1. Log in to the COS console.
2. Click Bucket List on the left sidebar and click the name of the target bucket.
3. Click Function Service > CDN Cache Purge Function on the left sidebar.


Note:
If you haven't activated SCF, go to the SCF console to activate it and authorize the service as instructed.
4. Click Add Function and configure the following in the pop-up window:


Function Name: It uniquely identifies a function and cannot be modified after being set. You can view the function in the SCF console.
Event Type: An event is an operation that triggers SCF. Take upload as an example. You can initiate an upload by calling the PUT Object or Post Object API. If you select PUT as the event type, only uploads through the PUT Object API can trigger the function to purge the cache on CDN edge nodes.
Trigger Condition: You can specify the file source scope of the triggered files, such as all buckets, specified prefix, or specified suffix. After you specify a prefix or suffix, the rule only applies to the matched file sources.
Specified Domain: Specify the CDN domain name to be purged.
SCF Authorization: CDN cache purge requires authorizing SCF to call the CDN API PurgeUrlsCache. In this way, SCF can replace your CDN cache with the latest data CDN pulls from the COS origin.
5. Click Confirm.
Click Log to view the historical operations of CDN cache purge.
Click Delete to delete an unwanted CDN cache purge rule.

Ajuda e Suporte

Esta página foi útil?

comentários