[jira] [Resolved] (TS-304) TS Doesn't treat badly formatted Expires as stale

["Leif Hedstrom (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom resolved TS-304.
------------------------------

    Resolution: Won't Fix

This bug doesn't make a whole lot of sense. I know we have a few issues around specific Expires problems (as reported by Coadvisor), but we'll file separate, more descriptive bugs for that.

Note that the current code does treat Date "parse errors" as if the Expires header was set to zero.

> TS Doesn't treat badly formatted Expires as stale
> -------------------------------------------------
>
>                 Key: TS-304
>                 URL: https://issues.apache.org/jira/browse/TS-304
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: HTTP
>            Reporter: Miles Libbey
>            Assignee: Leif Hedstrom
>            Priority: Minor
>
> (moved from yahoo bug 784579)
> Original description
> by Vladimir Legalov  3 years ago at 2006-08-23 21:27
> Ill-formatted Expires header values should be treated as being in the past, so that any mistakes will have the
> appropriate effect. TS treats these as if the Expires header wasn't there, assigning a heuristic freshness to the
> responses. The safe thing to do would be to consider it stale.
> From RFC2616:
> HTTP/1.1 clients and caches MUST treat other invalid date formats, 
> especially including the value "0", as in the past (i.e., "already 
> expired").
> 		
> Comment 1
>  by Leif Hedstrom  3 years ago at 2006-08-24 07:18:24
> I don't think this is particularly "critical" for us, since we have control of all Origin servers. Ryan's
> "Origin verification" tool also warns about bad Expire headers. Not saying we shouldn't fix this, but it's
> low priority IMO.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira