Release Notes
Security Announcement
Announcements
Rule type | Function | Usage Scenarios | Default Configuration |
Access control | EdgeOne nodes authenticate client access to prevent unauthorized behavior. | Off | |
| Smart acceleration for dynamic resource access requests to improve access speed. | Off | |
Cache configuration | Differentiate node cache content based on the Vary header in the origin response, and respond to corresponding resources based on the specified header content. | Globally disabled by default on the platform | |
| Customize the cache key (Cache Key) of the file in the node to determine the caching rules and whether to hit the cache. | By default, the character cache is not ignored. For details, please refer to the introduction of Cache Key. | |
| Customize the cache time of the file in the node to determine whether the file should be cached in the EdgeOne node and the corresponding cache time. | ||
| Customize the cache time of error status codes in EdgeOne nodes to reduce the pressure of origin-pull requests when the origin is abnormal. | Cache 404 for 10s, other exception status codes are not cached. | |
| Control whether the browser caches files to reduce access request traffic. | By default, follow the origin Cache-Control. | |
| Control whether EdgeOne uses cached files (even if the file has expired) to respond to client requests when the origin is abnormal, ensuring normal service response when the origin is abnormal. | Enable | |
| Let EdgeOne nodes verify the validity of the file before the cache expires, ensuring that the latest resource files are cached in the node. | Off | |
File optimization | EdgeOne nodes perform Gzip compression or Brotil compression to reduce file transmission size. | Enable Gzip compression and Brotil compression | |
Media processing | EdgeOne nodes automatically scale and convert image formats, eliminating the need for multiple sizes and formats of image copies on the origin, reducing image storage costs. | Off | |
Network optimization | Require EdgeOne nodes to support HTTP/2 access. | Enable | |
| Require EdgeOne nodes to support HTTP/3 access. | Off | |
| Require EdgeOne nodes to support IPv6 access. | Off | |
| EdgeOne nodes limit the maximum file size that users can upload to prevent malicious uploads of large files and reduce transmission traffic. | Enable, maximum limit of 800MB | |
| Require EdgeOne nodes to support WebSocket transmission and configure timeout connection duration. | Off | |
| Specify the request header to carry the client IP when EdgeOne nodes origin-pull. | Off | |
| Specify the request header to carry the client IP geographic location when EdgeOne nodes origin-pull. | Off | |
| Require EdgeOne nodes to support gRPC access. | Off | |
URL Rewrite | Customize the redirection of the user's access URL address. | N/A | |
| Customize the redirection of the user's origin-pull request URL address. | N/A | |
Modify headers | Customize the modification of HTTP headers carried by EdgeOne nodes when responding to user requests. | N/A | |
| Customize the modification of HTTP headers carried by EdgeOne nodes when origin-pulling. | N/A | |
| Customize the modification of the error page displayed to the client when the origin responds with 4xx and 5xx status codes. | N/A | |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback