April 2020 Release

This next release of EdgeWorkers uniquely combines the power of Serverless functions and the Akamai Edge; the April release adds powerful features to improve cached delivery and offload, as well as other features to ensure fast and accurate coding from design to production.

New CDN Integration

• Change URL and Origin Support.  You can now modify both the path and query arguments for a request, and determine which origin the request should be directed to. Combined, these features provide unique opportunities to change the user experience including: device personalization without redirects, image optimization for device and browser, origin load balancing, A/B testing using cached content, and controlled rollout of new applications.

For more details see the User Guide>Development>JavaScript Object reference>Request Object>Methods for the Request Object>route(destination)

• Control Cache Keys.  To optimize cached delivery, you can now programmatically define cache keys. Cache keys are used to determine unique cached content; typically a combination of the URL, query arguments, cookies, headers, or custom variables. Optimizing keys ensures the correct cached content is delivered, and improves offload and performance. A simple example is removing specific query arguments from the cache keys, so that random debug values don’t bust caching in production. Another example is modifying the key to leverage A/B testing cookies, ensuring A or B variant of cached content is delivered for the same URL.

For more details see the User Guide>Development>JavaScript Object reference>cacheKey Object

Improvements to the Developer Workflow

• TypeScript Bindings.  We’ve published TypeScript bindings to the EdgeWorkers JavaScript API. TypeScript provides useful IDE integrations for faster and more accurate coding, preventing bugs found late in the release cycle.

See this blog post for more information.

• Failover Integration.  The new failover integration enables you to provide an alternative action when an EdgeWorker function fails (for whatever reason). You can specify content to be served in place of the error status code as a redirect or new request (even to another origin).

See the User Guide for more details.

• Sandbox Integration.  To help developers deploy and test code changes with Akamai-in-the-middle, without impacting other teams, Akamai Sandbox integration enables fast testing.

For more details see the User Guide>Test EdgeWorkers with the Sandbox CLI

Fixes

• Timeout Issues: We’ve modified the timeouts to avoid failures on first use due to code bundles taking too long to download and compile

The latest version of Adaptive Acceleration includes the following new features and bug fix for Resource Optimizer:

• Resource Optimizer now supports the compression of SVG resources. 
• Resource Optimizer now supports the smart optimization of URLs that display cache busting behavior. This results in a more effective and timely optimization of resources. Resource Optimizer now optimizes a maximum of two instances of the same URL with different cache query parameters within any 24 hour window. After 24 hours has passed, Resource Optimizer optimizes the same URL again with different query parameters. 
• Resource Optimizer now supports purge by cache tag. 

Bug fix:

• Unoptimized resources are no longer cached with the original resource Time to Live (TTL). This prevented Resource Optimizer from optimizing resources the first time Resource Optimizer was applied. 

The latest update to mPulse includes an enhancement that improves bot detection and classification capabilities. Learn more about the Integration with Bot Manager.

General Updates

Cloudlets Origins are now called Conditional Origins in Property Manager. For example, the Cloudlets Origin Definition behavior is now the Conditional Origin Definition behavior.

Enhancements

• Activations. The Audience Segmentation, Edge Redirector, Forward Rewrite, and Input Validation Cloudlets now have:
  • Faster activation times. Most policy activations for these Cloudlets are live on the network in less than 15 minutes. Activations that impact more than 50 properties won’t see these improvements. The next version of the Cloudlets API will address this issue.
  • Faster response times. An activation request from these Cloudlets may receive a response in under two seconds. The next version of the API will extend the faster response times to all Cloudlets.

• Chrome v80 update. Cloudlets now support Chrome’s secure-by-default cookie model. Going forward, cookies created by Cloudlets will have HttpOnly, SameSite, and Secure attributes set correctly for HTTP and HTTPS clients.

• Custom header support for Application Load Balancer liveness tests. Liveness tests for Application Load Balancer now support custom HTTP headers. If you use a custom header in your load balancing configuration, all liveness requests sent to your data centers will include the custom header value.

Bug Fixes

• Cloudlets Origin IDs. Previously, you couldn’t have a Cloudlets Origin ID that was all numbers. This release fixes this issue.
• Application Load Balancer failover requests. In some cases, Application Load Balancer sent requests to a downed data center before failing over to a second data center.
• Application Load Balancer failover assignment. If Requests before Origin Stickiness Reassignment was set to 1, Application Load Balancer didn’t reassign clients back to original data center.
• Invalid CSV characters. The Edge Redirector CSV download function added invalid characters to regular expressions.

Script Management Updates

• Renamed the Go To Testing button to Test suggestions and added it to the Dashboard to enable direct access to the functionality. 
• The transfer size of scripts now displays as KBs if the size is greater than 1024 bytes. 

The latest update for API Gateway includes the following features, enhancements, and bug fixes:

New Features:

• Easily configure inbound and outbound traffic paths and routing with Origin Routing.
• “What’s New” section in Luna displays information about new features as they become available.
• HTTP methods now have 3 states to more clearly indicate status: inactive, activated on production, or activated on staging.
• HTTP methods are now color-coded to indicate which method(s) are selected.
• You will now be notified through a pop-up window when a Gateway policy has been successfully activated on the network.
• The access control group (ACG) for every key collection will now be displayed.
• You may now use a key collection (instead of an individual key) to enable the Gateway throttling feature.

Enhancements:

• Endpoints may no longer be activated without a defined hostname.
• Very long resource paths are now always visible in the UI.
• API Gateway will now honor cache settings as configured in Property Manager, unless caching is also configured in API Gateway. If configured in API Gateway, the Gateway settings override the Property Manager settings.

Bug fixes:

• Reimporting an API in API Definitions inadvertently replaced existing hostnames.
• Swagger import was failing for some use cases.
• Endpoint activation issues have been resolved.
• Fixed a problem where selecting too many methods resulted in a request being denied.
• Fixed a problem with the X-Throttling-Limit HTTP header to ensure it will always be sent to the client.

The latest update to mPulse includes the following features:

• mPulse Enterprise customers can now designate apps as “Lite” apps for specific properties. Find out more about Lite Apps for Enterprise Tenants.
• Automatic Page Groups (APG) uses URL regular expressions to automatically create logical page groups for new mPulse apps. Learn more about Automatic Page Groups.

The latest update to mPulse includes the following enhancements:

• The mPulse Query API ‘metrics-by-dimension’ query type now supports custom dimensions as inputs to the ‘dimension’ parameter.
• Added support for Edge Mobile on iOS and Android.

The latest update to mPulse includes the following bug fixes:

• Fixed an issue that caused SVG dimension errors to appear in the console when timing data for a resource had a negative value.
• Fixed an issue of mPulse failing to collect beacons that contained a dash in their AMP Session ID.
• Fixed an issue where mPulse was not detecting changes to custom metric definitions.
• Fixed an issue where dimension values were not appearing correctly in filtered search results.
• Fixed an issue related to the breakdown of data for regions within a country.
• Fixed an issue that caused charts to appear distorted when resized.

The latest update to mPulse resolves an issue that caused alerts to be delayed and/or misfired in some cases.

New features:

• Liveness tests with many headers. You can define multiple HTTP headers for any HTTP(S) liveness test configuration using the API and user interface.

• Disable liveness tests. You can use the API or a checkbox in the user interface to disable a liveness test, which directs the GTM service to cease running the test and effectively treat the test as no longer existing.

• Static property types. You can use the API to configure static answers, such as an A record value for GTM properties, to deliver static record responses.

• Apex properties. You can configure properties at the apex record of a domain, which eliminates the need to create a subdomain of a GTM domain with only one property. The API and user interface display the apex record with an @ symbol.

• Terraform Provider. You can use Terraform Provider to minimize the activity required to manage and configure GTM domains and properties.

With the latest update to mPulse, metrics that had been displayed as 9,999% will now correctly appear as 9.999%.