<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I finally realize my Age method is vulnerable to clock skew as it is
calculated from the upstream Date. There seems to be no way to get
the date/time that the original request was made to the origin. The
closest is the cached file's mtime, but this represents the time
that the request finished, not the start.<br>
<br>
On 2010-06-09 1:47 PM, Woon Wai Keen wrote:
<blockquote cite="mid:4C0F2AFE.9090906@doubleukay.com" type="cite">Hi
all, I would like to contribute a patch to provide the cached file
age as a variable $proxy_cache_age , which can then be used
together with add_header Age $proxy_cache_age.
<br>
<br>
The age calculation is not RFC2616 compliant (13.2.3) as it
doesn't take into consideration the cached origin Age header and
Date. Is it feasible to extract this from the cached headers?
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
nginx-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:nginx-devel@nginx.org">nginx-devel@nginx.org</a>
<a class="moz-txt-link-freetext" href="http://nginx.org/mailman/listinfo/nginx-devel">http://nginx.org/mailman/listinfo/nginx-devel</a>
</pre>
</blockquote>
<br>
</body>
</html>