Ticket #338: 338.diff

File 338.diff, 1.1 KB (added by julian.reschke@…, 8 years ago)

Proposed patch

  • p3-payload.xml

    14101410   If Content-Location is included in a response message and its value
    14111411   is the same as the effective request URI, then the response payload
    1412    &SHOULD; be considered the current representation of that resource.
     1412   &SHOULD; be considered a current representation of that resource.
    14131413   For a GET or HEAD request, this is the same as the default semantics
    14141414   when no Content-Location is provided by the server.  For a state-changing
    14151415   request like PUT or POST, it implies that the server's response contains
    31163116      "is ETag a representation header field?"
    31173117    </t>
    31183118    <t>
     3119      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/338"/>:
     3120      "Content-Location doesn't constrain the cardinality of representations"
     3121    </t>
     3122    <t>
    31193123      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>:
    31203124      "make IANA policy definitions consistent"
    31213125    </t>