Can you confirm how long does the transition (activation) take from Fast Invalidate to Fast Purge?
And just to be sure I understand correctly - After activation, we can still continue to use CCU v2 API/UI functionality?
It takes a few seconds to transition, assuming the customer is not using *.akadns.net as any origin hostname on the account. Both the legacy CCU UI and legacy CCU API versions can be used in parallel. Who is the customer?
Hope everything is fine with you.
We have already noticed that the Fast Purge feature was already enabled in some of our customers.
But we have this Menu “Fast Purge Transition” which has a button to change between Queuing CCU and Fast Purge and I have a doubt:
Should the customers turn that button to ON only when they have changed to the CCU API V3 ?
Have I understood it correctly ?
The button only impacts CCU V3 API, and no other version of the API. It does not matter if the customer toggles the button before or after integrating with the API.
Thanks for your reply Jeff!
A quick question:
In one of the posts above, you have written that the transition to Fast Purge takes a few seconds “assuming the customer is not using *.akadns.net as any origin hostname on the account”.
So, what’s the caveat, if there is one, if the customer is using *.akadns.net as any origin hostname ?
As of today there are no issues with Fast Purge when working in conjunction with *.akadns.net origins.
Thank you very much Marco!
I came across another issue using Purge API with Forward Rewrite Cloudlet, where the urls in Forward Rewrite had to be configured with http even if the app is only on https. Instead of the matching regex criteria exclusively using https, we had to update it to be https?, since the purge is submitted as http only.
Retrieving data ...