Problem with HTTP/1.1 Warning header, and proposed fix
draft-ietf-http-warning-00

Document Type Expired Internet-Draft (http WG)
Last updated 1997-07-30
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-ietf-http-warning-00.txt

Abstract

The current HTTP/1.1 (RFC2068) specification introduces a new Warning header, meant to carry status information about a request that cannot or should not be carried by the response status code. The existing specification for the interaction between Warning and HTTP caches is faulty, in that it may allow incorrect results after cache validation operations. This document identifies two separate (but related) problems, and proposes revisions of the HTTP/1.1 specification to solve these problems.

Authors

Josh Cohen (josh@microsoft.com)
Scott Lawrence (slawrence@pingtel.com)

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