You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2013/07/29 01:41:48 UTC

[jira] [Created] (TS-2080) Remove arbitrary 1 year max cache freshness limit

Leif Hedstrom created TS-2080:
---------------------------------

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


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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira