You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by GitBox <gi...@apache.org> on 2021/04/12 21:55:21 UTC

[GitHub] [trafficserver] rob05c commented on issue #1329: action=never-cache did NOT take effect in cache.config

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


   This is working as documented: https://docs.trafficserver.apache.org/en/7.1.x/admin-guide/files/cache.config.en.html#matching-multiple-rules
   
   > 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.
   
   And we can't change the current behavior, or we'd break people.
   
   I think we all agree the behavior is highly unintuitive. We're planning to rewrite all configs in YAML. When we rewrite cache.config in YAML, we should make that design not additive, or somehow more intuitive.


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