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

["Miles Libbey (JIRA)" <ji...@apache.org>]

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
            Reporter: Miles Libbey
            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.
-
You can reply to this email to add a comment to the issue online.