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

regen -19 draft (see #338)

File:
1 edited

Legend:

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

    r1592 r1594  
    12791279   If Content-Location is included in a response message and its value
    12801280   is the same as the effective request URI, then the response payload
    1281    SHOULD be considered the current representation of that resource.
     1281   SHOULD be considered a current representation of that resource.
    12821282   For a GET or HEAD request, this is the same as the default semantics
    12831283   when no Content-Location is provided by the server.  For a state-changing
     
    28662866    </t>
    28672867    <t>
     2868      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/338"/>:
     2869      "Content-Location doesn't constrain the cardinality of representations"
     2870    </t>
     2871    <t>
    28682872      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>:
    28692873      "make IANA policy definitions consistent"
Note: See TracChangeset for help on using the changeset viewer.