The Hypertext Transfer Protocol (HTTP) Entity Tag ("ETag") Response Header in Write Operations

Glossary

The identifier is a name for the issue (and is unique within this document).

The type of issue is one of:

Editorial: for example typographical errors, poor clarity, or inconsistent terminology.
Change: an addition, deletion, or modification to the published specification.

The status of the issue is one of:

Open: subject to ongoing discussion and not yet resolved.
Closed: resolved by the working group. Requires documented resolution.
Editor: an editorial issue has been resolved unilaterally. Can be re-opened by the working group.

The reference is an indication of where the issue was first raised.

The description is a succinct overview of the issue.

The resolution describes the specification change that resolves the issue.

Identifier	Type / Status	Reference and Description	Proposed Resolution / Latest Change
edit	edit open	julian.reschke@greenbytes.de, 2006-08-10: Umbrella issue for editorial fixes/enhancements.	latest change in revision latest

Identifier	Type / Status	Reference and Description	Resolution / Latest Change
clarify-extensibility	edit closed	julian.reschke@greenbytes.de, 2006-10-12: Clarify the extension point.	in revision 03: Clarify that future revisions of this specification may define keywords other than the two defined here, and that the only one specifiying octet-by-octet equivalence is "identity".
entity-header	change closed	Reference: <http://lists.w3.org/Archives/Public/ietf-http-wg/2006JulSep/0031.html> julian.reschke@greenbytes.de, 2006-08-10: Roy Fielding points out that it's problematic to introduce new HTTP response headers, as deployed software will treat it as an entity header (see http://lists.w3.org/Archives/Public/ietf-http-wg/2006JulSep/0031.html and RFC 2616, Section 6.2).	in revision 01: Redefine the header so that it can indeed be used as an Entity header.
extensibility	change closed	julian.reschke@greenbytes.de, 2006-08-20: In draft 00, the presence of extensibility points for the "Entity-Transform" header apparently draws attention away from the more important parts of the draft: analyzing the key problem, and making minimal changes to solve them.	in revision 01: Header definition completely rewritten (including a reduction in extensibility).
rfc4918	change closed	julian.reschke@greenbytes.de, 2007-07-07: Update RFC2518 references to RFC4918, where appropriate.	in revision 07: Done.

Last change: 2007-07-07