mitchell852 edited a comment on issue #7322: URL: https://github.com/apache/trafficserver/issues/7322#issuecomment-726919791
Here is what we are experiencing: ``` Path: /opt/trafficserver/etc/trafficserver/regex_revalidate.config http://my.origin.net/foo.png 1606758714 <-- this rule was created on 11/13 with an expiration (TTL) of 11/30 (the invalidation may occur at anytime betwen 11/13 - 11/30) http://my.origin.net/foo.png 1606845114 <-- this rule was created because the user needed to invalidate foo.png AGAIN...but it is blocked until 11/30 due to rule #1 ``` Since we don't really know when the invalidation for rule #1 occurs, we leave that rule in until it expires (11/30)....which basically blocks subsequent rules... If the ATS regex reval plugin considers the last rule to be the winner (instead of the first), the last rule would be loaded and the content invalidation would be reset (because it is different based on expiration date/epoch) allowing users to create additional rules for the same regex. More than anything, the first/last thing is not a big deal, it's the immutable part. I would expect ATS to say "hey, look this rule changed as it has a different epoch. let me start over and respect the new rule". ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
