Ignore:
Timestamp:
Mar 12, 2012, 3:22:53 AM (8 years ago)
Author:
julian.reschke@…
Message:

Content-Location doesn't constrain the cardinality of representations (see #338)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.xml

    r1592 r1593  
    13211321   If Content-Location is included in a response message and its value
    13221322   is the same as the effective request URI, then the response payload
    1323    &SHOULD; be considered the current representation of that resource.
     1323   &SHOULD; be considered a current representation of that resource.
    13241324   For a GET or HEAD request, this is the same as the default semantics
    13251325   when no Content-Location is provided by the server.  For a state-changing
     
    29082908    </t>
    29092909    <t>
     2910      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/338"/>:
     2911      "Content-Location doesn't constrain the cardinality of representations"
     2912    </t>
     2913    <t>
    29102914      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>:
    29112915      "make IANA policy definitions consistent"
Note: See TracChangeset for help on using the changeset viewer.