Ignore:
Timestamp:
11/01/13 08:39:05 (8 years ago)
Author:
fielding@…
Message:

ensure that a validator field sent in response to a successful PUT means something useful; addresses #22 (along with [2110])

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2110 r2111  
    14431443</t>
    14441444<t>
     1445   An origin server &MUST-NOT; send a validator header field
     1446   (<xref target="response.validator"/>), such as an <x:ref>ETag</x:ref> or
     1447   <x:ref>Last-Modified</x:ref> field, in a successful response to PUT unless
     1448   the request's representation data was saved without any transformation
     1449   applied to the body (i.e., the resource's new representation data is
     1450   identical to the representation data received in the PUT request) and the
     1451   validator field value reflects the new representation.
     1452   This requirement allows a user agent to know when the representation body
     1453   it has in memory remains current as a result of the PUT, thus not in need
     1454   of retrieving again from the origin server, and that the new validator(s)
     1455   received in the response can be used for future conditional requests in
     1456   order to prevent accidental overwrites.
     1457</t>
     1458<t>
    14451459   The fundamental difference between the POST and PUT methods is
    14461460   highlighted by the different intent for the enclosed representation.
Note: See TracChangeset for help on using the changeset viewer.