Edge Security Acceleration (ESA) checks parameters contained in user requests based on the rules you created to rewrite URLs, modify request or response headers, and enable managed transform rules for matched user requests.
Features overview
You can create transform rules to configure the features listed in the following table and apply the rules to requests that match a custom filter expression.
If the storage path of your origin resources changes but you want to maintain the URL path that users access, you can rewrite URLs on Edge Security Acceleration (ESA) nodes. This allows you to modify the path and query string (request parameters) in the URL when user requests need to be forwarded to the origin, and use the rewritten URL to request resources from the origin.
HTTP request headers are components of the header section in requests transmitted over HTTP. HTTP request headers provide specific parameters to servers. You can add, remove, modify, and replace HTTP headers in origin requests to meet various business requirements.
An HTTP response header is part of an HTTP response message and carries specific response parameters to pass to clients. By configuring HTTP response headers, Edge Security Acceleration (ESA) nodes include the configured response headers in the response messages when returning resources to clients. This allows you to implement specific features such as cross-origin access.
Add the "ali-real-client-ip" header
You can use the managed transforms feature of Edge Security Acceleration (ESA) to apply common adjustments to HTTP request and response headers.
Availability
Entrance | Pro | Premium | Enterprise | |
Transform rules | 10 | 25 | 50 | 125 |