<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.reschke-http-etag-on-write" target="https://datatracker.ietf.org/doc/html/draft-reschke-http-etag-on-write-09">
   <front>
      <title>The Hypertext Transfer Protocol (HTTP) Entity Tag (&quot;ETag&quot;) Response Header in Write Operations</title>
      <author initials="J." surname="Reschke" fullname="Julian Reschke">
         <organization>greenbytes</organization>
      </author>
      <date month="March" day="2" year="2009" />
      <abstract>
	 <t>The Hypertext Transfer Protocol (HTTP) specifies a state identifier,
called &quot;Entity Tag&quot;, to be returned in the &quot;ETag&quot; 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.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-reschke-http-etag-on-write-09" />
   
</reference>
