Age Header Field in HTTP/1.1
draft-fielding-http-age-00

Document Type Expired Internet-Draft (individual)
Author Roy Fielding 
Last updated 1997-09-16 (latest revision 1997-04-05)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-fielding-http-age-00.txt

Abstract

The 'Age' response-header field in HTTP/1.1 [RFC 2068] is intended to provide a lower-bound for the estimation 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. However, there has been considerable controversy over when the Age header field should be added to a response. This document explains the issues and provides a set of proposed changes for the revision of RFC 2068.

Authors

Roy Fielding (fielding@ics.uci.edu)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)