Linked Cache Invalidation
draft-nottingham-linked-cache-inv-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Mark Nottingham , Mike Kelly | ||
| Last updated | 2012-05-27 (Latest revision 2011-11-24) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo defines Web link types that invalidate HTTP caches, along with an HTTP cache-control extension that allows caches that understand those link types to use responses containing them. Together, these mechanisms offer a way to avoid use of a response that has become stale due to another request that changes server-side state. Collectively, this is referred to as Linked Cache Invalidation (LCI).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)