[
https://issues.apache.org/jira/browse/TS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14553489#comment-14553489
]
ASF subversion and git services commented on TS-2080:
-----------------------------------------------------
Commit bdca37f0edef7a0b7e5043ea890528d09fcd77c2 in trafficserver's branch
refs/heads/master from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=bdca37f ]
TS-2080 Remove arbitrary 1 year max age limit on the cache, use configuration
option
> Remove arbitrary 1 year max cache freshness limit
> -------------------------------------------------
>
> Key: TS-2080
> URL: https://issues.apache.org/jira/browse/TS-2080
> Project: Traffic Server
> Issue Type: Improvement
> Components: Cache
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Labels: compatibility
> Fix For: 6.0.0
>
>
> For some reason (maybe john know's ?) we have an upper limit on cache
> freshness at 1 year. I have no idea why this is, the only place it's used is
> in HttpTransact.cc:
> {code}
> max_freshness_bounds = min((MgmtInt)NUM_SECONDS_IN_ONE_YEAR,
> s->txn_conf->cache_guaranteed_max_lifetime);
> {code}
> Begs the question, why not just remove the min(), and always use the
> cache_guranteed_max_lifetime? This is a records.config setting, defaults to a
> 1 year (go figure).
> {code}
> {RECT_CONFIG, "proxy.config.http.cache.guaranteed_max_lifetime", RECD_INT,
> "31536000", RECU_DYNAMIC, RR_NULL, RECC_NULL, NULL, RECA_NULL}
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
