[
https://issues.apache.org/jira/browse/TS-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom resolved TS-642.
------------------------------
Resolution: Invalid
So, I've tested this, and I'm fairly positive (well, 99.999% positive) that
setting this setting to 0 does indeed disable HTTP caching.
Note that at startup, if you have configured a cache, it will still report it.
You could for example use the cache for storing your own protocol. This setting
only says to never cache HTTP (which is the only protocol we handle internally).
> Setting proxy.config.http.cache.http to 0 does not turn off caching
> -------------------------------------------------------------------
>
> Key: TS-642
> URL: https://issues.apache.org/jira/browse/TS-642
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache
> Affects Versions: 2.1.6, 2.1.5
> Environment: Debian Linux
> Reporter: Marcus Clyne
> Assignee: Leif Hedstrom
> Fix For: 2.1.7
>
>
> CONFIG proxy.config.http.cache.http INT 0
> does not turn off caching (at least traffic.out says it's enabled).
> I've tested in trunk (2.1.6) as of today and version 2.1.3and 2.1.4.
> I tried both with traffic_cop and traffic_manager and with just
> traffic_server and a notice of caching being enabled was displayed in both
> cases.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
