Mar 2, 2020 — Conditional Origins update and more
almost 5 years ago by kporeba@akamai.com
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.