Changeset 1593


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)

Location:
draft-ietf-httpbis
Files:
4 edited

Legend:

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

    r1592 r1593  
    13751375      </p>
    13761376      <p id="rfc.section.6.7.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
    1377          payload <em class="bcp14">SHOULD</em> be considered the current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
     1377         payload <em class="bcp14">SHOULD</em> be considered a current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
    13781378         when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's
    13791379         response contains the new representation of that resource, thereby distinguishing it from representations that might only
     
    21252125      <ul>
    21262126         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>&gt;: "is ETag a representation header field?"
     2127         </li>
     2128         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/338">http://tools.ietf.org/wg/httpbis/trac/ticket/338</a>&gt;: "Content-Location doesn't constrain the cardinality of representations"
    21272129         </li>
    21282130         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>&gt;: "make IANA policy definitions consistent"
  • draft-ietf-httpbis/19/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"
  • draft-ietf-httpbis/latest/p3-payload.html

    r1592 r1593  
    13761376      </p>
    13771377      <p id="rfc.section.6.7.p.4">If Content-Location is included in a response message and its value is the same as the effective request URI, then the response
    1378          payload <em class="bcp14">SHOULD</em> be considered the current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
     1378         payload <em class="bcp14">SHOULD</em> be considered a current representation of that resource. For a GET or HEAD request, this is the same as the default semantics
    13791379         when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's
    13801380         response contains the new representation of that resource, thereby distinguishing it from representations that might only
     
    21262126      <ul>
    21272127         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>&gt;: "is ETag a representation header field?"
     2128         </li>
     2129         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/338">http://tools.ietf.org/wg/httpbis/trac/ticket/338</a>&gt;: "Content-Location doesn't constrain the cardinality of representations"
    21282130         </li>
    21292131         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>&gt;: "make IANA policy definitions consistent"
  • 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.