Context: currently it is not possible to bypass the CDN cache. As a result when a developer works on a new feature or a correction and he wants to check whether his code is satisfying or not, he has to wait for the cache to be refreshed to see the actual result of the change he performed.
It slows down the development process as the cache refresh induces unnecessary waiting times;
Expected result : As a developer, when I want to view the result of a code change, I have the possibility to manually bypass the cache refresh and immediately visualize the outcome of my work.
This bypass could be managed in various ways such as a parameter, a cookie, a key, etc. It simply needs to enable a developer to activate it case by case when he needs it.
Guillaume Lefebvre
Carlos is correct, token can be used to push through delivery cache however it will not impact feature level content source cache when rendering. Note that usage of this parameter is monitored and abuse will result in blocking/removal so please only use it sparingly and not use it within any stress/QA automatic testing which would result in large volumes of requests.
Hi Guillaume, I am also an Arc's customer and I think I experienced the same problem before. If I am right about that, what we do today to bypass the cache is to add a
?token=parameter to the url, has to be specificallytokenwith some random value.You can check it out.