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 2010/11/10 19:46:18 UTC
[jira] Updated: (TS-483) Should we return cached Date: header to UA
?
[ https://issues.apache.org/jira/browse/TS-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Leif Hedstrom updated TS-483:
-----------------------------
Fix Version/s: (was: 3.1)
2.1.5
> Should we return cached Date: header to UA ?
> --------------------------------------------
>
> Key: TS-483
> URL: https://issues.apache.org/jira/browse/TS-483
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP
> Reporter: Leif Hedstrom
> Fix For: 2.1.5
>
> Attachments: TS-483.diff
>
>
> Right now, we cache the Date: header from the origin server, and upon cache hits, we return this cached Date: header to the UA as well. It seems most proxy caches will return the current date from the server itself as the Date: header. I'm suggesting we make it configurable (records.config) to send either the current proxy server date as the Date: header, or the cached Date: header.
> This could obviously be done as a plugin, but I think it'd be a useful built-in feature to have. I remember Souders complained about the fact that we use the cached Date: header, but that the RFC was unspecified in this regard (maybe the BIS will address this).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.