> generated at the origin server.  THIS IS GOOD.  THIS IS INTENTIONAL.
> response as stale, which can cause extra revalidation messages.
is to provide a reliable estimate regardless of clock synchronization.
> Age header if the response comes from its own cache.
> to the wrong time zone, and it's an hour slow.
> of its cache entry for perhaps a significant amount of time.
when any old cache is present, and never occurring once people upgrade.
we can design the protocol to allow them to operate in this situation.
network failure (affecting not only HTTP traffic, but all network traffic).
my Aunt when she receives the bill for unusual network usage?
add superfluous age due to double-counting every connection round trip.
> of stale responses in the presence of clock skew.
networks which are becoming increasingly dependent on cache efficiency.
there are no HTTP/1.0 caches in the loop, and that is our GOAL, right?
anyone even begins using caching for critical applications?
please forgive me if there are any further questions.
Reply: Larry Masinter: "Re: Confusion about Age: accuracy vs. safety"