[
https://issues.apache.org/jira/browse/TS-4751?focusedWorklogId=26432&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26432
]
ASF GitHub Bot logged work on TS-4751:
--------------------------------------
Author: ASF GitHub Bot
Created on: 15/Aug/16 15:46
Start Date: 15/Aug/16 15:46
Worklog Time Spent: 10m
Work Description: Github user jpeach commented on the issue:
https://github.com/apache/trafficserver/pull/864
The problem we hit was we had a bogus Age (12000) header cached. Since the
origin was no linger sending an Age header, the object would never become fresh.
One common case could be an origin that sends Expires, then is reconfigured
to not send Expires. In this case, we would always keep the Expires from the
cached header which would be wrong.
Issue Time Tracking
-------------------
Worklog Id: (was: 26432)
Time Spent: 1h 20m (was: 1h 10m)
> revalidation can skip updating the Age header
> ---------------------------------------------
>
> Key: TS-4751
> URL: https://issues.apache.org/jira/browse/TS-4751
> Project: Traffic Server
> Issue Type: Bug
> Components: Cache, Core
> Reporter: James Peach
> Assignee: James Peach
> Fix For: 7.0.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> In {{HttpTransact::merge_and_update_headers_for_cache_update}}, the cached
> {{Age}} header is only updated if the server response also contains an
> {{Age}} header. If the revalidation response does not contain an {{Age}}, we
> will retain the cache {{Age}} header which makes the document permanently
> stale, causing a revalidation on every request.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
