Through traffic control we have the limited ability for CDN customers to add
revalidation requests. Unfortunately there are times when assets need to be
revalidated multiple times due to whatever reason.
The way regex_revalidate works now it is first rule wins, meaning that once a
rule (regex)
Sounds reasonable to me.
Unless, it breaks some backward compatibility that can't be worked around, it
feels that this behavior can be made the default (without any need of a config
even).
Thanks!
Sudheer
On Friday, November 13, 2020, 08:38:43 AM PST, Olsen, Brian
wrote:
Through traff
1. Two-character string substitutions can begin with ^ as well as $. If ^
is used, and the substitution is a URL component, the component will be the
one in the pristine, rather than the remapped, URL. So, for example, $h is
the host in the remapped URL, and ^h is the host in the pristine URL.
For safety's sake it might be best to take the rule expiration that's furthest
away (including any already loaded rules) and reset the activation/epoch.
On 11/13/20, 10:03 AM, "Sudheer Vinukonda"
wrote:
Sounds reasonable to me.
Unless, it breaks some backward compatibility that can't
Never mind that's too hard to keep track of. The idea here is that if a new
regex_revalidate rule comes in with the same regex as an active but a different
expiration time it should act as though a new rule came in.
On 11/13/20, 11:59 AM, "Olsen, Brian" wrote:
For safety's sake it might
