You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2019/06/27 19:20:25 UTC

[GitHub] [trafficcontrol] ocket8888 opened a new issue #3702: Reval max days chosen at random

ocket8888 opened a new issue #3702: Reval max days chosen at random
URL: https://github.com/apache/trafficcontrol/issues/3702
 
 
   The ``maxRevalDurationDays`` parameter is currently chosen by the `regex_revalidate.config` generation process at random from the set of all Parameters with the name `maxRevalDurationDays` and the Config File `regex_revalidate.config`. If, for example, a user assumes that assigning this to a Delivery Service Profile will cause it to be enforced on that Delivery Service only, they will inadvertently set a different `maxRevalDurationDays` value that will compete with the original every time a `regex_revalidate.config` file is generated.
   
   At first glance it may seem like all that's needed is to check specifically for the Parameter on the GLOBAL Profile, but there's no reason (as far as I know) two or more Parameters with the same Config File and Name but different Values can't be assigned to the same Profile.
   
   This is *not* a regression from Perl, which had the same problem.

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services