The Hypertext Transfer Protocol (HTTP) Entity Tag ("ETag") Response Header in Write Operations
draft-reschke-http-etag-on-write-09

Document Type Expired Internet-Draft (individual)
Last updated 2009-03-02
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-reschke-http-etag-on-write-09.txt

Abstract

The Hypertext Transfer Protocol (HTTP) specifies a state identifier, called "Entity Tag", to be returned in the "ETag" response header. However, the description of this header for write operations such as PUT is incomplete, and has caused confusion among developers and protocol designers, and potentially interoperability problems. This document explains the problem in detail and suggests both a clarification for a revision to the HTTP/1.1 specification (RFC2616) and a new header for use in responses, making HTTP entity tags more useful for user agents that want to avoid round-trips to the server after modifying a resource.

Authors

Julian Reschke (julian.reschke@greenbytes.de)

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