[jira] [Updated] (TS-2080) Remove arbitrary 1 year max cache freshness limit
[
https://issues.apache.org/jira/browse/TS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2080:
--
Labels: compatibility (was: )
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)
[jira] [Updated] (TS-2080) Remove arbitrary 1 year max cache freshness limit
[
https://issues.apache.org/jira/browse/TS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-2080:
---
Assignee: Leif Hedstrom
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
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)
[jira] [Updated] (TS-2080) Remove arbitrary 1 year max cache freshness limit
[
https://issues.apache.org/jira/browse/TS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Susan Hinrichs updated TS-2080:
---
Fix Version/s: (was: sometime)
6.0.0
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
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)
[jira] [Updated] (TS-2080) Remove arbitrary 1 year max cache freshness limit
[
https://issues.apache.org/jira/browse/TS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Call updated TS-2080:
---
Fix Version/s: (was: 5.0.0)
sometime
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
Fix For: sometime
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.2#6252)
[jira] [Updated] (TS-2080) Remove arbitrary 1 year max cache freshness limit
[
https://issues.apache.org/jira/browse/TS-2080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-2080:
--
Fix Version/s: 3.5.0
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
Fix For: 3.5.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 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
