Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-2080

Remove arbitrary 1 year max cache freshness limit

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 6.0.0
    • Cache

    Description

      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:

        max_freshness_bounds = min((MgmtInt)NUM_SECONDS_IN_ONE_YEAR, s->txn_conf->cache_guaranteed_max_lifetime);
      

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

        {RECT_CONFIG, "proxy.config.http.cache.guaranteed_max_lifetime", RECD_INT, "31536000", RECU_DYNAMIC, RR_NULL, RECC_NULL, NULL, RECA_NULL}
      

      Attachments

        Activity

          People

            zwoop Leif Hedstrom
            zwoop Leif Hedstrom
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: