[GitHub] [trafficserver] rob05c opened a new issue #7701: When rewriting cache.config in YAML, make it not additive.

[GitBox <gi...@apache.org>]

rob05c opened a new issue #7701:
URL: https://github.com/apache/trafficserver/issues/7701


   cache.config is currently additive.
   
   > When multiple rules are specified in cache.config, Traffic Server will check all of them in order for each request. Thus, two rules which match the same request but have conflicting actions will result in their actions being compounded. In other words, Traffic Server does not stop on the first match.
   
   This is highly unintuitive and unexpected. Furthermore, because the match logic isn't very powerful, it's not possible to do certain things.
   
    I'm making this issue as a placeholder so we don't forget: when we rewrite it in YAML, we should make it not additive, or possibly extend the matching capabilities to be more powerful, so things like `suffix=jpeg` and `suffix!=jpeg` are possible, or possibly both.


-- 
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

[GitHub] [trafficserver] rob05c commented on issue #7701: When rewriting cache.config in YAML, make it not additive.

[GitBox <gi...@apache.org>]

rob05c commented on issue #7701:
URL: https://github.com/apache/trafficserver/issues/7701#issuecomment-818269721


   See https://github.com/apache/trafficserver/issues/1329


-- 
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