Skip to main content

State Tokens and Preconditions for HTTP

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors Jim Whitehead , Yaron Y. Goland
Last updated 1997-05-22
RFC stream (None)
Intended RFC status (None)
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:


There are times when a principal will want to predicate successful execution of a method on the current state of a resource. While HTTP/1.1 provides a mechanism for conditional execution of methods using entity tags via the 'If-Match' and 'If-None-Match' headers, the mechanism is not sufficiently extensible to express conditional statements involving more generic state indicators, such as lock tokens. This draft defines the term 'state token' as an identifier for a state of a resource. This draft defines requirements for state tokens and provides a state token syntax, along with two new headers which are used to express method preconditions using state tokens.


Jim Whitehead
Yaron Y. Goland

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