The Monitoring section now includes a table that summarizes each of the options available to help you gain insight about the performance of your EdgeWorkers functions. This overview can help you, for example, decide if you want to deliver JavaScript logs via Enhanced debug headers or a DataStream 2 stream.

If validation fails when activating an EdgeWorker version, details about the error are now provided in the UI.

Flexible composition lets you create and deploy multiple EdgeWorkers for the same website. You can enable dynamic reactivation when you activate a parent EdgeWorker by disabling the auto pin option.

The getHeaders() method for the Response Object is now available to return a JavaScript object that contains all HTTP response headers as properties. You can use the getHeaders() method on the onOrigin Response and onClient Response event handlers.

The EdgeWorkers event handlers now support the OPTIONS HTTP method. To use the OPTIONS method you need to add the PMUSER_EW_ENABLE_OPTIONS variable to your rule and set the value to true. The name of the variable must be UPPERCASE.

The request object now supports the clientIp property. You can use it to get the original client IP address that can be either IPv4 or IPv6.

Flexible composition is now available to use without having to join the Beta program.

You can now use a DataStream 2 stream to deliver JavaScript logs to an external endpoint. You can also set the log-levels for the logs sent via DataStream 2.

You can now use subWorkers to make HTTP requests to EdgeWorkers on different properties or different accounts.

You can now configure an EdgeWorkers function to execute via an ESI (Edge Side Includes) fragment request on the enhanced TLS network.