Changeset 1593 for draft-ietf-httpbis/19/p3-payload.html
- Timestamp:
- 12/03/12 10:22:53 (10 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/19/p3-payload.html
r1592 r1593 1375 1375 </p> 1376 1376 <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 thecurrent representation of that resource. For a GET or HEAD request, this is the same as the default semantics1377 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 1378 1378 when no Content-Location is provided by the server. For a state-changing request like PUT or POST, it implies that the server's 1379 1379 response contains the new representation of that resource, thereby distinguishing it from representations that might only … … 2125 2125 <ul> 2126 2126 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/330">http://tools.ietf.org/wg/httpbis/trac/ticket/330</a>>: "is ETag a representation header field?" 2127 </li> 2128 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/338">http://tools.ietf.org/wg/httpbis/trac/ticket/338</a>>: "Content-Location doesn't constrain the cardinality of representations" 2127 2129 </li> 2128 2130 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/346">http://tools.ietf.org/wg/httpbis/trac/ticket/346</a>>: "make IANA policy definitions consistent"
Note: See TracChangeset
for help on using the changeset viewer.