[
https://issues.apache.org/jira/browse/TS-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793401#comment-13793401
]
Leif Hedstrom commented on TS-2189:
-----------------------------------
I'm wondering if this is a misunderstanding / undocumented problem. As far as I
can tell, this configuration does exactly what it says; it'll force all
requests to be cached locally. You probably almost never want to enable this in
records.config, but instead via conf_remap.so (remap plugin) or a custom
plugin, and enable it per remap rule or per transaction.
This stems from the fact that cache.config behavior can not be modified per
remap rule or from a plugin API, so I think they added this records.config.
Basically, this is an alternative way to configure this behavior, outside of
cache.config.
We really ought to document this, so I'm going to move this to a documentation
bug.
> enabling proxy.config.http.cache.cluster_cache_local causes all traffic to
> store local
> --------------------------------------------------------------------------------------
>
> Key: TS-2189
> URL: https://issues.apache.org/jira/browse/TS-2189
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache, Clustering, Documentation
> Reporter: Scott Harris
> Fix For: Docs
>
>
> Setting proxy.config.http.cache.cluster_cache_local=1 is causing all requests
> to cache locally and not work in cluster mode.
> cache.config contains no rules so nothing should be caching locally.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
