Generation of the Age header field in HTTP/1.1
draft-mogul-http-age-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Jeffrey Mogul | ||
| Last updated | 1999-03-26 (Latest revision 1998-03-28) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-mogul-http-age-00.txt
Abstract
The 'Age' response-header field in HTTP/1.1 [RFC 2068] is intended to provide a lower bound of an estimate of a response message's age (time since generation), by explicitly indicating the amount of time that is known to have passed since the response message was retrieved or revalidated. There has been considerable controversy over when the Age header field should be added to a response. This document explains the issues, rebuts a previous proposal, and provides a set of proposed changes for the revision of RFC 2068.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)