@techreport{reschke-http-etag-on-write-09,
    number =    {draft-reschke-http-etag-on-write-09},
    type =      {Internet-Draft},
    institution =   {Internet Engineering Task Force},
    publisher = {Internet Engineering Task Force},
    note =      {Work in Progress},
    url =       {https://datatracker.ietf.org/doc/draft-reschke-http-etag-on-write/09/},
    author =    {Julian Reschke},
    title =     {{The Hypertext Transfer Protocol (HTTP) Entity Tag ("ETag") Response Header in Write Operations}},
    pagetotal = 20,
    year =      2009,
    month =     mar,
    day =       2,
    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.},
}