The EdgeWorkers event model contains "hooks" that can be called at specific points throughout the end user request-response workflow. Each event has specific features and capabilities that allow it to transform and modify the request and response as it flows through the Intelligent Edge Platform.
Metadata actions are performed during the stages where EdgeWorkers events are defined. EdgeWorkers functions do not alter the execution order from the metadata stage or from a top-to-bottom perspective. You can think of EdgeWorkers as a different way to produce a metadata equivalent.
Let’s review the order in which actions are applied when manipulating a response header that includes:
- An Edge Side Includes (ESI) add_header()
- The EdgeWorkers response.setHeader() in the onClientResponse event
- The Property Manager Modify Outgoing Response Header behavior
EdgeWorkers and Property Manager are different interfaces that result in the same proxy task.
- EdgeWorkers and Property Manager both perform header manipulation. They provide different interfaces that can achieve the same results. This means both default to the general rule of thumb that whichever behavior is encountered last in the delivery property wins.
- In this scenario, the EdgeWorkers or Property Manager header behavior that happens last will not see what the previous behavior did. It is a stateless change that gets confirmed at the end of the metadata stage.
- ESI is processed on the last proxy before the client, in nearly the last metadata stage. An EdgeWorkers function will not apply after ESI is processed because the EdgeWorkers job is complete at that point.
Security products tend to run prior to delivery features. EdgeWorkers live inside the delivery block of feature applications, so they would typically happen after security features.
No, daisy chaining is not allowed at this time. Only one EdgeWorkers function, the last one configured in the delivery property for a given request or response, can apply.
Updated over 1 year ago