[
https://issues.apache.org/jira/browse/TS-4751?focusedWorklogId=26405&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-26405
]
ASF GitHub Bot logged work on TS-4751:
--------------------------------------
Author: ASF GitHub Bot
Created on: 12/Aug/16 23:22
Start Date: 12/Aug/16 23:22
Worklog Time Spent: 10m
Work Description: Github user jpeach commented on the issue:
https://github.com/apache/trafficserver/pull/864
I guess the key phrase from RFC 2616 is ``if the field-value might differ
from that sent in any previous response``. What happens if the origin had an
``Expires`` but not it doesn't? RFC7232 would say that we MUST not use the
``Expires`` we have, but RFC2616 says we should. I think this could easily
happen with an origin server configuration change.
Issue Time Tracking
-------------------
Worklog Id: (was: 26405)
Time Spent: 1h (was: 50m)
> 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
> 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)
