Transform rules match requests by specific parameters to rewrite URLs, modify headers, or apply managed transforms.
Rule types
Feature | Description |
Configure URL rewrite rules on ESA edge nodes to modify the request path and query string during origin requests. Migrate origin server paths without changing user-facing URLs or frontend configurations. | |
Add, modify, or delete specific incoming request headers at the edge to control what your backend receives—for example, injecting Accept-Encoding or Accept-Language headers to customize visitor experiences and track usage behavior. | |
Configure rules to add, modify, or delete HTTP headers in origin requests sent from ESA points of presence (POPs) to your origin server. | |
You can modify, delete, or add response headers from an origin server to ESA, such as Cache-Control and Expires. By controlling these headers, you can optimize cache behavior, enhance security, and customize the client experience. | |
Outbound response headers from Edge Security Acceleration (ESA) nodes are part of the HTTP response headers sent to clients. By configuring outbound response headers in ESA, you can control the headers that are returned with resources. ESA lets you add, modify, and delete outbound response header rules to meet specific business requirements. | |
The Edge Security Acceleration (ESA) managed transform feature automatically adds headers to origin requests to record information such as the real client IP, geolocation, and TLS fingerprint. This feature can also add standard security headers to client responses, which simplifies configuring common request and security headers. |
Edition quotas
Transform rules | Entrance | Pro | Premium | Enterprise |
Transform rules | 10 | 50 | 75 | 125 |