Changeset 1594 for draft-ietf-httpbis/19
- Timestamp:
- 12/03/12 10:28:12 (11 years ago)
- Location:
- draft-ietf-httpbis/19
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/19/draft-ietf-httpbis-p3-payload-19.txt
r1592 r1594 1322 1322 If Content-Location is included in a response message and its value 1323 1323 is the same as the effective request URI, then the response payload 1324 SHOULD be considered the current representation of that resource.1325 For a GET or HEAD request, this is the same as the default semantics1326 when no Content-Location is provided by the server. For a state-1327 changing request like PUT or POST, it implies that the server's1328 responsecontains the new representation of that resource, thereby1324 SHOULD be considered a current representation of that resource. For 1325 a GET or HEAD request, this is the same as the default semantics when 1326 no Content-Location is provided by the server. For a state-changing 1327 request like PUT or POST, it implies that the server's response 1328 contains the new representation of that resource, thereby 1329 1329 distinguishing it from representations that might only report about 1330 1330 the action (e.g., "It worked!"). This allows authoring applications … … 2310 2310 representation header field?" 2311 2311 2312 o <http://tools.ietf.org/wg/httpbis/trac/ticket/338>: "Content- 2313 Location doesn't constrain the cardinality of representations" 2314 2312 2315 o <http://tools.ietf.org/wg/httpbis/trac/ticket/346>: "make IANA 2313 2316 policy definitions consistent" … … 2327 2330 gzip 8 2328 2331 compress (Coding Format) 7 2332 2333 2334 2335 Fielding, et al. Expires September 13, 2012 [Page 41] 2336 2337 2338 Internet-Draft HTTP/1.1, Part 3 March 2012 2339 2340 2329 2341 content negotiation 5 2330 2342 Content-Encoding header field 22 2331 2343 Content-Language header field 23 2332 2333 2334 2335 Fielding, et al. Expires September 13, 2012 [Page 41]2336 2337 2338 Internet-Draft HTTP/1.1, Part 3 March 20122339 2340 2341 2344 Content-Location header field 23 2342 2345 Content-Transfer-Encoding header field 32 … … 2384 2387 Content-Transfer-Encoding 32 2385 2388 Content-Type 25 2389 2390 2391 2392 Fielding, et al. Expires September 13, 2012 [Page 42] 2393 2394 2395 Internet-Draft HTTP/1.1, Part 3 March 2012 2396 2397 2386 2398 MIME-Version 30 2387 2399 2388 2400 M 2389 2390 2391 2392 Fielding, et al. Expires September 13, 2012 [Page 42]2393 2394 2395 Internet-Draft HTTP/1.1, Part 3 March 20122396 2397 2398 2401 MIME-Version header field 30 2399 2402 … … 2444 2447 2445 2448 2446 2447 2448 2449 2449 Fielding, et al. Expires September 13, 2012 [Page 43] 2450 2450 -
draft-ietf-httpbis/19/draft-ietf-httpbis-p3-payload-19.xml
r1592 r1594 1279 1279 If Content-Location is included in a response message and its value 1280 1280 is the same as the effective request URI, then the response payload 1281 SHOULD be considered thecurrent representation of that resource.1281 SHOULD be considered a current representation of that resource. 1282 1282 For a GET or HEAD request, this is the same as the default semantics 1283 1283 when no Content-Location is provided by the server. For a state-changing … … 2866 2866 </t> 2867 2867 <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> 2868 2872 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/346"/>: 2869 2873 "make IANA policy definitions consistent"
Note: See TracChangeset
for help on using the changeset viewer.