Changelog

The EdgeWorkers reports now provide improved data accuracy and the following filters.

The onBotSegmentAvailable event lets you inspect the bot status assigned to the request by Bot Manager. You can only use this event handler if your property is configured to use Bot Manager Premier.

The maximum size of the response status and header for responses generated using createResponse() is now 16 K. This increase provides additional header flexibility when building your edge applications.

Limits no longer apply to the maximum body size in the following cases:

You can now use the Continue on error behavior to let requests continue processing to the next step even if an EdgeWorkers event handler fails.

You can now request an increase to a total of 4000 characters for all of your Property Manager user-defined variables. Contact your Akamai representative to make these changes to your account.

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.