tencent cloud

Tencent Cloud EdgeOne

Release Notes and Announcements
Release Notes
Security Announcement
Announcements
Product Introduction
Overview
Strengths
Use Cases
Comparison Between EdgeOne and CDN Products
Use Limits
Purchase Guide
Description of Trial Plan Experience Benefits
Free Plan Guide
Billing Overview
Billing Items
Subscriptions
Renewals
Instructions for overdue and refunds
Comparison of EdgeOne Plans
About "clean traffic" billing instructions
DDoS Protection Capacity Description
Getting Started
Choose business scenario
Quick access to website security acceleration
Quick deploying a website with Pages
Domain Service&Origin Configuration
Domain Service
HTTPS Certificate
Origin Configuration
Site Acceleration
Overview
Access Control
Smart Acceleration
Cache Configuration
File Optimization
Network Optimization
URL Rewrite
Modifying Header
Modify the response content
Rule Engine
Image&Video Processing
Speed limit for single connection download
DDoS & Web Protection
Overview
DDoS Protection
Web Protection
Bot Management
API Discovery(Beta)
Edge Functions
Overview
Getting Started
Operation Guide
Runtime APIs
Sample Functions
Best Practices
Pages
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
Data Analysis&Log Service
Log Service
Data Analysis
Alarm Service
Site and Billing Management
Billing Management
Site Management
Version Management
General Policy
General Reference
Configuration Syntax
Request and Response Actions
Country/region and Corresponding Codes
Terraform
Overview
Installing and Configuring Terraform
Practical Tutorial
Automatic Warm-up/Cache Purge
Resource Abuse/hotlinking Protection Practical
HTTPS Related Practices
Acceleration Optimization
Scheduling Traffic
Data Analysis and Alerting
Log Platform Integration Practices
Configuring Origin Servers for Cloud Object Storage (Such As COS)
CORS Response Configuration
API Documentation
History
Introduction
API Category
Making API Requests
Site APIs
Acceleration Domain Management APIs
Site Acceleration Configuration APIs
Edge Function APIs
Alias Domain APIs
Security Configuration APIs
Layer 4 Application Proxy APIs
Content Management APIs
Data Analysis APIs
Log Service APIs
Billing APIs
Certificate APIs
Origin Protection APIs
Load Balancing APIs
Diagnostic Tool APIs
Custom Response Page APIs
API Security APIs
DNS Record APIs
Content Identifier APIs
Legacy APIs
Ownership APIs
Image and Video Processing APIs
Multi-Channel Security Gateway APIs
Version Management APIs
Data Types
Error Codes
FAQs
Product Features FAQs
DNS Record FAQs
Domain Configuration FAQs
Site Acceleration FAQs
Data and Log FAQs
Security Protection-related Queries
Origin Configuration FAQs
Troubleshooting
Reference for Abnormal Status Codes
Troubleshooting Guide for EdgeOne 4XX/5XX Status Codes
520/524 Status Code Troubleshooting Guide
521/522 Status Code Troubleshooting Guide
Tool Guide
Agreements
Service Level Agreement
Origin Protection Enablement Conditions of Use
TEO Policy
Privacy Policy
Data Processing And Security Agreement
Contact Us
Glossary

HTTP Response

PDF
Focus Mode
Font Size
Last updated: 2025-07-29 15:19:21

Overview

The HTTP response feature is supported by the rule engine. When the corresponding conditions are matched, the EdgeOne node directly responds with the specified status code and page content.


Feature Description

Response status code: supports 2XX, 4XX, and 5XX, excluding 499, 514, 101, 301, 302, 303, 509, and 520-599.
Response page: supports the Content-Type options including text/html, application/json, text/plain, and text/xml.

Use Cases

The following are some common use cases for HTTP responses:
Configuring the Flash cross-domain policy file: The crossdomain.xml file is used to specify the domain names or IP addresses that can access the website resources.
Basic access control: such as IP allowlist/blocklist, Referer allowlist/blocklist, UA allowlist/blocklist, and region access control.
Temporary maintenance or activity page: When the website is under temporary maintenance or hosting specific activities, the HTTP response feature can be used to guide users to the maintenance notification page or activity page, thereby enhancing user experience.

Preparations

Go to the Custom Response Page to create a necessary custom page for the HTTP response action.

Scenario 1: The Domain Name Requires Configuring the crossdomain.xml File

If your business at the www.example.com domain name under the example.com site needs to control cross-domain access through the crossdomain.xml file, you can refer to the following steps:
1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. On the site details page, click Site Acceleration to enter the global site configuration page. Then click Network Optimization in the right sidebar.
3. On the site details page, click Site Acceleration to enter the global configuration page. Then click the Rule Engine tab.
4. On the rule engine page, click Create rule and select Add blank rule.
5. On the rule editing page, select the matching type as HOST and set its value to equal www.example.com.
6. Click the choice box below Action and select the action as HTTP Response in the pop-up action list.
7. Configure the response status code to 200 and select the created crossdomain.xml file from the dropdown list for the response page.
8. The complete rule configuration is shown below. Click Save and publish to finish the rule configuration.


Scenario 2: The Domain Name Requires Configuring a Referer Allowlist

If your business at the www.example.com domain name under the example.com site only allows access by requests with https://www.example.com/ as Referer, and directly denies other requests with 403, you can refer to the following steps:
1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. On the site details page, click Site Acceleration to enter the global configuration page. Then click the Rule Engine tab.
3. On the rule engine page, click Create rule and select Add blank rule.
4. On the rule editing page, select the matching type as HOST and set its value to equal www.example.com. Additionally, select the matching type as HTTP Request Header, select the header name as Referer, and set the header value to equal https://www.example.com/.
5. Click the choice box below Action and select the action as HTTP Response in the pop-up action list.
6. Configure the response status code to 403 and select the response page from the dropdown list. If no page is available, click Create page to create a page first and then reference it.
7. The complete rule configuration is shown below. Click Save and publish to finish the rule configuration.


Scenario 3: The Domain Name Requires Configuring a UA Blocklist

The resources of your business at the www.example.com domain name under the example.com site are maliciously crawled by Google crawlers, causing a sudden bandwidth increase of the domain name and severely affecting the bills. Through analysis, it is found that the crawler requests contain spider in the User-Agent. To block such requests, you can refer to the following steps:
1. Log in to the Tencent Cloud EdgeOne console, enter Service Overview in the left menu bar, and click the site to be configured under Website Security Acceleration.
2. On the site details page, click Site Acceleration to enter the global configuration page. Then click the Rule Engine tab.
3. On the rule engine page, click Create rule and select Add blank rule.
4. On the rule editing page, select the matching type as HOST and set its value to equal www.example.com. Additionally, select the matching type as HTTP Request Header, select the header name as User-Agent, and set the header value to match the regular expression *spider*.
5. Click the choice box below Action and select the action as HTTP Response in the pop-up action list.
6. Configure the response status code to 403 and select the response page from the dropdown list. If no page is available, click Create page to create a page first and then reference it.
7. The complete rule configuration is shown below. Click Save and publish to finish the rule configuration.



Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback