![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 2110 for draft-ietf-httpbis/latest
- Timestamp:
- 11/01/13 08:14:43 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 4 edited
-
p1-messaging.html (modified) (7 diffs)
-
p1-messaging.xml (modified) (2 diffs)
-
p2-semantics.html (modified) (40 diffs)
-
p2-semantics.xml (modified) (4 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2101 r2110 449 449 } 450 450 @bottom-center { 451 content: "Expires July 1 2, 2013";451 content: "Expires July 15, 2013"; 452 452 } 453 453 @bottom-right { … … 491 491 <meta name="dct.creator" content="Reschke, J. F."> 492 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 493 <meta name="dct.issued" scheme="ISO8601" content="2013-01- 08">493 <meta name="dct.issued" scheme="ISO8601" content="2013-01-11"> 494 494 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 520 520 <tr> 521 521 <td class="left">Intended status: Standards Track</td> 522 <td class="right">January 8, 2013</td>522 <td class="right">January 11, 2013</td> 523 523 </tr> 524 524 <tr> 525 <td class="left">Expires: July 1 2, 2013</td>525 <td class="left">Expires: July 15, 2013</td> 526 526 <td class="right"></td> 527 527 </tr> … … 551 551 in progress”. 552 552 </p> 553 <p>This Internet-Draft will expire on July 1 2, 2013.</p>553 <p>This Internet-Draft will expire on July 15, 2013.</p> 554 554 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 555 555 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 1381 1381 payload body. For messages that do include a payload body, the Content-Length field-value provides the framing information 1382 1382 necessary for determining where the body (and message) ends. For messages that do not include a payload body, the Content-Length 1383 indicates the size of the selected representation (<a href="p2-semantics.html# selected.representation" title="Selected Representation Header Fields">Section 7.2</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>).1383 indicates the size of the selected representation (<a href="p2-semantics.html#representations" title="Representations">Section 3</a> of <a href="#Part2" id="rfc.xref.Part2.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a>). 1384 1384 </p> 1385 1385 <div id="rfc.figure.u.28"></div><pre class="inline"><span id="rfc.iref.g.54"></span> <a href="#header.content-length" class="smpl">Content-Length</a> = 1*<a href="#core.rules" class="smpl">DIGIT</a> … … 3259 3259 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">2.1</a>, <a href="#rfc.xref.Part2.3">2.3</a>, <a href="#rfc.xref.Part2.4">2.7</a>, <a href="#rfc.xref.Part2.5">2.7.1</a>, <a href="#rfc.xref.Part2.6">3.1.1</a>, <a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.8">3.1.2</a>, <a href="#rfc.xref.Part2.9">3.2</a>, <a href="#rfc.xref.Part2.10">3.2.1</a>, <a href="#rfc.xref.Part2.11">3.3</a>, <a href="#rfc.xref.Part2.12">3.3</a>, <a href="#rfc.xref.Part2.13">3.3.1</a>, <a href="#rfc.xref.Part2.14">3.3.2</a>, <a href="#rfc.xref.Part2.15">3.3.2</a>, <a href="#rfc.xref.Part2.16">3.3.2</a>, <a href="#rfc.xref.Part2.17">4.3</a>, <a href="#rfc.xref.Part2.18">5.1</a>, <a href="#rfc.xref.Part2.19">5.3</a>, <a href="#rfc.xref.Part2.20">5.3</a>, <a href="#rfc.xref.Part2.21">5.6</a>, <a href="#rfc.xref.Part2.22">5.7.2</a>, <a href="#rfc.xref.Part2.23">6.3.1</a>, <a href="#rfc.xref.Part2.24">6.3.2</a>, <a href="#rfc.xref.Part2.25">6.7</a>, <a href="#rfc.xref.Part2.26">7.4</a>, <a href="#rfc.xref.Part2.27">8.3</a>, <a href="#rfc.xref.Part2.28">8.3</a>, <a href="#Part2"><b>10.1</b></a><ul> 3260 3260 <li><em>Section 2</em> <a href="#rfc.xref.Part2.4">2.7</a></li> 3261 <li><em>Section 3</em> <a href="#rfc.xref.Part2.14">3.3.2</a></li> 3261 3262 <li><em>Section 3.1.2.1</em> <a href="#rfc.xref.Part2.13">3.3.1</a>, <a href="#rfc.xref.Part2.26">7.4</a></li> 3262 3263 <li><em>Section 3.3</em> <a href="#rfc.xref.Part2.22">5.7.2</a></li> … … 3274 3275 <li><em>Section 6.5.12</em> <a href="#rfc.xref.Part2.7">3.1.1</a>, <a href="#rfc.xref.Part2.27">8.3</a></li> 3275 3276 <li><em>Section 7.1.1.2</em> <a href="#rfc.xref.Part2.9">3.2</a></li> 3276 <li><em>Section 7.2</em> <a href="#rfc.xref.Part2.14">3.3.2</a></li>3277 3277 <li><em>Section 8.3</em> <a href="#rfc.xref.Part2.10">3.2.1</a></li> 3278 3278 <li><em>Appendix A</em> <a href="#rfc.xref.Part2.2">2.1</a></li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2101 r2110 48 48 <!ENTITY qvalue "<xref target='Part2' x:rel='#quality.values' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 49 49 <!ENTITY resource "<xref target='Part2' x:rel='#resources' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 50 <!ENTITY selected-representation "<xref target='Part2' x:rel='#selected.representation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">51 50 <!ENTITY status-codes "<xref target='Part2' x:rel='#status.codes' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> 52 51 <!ENTITY status-1xx "<xref target='Part2' x:rel='#status.1xx' xmlns:x='http://purl.org/net/xml2rfc/ext'/>"> … … 1563 1562 (and message) ends. For messages that do not include a payload body, the 1564 1563 Content-Length indicates the size of the selected representation 1565 (& selected-representation;).1564 (&representation;). 1566 1565 </t> 1567 1566 <figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Content-Length"/> -
draft-ietf-httpbis/latest/p2-semantics.html
r2108 r2110 449 449 } 450 450 @bottom-center { 451 content: "Expires July 1 4, 2013";451 content: "Expires July 15, 2013"; 452 452 } 453 453 @bottom-right { … … 494 494 <meta name="dct.creator" content="Reschke, J. F."> 495 495 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 496 <meta name="dct.issued" scheme="ISO8601" content="2013-01-1 0">496 <meta name="dct.issued" scheme="ISO8601" content="2013-01-11"> 497 497 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 498 498 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation."> … … 522 522 <tr> 523 523 <td class="left">Intended status: Standards Track</td> 524 <td class="right">January 1 0, 2013</td>524 <td class="right">January 11, 2013</td> 525 525 </tr> 526 526 <tr> 527 <td class="left">Expires: July 1 4, 2013</td>527 <td class="left">Expires: July 15, 2013</td> 528 528 <td class="right"></td> 529 529 </tr> … … 553 553 in progress”. 554 554 </p> 555 <p>This Internet-Draft will expire on July 1 4, 2013.</p>555 <p>This Internet-Draft will expire on July 15, 2013.</p> 556 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 557 557 <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 728 728 </ul> 729 729 </li> 730 <li><a href="#rfc.section.7.2">7.2</a> <a href="# selected.representation">Selected RepresentationHeader Fields</a></li>730 <li><a href="#rfc.section.7.2">7.2</a> <a href="#response.validator">Validator Header Fields</a></li> 731 731 <li><a href="#rfc.section.7.3">7.3</a> <a href="#response.auth">Authentication Challenges</a></li> 732 732 <li><a href="#rfc.section.7.4">7.4</a> <a href="#response.context">Response Context</a><ul> … … 836 836 </p> 837 837 <div id="rfc.iref.r.1"></div> 838 <div id="rfc.iref.s.1"></div> 838 839 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="representations" href="#representations">Representations</a></h1> 839 840 <p id="rfc.section.3.p.1">If we consider that a resource could be anything, and that the uniform interface provided by HTTP is similar to a window through … … 845 846 readily communicated via the protocol, and that consists of a set of representation metadata and a potentially unbounded stream 846 847 of representation data. 848 </p> 849 <p id="rfc.section.3.p.3">We use the term "<dfn>selected representation</dfn>" to refer to the representation of the <a href="#resources" class="smpl">target resource</a> in a <a href="#status.200" class="smpl">200 (OK)</a> response to <a href="#GET" class="smpl">GET</a>, or the representation that would have been selected in a successful response if the request had used the method <a href="#GET" class="smpl">GET</a> and excluded any conditional request header fields. 847 850 </p> 848 851 <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="representation.metadata" href="#representation.metadata">Representation Metadata</a></h2> … … 1327 1330 </p> 1328 1331 <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a> <a id="method.properties" href="#method.properties">Common Method Properties</a></h2> 1329 <div id="rfc.iref.s. 1"></div>1332 <div id="rfc.iref.s.2"></div> 1330 1333 <h3 id="rfc.section.4.2.1"><a href="#rfc.section.4.2.1">4.2.1</a> <a id="safe.methods" href="#safe.methods">Safe Methods</a></h3> 1331 1334 <p id="rfc.section.4.2.1.p.1">Request methods are considered "<dfn>safe</dfn>" if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state … … 1667 1670 </p> 1668 1671 <p id="rfc.section.5.1.1.p.6">Many older HTTP/1.0 and HTTP/1.1 servers do not understand the Expect header field.</p> 1669 <div id="rfc.iref.4 4"></div>1672 <div id="rfc.iref.45"></div> 1670 1673 <div id="rfc.iref.e.2"></div> 1671 1674 <h4 id="rfc.section.5.1.1.1"><a href="#rfc.section.5.1.1.1">5.1.1.1</a> <a id="use.of.the.100.status" href="#use.of.the.100.status">Use of the 100 (Continue) Status</a></h4> … … 2379 2382 <p id="rfc.section.6.1.p.2">Note that this list is not exhaustive — it does not include extension status codes defined in other specifications.</p> 2380 2383 <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="status.1xx" href="#status.1xx">Informational 1xx</a></h2> 2381 <div id="rfc.iref.7 0"></div>2382 <div id="rfc.iref.s. 2"></div>2384 <div id="rfc.iref.71"></div> 2385 <div id="rfc.iref.s.3"></div> 2383 2386 <p id="rfc.section.6.2.p.1">The <dfn>1xx (Informational)</dfn> class of status code indicates an interim response for communicating connection status or request progress prior to completing 2384 2387 the requested action and sending a final response. All 1xx responses consist of only the status-line and optional header fields, … … 2392 2395 a request, then it need not forward the corresponding <a href="#status.100" class="smpl">100 (Continue)</a> response(s). 2393 2396 </p> 2394 <div id="rfc.iref.7 1"></div>2397 <div id="rfc.iref.72"></div> 2395 2398 <h3 id="rfc.section.6.2.1"><a href="#rfc.section.6.2.1">6.2.1</a> <a id="status.100" href="#status.100">100 Continue</a></h3> 2396 2399 <p id="rfc.section.6.2.1.p.1">The <dfn>100 (Continue)</dfn> status code indicates that the initial part of a request has been received and has not yet been rejected by the server. The … … 2401 2404 <p id="rfc.section.6.2.1.p.3">If the request did not contain an <a href="#header.expect" class="smpl">Expect</a> header field containing the <a href="#use.of.the.100.status" class="smpl">100-continue</a> expectation, the client can simply discard this interim response. 2402 2405 </p> 2403 <div id="rfc.iref.7 1"></div>2406 <div id="rfc.iref.72"></div> 2404 2407 <h3 id="rfc.section.6.2.2"><a href="#rfc.section.6.2.2">6.2.2</a> <a id="status.101" href="#status.101">101 Switching Protocols</a></h3> 2405 2408 <p id="rfc.section.6.2.2.p.1">The <dfn>101 (Switching Protocols)</dfn> status code indicates that the server understands and is willing to comply with the client's request, via the <a href="p1-messaging.html#header.upgrade" class="smpl">Upgrade</a> header field (<a href="p1-messaging.html#header.upgrade" title="Upgrade">Section 6.7</a> of <a href="#Part1" id="rfc.xref.Part1.22"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>), for a change in the application protocol being used on this connection. The server will switch to the protocol(s) indicated … … 2411 2414 </p> 2412 2415 <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a> <a id="status.2xx" href="#status.2xx">Successful 2xx</a></h2> 2413 <div id="rfc.iref.7 1"></div>2414 <div id="rfc.iref.s. 3"></div>2416 <div id="rfc.iref.72"></div> 2417 <div id="rfc.iref.s.4"></div> 2415 2418 <p id="rfc.section.6.3.p.1">The <dfn>2xx (Successful)</dfn> class of status code indicates that the client's request was successfully received, understood, and accepted. 2416 2419 </p> 2417 <div id="rfc.iref.7 2"></div>2420 <div id="rfc.iref.73"></div> 2418 2421 <h3 id="rfc.section.6.3.1"><a href="#rfc.section.6.3.1">6.3.1</a> <a id="status.200" href="#status.200">200 OK</a></h3> 2419 2422 <p id="rfc.section.6.3.1.p.1">The <dfn>200 (OK)</dfn> status code indicates that the request has succeeded. The meaning of a payload sent in the response depends on the request … … 2440 2443 <p id="rfc.section.6.3.1.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 200 responses. 2441 2444 </p> 2442 <div id="rfc.iref.7 2"></div>2445 <div id="rfc.iref.73"></div> 2443 2446 <h3 id="rfc.section.6.3.2"><a href="#rfc.section.6.3.2">6.3.2</a> <a id="status.201" href="#status.201">201 Created</a></h3> 2444 2447 <p id="rfc.section.6.3.2.p.1">The <dfn>201 (Created)</dfn> status code indicates that the request has been fulfilled and has resulted in one or more new resources being created. The 2445 2448 primary resource created by the request is identified by either a <a href="#header.location" class="smpl">Location</a> header field in the response or, if no <a href="#header.location" class="smpl">Location</a> field is received, by the effective request URI. 2446 2449 </p> 2447 <p id="rfc.section.6.3.2.p.2">The 201 response payload typically describes and links to the resource(s) created. See <a href="# selected.representation" title="Selected Representation Header Fields">Section 7.2</a> for discussion of the meaning and purpose of selected representationheader fields, such as <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> and <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a>, in a 201 response.2448 </p> 2449 <div id="rfc.iref.7 2"></div>2450 <p id="rfc.section.6.3.2.p.2">The 201 response payload typically describes and links to the resource(s) created. See <a href="#response.validator" title="Validator Header Fields">Section 7.2</a> for a discussion of the meaning and purpose of validator header fields, such as <a href="p4-conditional.html#header.etag" class="smpl">ETag</a> and <a href="p4-conditional.html#header.last-modified" class="smpl">Last-Modified</a>, in a 201 response. 2451 </p> 2452 <div id="rfc.iref.73"></div> 2450 2453 <h3 id="rfc.section.6.3.3"><a href="#rfc.section.6.3.3">6.3.3</a> <a id="status.202" href="#status.202">202 Accepted</a></h3> 2451 2454 <p id="rfc.section.6.3.3.p.1">The <dfn>202 (Accepted)</dfn> status code indicates that the request has been accepted for processing, but the processing has not been completed. The request … … 2459 2462 be fulfilled. 2460 2463 </p> 2461 <div id="rfc.iref.7 2"></div>2464 <div id="rfc.iref.73"></div> 2462 2465 <h3 id="rfc.section.6.3.4"><a href="#rfc.section.6.3.4">6.3.4</a> <a id="status.203" href="#status.203">203 Non-Authoritative Information</a></h3> 2463 2466 <p id="rfc.section.6.3.4.p.1">The <dfn>203 (Non-Authoritative Information)</dfn> status code indicates that the request was successful but the enclosed payload has been modified from that of the origin server's <a href="#status.200" class="smpl">200 (OK)</a> response by a transforming proxy (<a href="p1-messaging.html#message.transformations" title="Transformations">Section 5.7.2</a> of <a href="#Part1" id="rfc.xref.Part1.23"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). This status code allows the proxy to notify recipients when a transformation has been applied, since that knowledge might … … 2467 2470 <p id="rfc.section.6.3.4.p.2">The 203 response is similar to the Warning code of 214 Transformation Applied (<a href="p6-cache.html#header.warning" title="Warning">Section 7.5</a> of <a href="#Part6" id="rfc.xref.Part6.11"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>), which has the advantage of being applicable to responses with any status code. 2468 2471 </p> 2469 <div id="rfc.iref.7 2"></div>2472 <div id="rfc.iref.73"></div> 2470 2473 <h3 id="rfc.section.6.3.5"><a href="#rfc.section.6.3.5">6.3.5</a> <a id="status.204" href="#status.204">204 No Content</a></h3> 2471 2474 <p id="rfc.section.6.3.5.p.1">The <dfn>204 (No Content)</dfn> status code indicates that the server has successfully fulfilled the request and that there is no additional content to send … … 2485 2488 </p> 2486 2489 <p id="rfc.section.6.3.5.p.5">A 204 response is terminated by the first empty line after the header fields because it cannot contain a message body.</p> 2487 <div id="rfc.iref.7 2"></div>2490 <div id="rfc.iref.73"></div> 2488 2491 <h3 id="rfc.section.6.3.6"><a href="#rfc.section.6.3.6">6.3.6</a> <a id="status.205" href="#status.205">205 Reset Content</a></h3> 2489 2492 <p id="rfc.section.6.3.6.p.1">The <dfn>205 (Reset Content)</dfn> status code indicates that the server has fulfilled the request and desires that the user agent reset the "document view", … … 2498 2501 </p> 2499 2502 <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a> <a id="status.3xx" href="#status.3xx">Redirection 3xx</a></h2> 2500 <div id="rfc.iref.7 2"></div>2501 <div id="rfc.iref.s. 4"></div>2503 <div id="rfc.iref.73"></div> 2504 <div id="rfc.iref.s.5"></div> 2502 2505 <p id="rfc.section.6.4.p.1">The <dfn>3xx (Redirection)</dfn> class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. If 2503 2506 a <a href="#header.location" class="smpl">Location</a> header field (<a href="#header.location" id="rfc.xref.header.location.2" title="Location">Section 7.1.2</a>) is provided, the user agent <em class="bcp14">MAY</em> automatically redirect its request to the URI referenced by the Location field value, even if the specific status code is … … 2535 2538 </p> 2536 2539 </div> 2537 <div id="rfc.iref.7 3"></div>2540 <div id="rfc.iref.74"></div> 2538 2541 <h3 id="rfc.section.6.4.1"><a href="#rfc.section.6.4.1">6.4.1</a> <a id="status.300" href="#status.300">300 Multiple Choices</a></h3> 2539 2542 <p id="rfc.section.6.4.1.p.1">The <dfn>300 (Multiple Choices)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> has more than one representation, each with its own more specific identifier, and information about the alternatives is being … … 2557 2560 </p> 2558 2561 </div> 2559 <div id="rfc.iref.7 3"></div>2562 <div id="rfc.iref.74"></div> 2560 2563 <h3 id="rfc.section.6.4.2"><a href="#rfc.section.6.4.2">6.4.2</a> <a id="status.301" href="#status.301">301 Moved Permanently</a></h3> 2561 2564 <p id="rfc.section.6.4.2.p.1">The <dfn>301 (Moved Permanently)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> has been assigned a new permanent URI and any future references to this resource ought to use one of the enclosed URIs. Clients … … 2572 2575 <p id="rfc.section.6.4.2.p.4">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.13"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 301 responses. 2573 2576 </p> 2574 <div id="rfc.iref.7 3"></div>2577 <div id="rfc.iref.74"></div> 2575 2578 <h3 id="rfc.section.6.4.3"><a href="#rfc.section.6.4.3">6.4.3</a> <a id="status.302" href="#status.302">302 Found</a></h3> 2576 2579 <p id="rfc.section.6.4.3.p.1">The <dfn>302 (Found)</dfn> status code indicates that the target resource resides temporarily under a different URI. Since the redirection might be altered … … 2584 2587 </p> 2585 2588 </div> 2586 <div id="rfc.iref.7 3"></div>2589 <div id="rfc.iref.74"></div> 2587 2590 <h3 id="rfc.section.6.4.4"><a href="#rfc.section.6.4.4">6.4.4</a> <a id="status.303" href="#status.303">303 See Other</a></h3> 2588 2591 <p id="rfc.section.6.4.4.p.1">The <dfn>303 (See Other)</dfn> status code indicates that the server is redirecting the user agent to a different resource, as indicated by a URI in the <a href="#header.location" class="smpl">Location</a> header field, that is intended to provide an indirect response to the original request. In order to satisfy the original request, … … 2603 2606 a hyperlink to the same URI reference provided in the <a href="#header.location" class="smpl">Location</a> header field. 2604 2607 </p> 2605 <div id="rfc.iref.7 3"></div>2608 <div id="rfc.iref.74"></div> 2606 2609 <h3 id="rfc.section.6.4.5"><a href="#rfc.section.6.4.5">6.4.5</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h3> 2607 2610 <p id="rfc.section.6.4.5.p.1">The <dfn>305 (Use Proxy)</dfn> status code was defined in a previous version of this specification and is now deprecated (<a href="#changes.from.rfc.2616" title="Significant changes from RFC 2616">Appendix B</a>). 2608 2611 </p> 2609 <div id="rfc.iref.7 3"></div>2612 <div id="rfc.iref.74"></div> 2610 2613 <h3 id="rfc.section.6.4.6"><a href="#rfc.section.6.4.6">6.4.6</a> <a id="status.306" href="#status.306">306 (Unused)</a></h3> 2611 2614 <p id="rfc.section.6.4.6.p.1">The 306 status code was defined in a previous version of this specification, is no longer used, and the code is reserved.</p> 2612 <div id="rfc.iref.7 3"></div>2615 <div id="rfc.iref.74"></div> 2613 2616 <h3 id="rfc.section.6.4.7"><a href="#rfc.section.6.4.7">6.4.7</a> <a id="status.307" href="#status.307">307 Temporary Redirect</a></h3> 2614 2617 <p id="rfc.section.6.4.7.p.1">The <dfn>307 (Temporary Redirect)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> resides temporarily under a different URI and the user agent <em class="bcp14">MUST NOT</em> change the request method if it performs an automatic redirection to that URI. Since the redirection can change over time, … … 2625 2628 </div> 2626 2629 <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a> <a id="status.4xx" href="#status.4xx">Client Error 4xx</a></h2> 2627 <div id="rfc.iref.7 3"></div>2628 <div id="rfc.iref.s. 5"></div>2630 <div id="rfc.iref.74"></div> 2631 <div id="rfc.iref.s.6"></div> 2629 2632 <p id="rfc.section.6.5.p.1">The <dfn>4xx (Client Error)</dfn> class of status code indicates that the client seems to have erred. Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition. 2630 2633 These status codes are applicable to any request method. User agents <em class="bcp14">SHOULD</em> display any included representation to the user. 2631 2634 </p> 2632 <div id="rfc.iref.7 4"></div>2635 <div id="rfc.iref.75"></div> 2633 2636 <h3 id="rfc.section.6.5.1"><a href="#rfc.section.6.5.1">6.5.1</a> <a id="status.400" href="#status.400">400 Bad Request</a></h3> 2634 2637 <p id="rfc.section.6.5.1.p.1">The <dfn>400 (Bad Request)</dfn> status code indicates that the server cannot or will not process the request because the received syntax is invalid, nonsensical, 2635 2638 or exceeds some limitation on what the server is willing to process. 2636 2639 </p> 2637 <div id="rfc.iref.7 4"></div>2640 <div id="rfc.iref.75"></div> 2638 2641 <h3 id="rfc.section.6.5.2"><a href="#rfc.section.6.5.2">6.5.2</a> <a id="status.402" href="#status.402">402 Payment Required</a></h3> 2639 2642 <p id="rfc.section.6.5.2.p.1">The <dfn>402 (Payment Required)</dfn> status code is reserved for future use. 2640 2643 </p> 2641 <div id="rfc.iref.7 4"></div>2644 <div id="rfc.iref.75"></div> 2642 2645 <h3 id="rfc.section.6.5.3"><a href="#rfc.section.6.5.3">6.5.3</a> <a id="status.403" href="#status.403">403 Forbidden</a></h3> 2643 2646 <p id="rfc.section.6.5.3.p.1">The <dfn>403 (Forbidden)</dfn> status code indicates that the server understood the request but refuses to authorize it. A server that wishes to make public … … 2648 2651 <p id="rfc.section.6.5.3.p.3">An origin server that wishes to "hide" the current existence of a forbidden <a href="#resources" class="smpl">target resource</a> <em class="bcp14">MAY</em> instead respond with a status code of <a href="#status.404" class="smpl">404 (Not Found)</a>. 2649 2652 </p> 2650 <div id="rfc.iref.7 4"></div>2653 <div id="rfc.iref.75"></div> 2651 2654 <h3 id="rfc.section.6.5.4"><a href="#rfc.section.6.5.4">6.5.4</a> <a id="status.404" href="#status.404">404 Not Found</a></h3> 2652 2655 <p id="rfc.section.6.5.4.p.1">The <dfn>404 (Not Found)</dfn> status code indicates that the origin server did not find a current representation for the <a href="#resources" class="smpl">target resource</a> or is not willing to disclose that one exists. A 404 status does not indicate whether this lack of representation is temporary … … 2654 2657 is likely to be permanent. 2655 2658 </p> 2656 <div id="rfc.iref.7 4"></div>2659 <div id="rfc.iref.75"></div> 2657 2660 <h3 id="rfc.section.6.5.5"><a href="#rfc.section.6.5.5">6.5.5</a> <a id="status.405" href="#status.405">405 Method Not Allowed</a></h3> 2658 2661 <p id="rfc.section.6.5.5.p.1">The <dfn>405 (Method Not Allowed)</dfn> status code indicates that the method specified in the request-line is known by the origin server but not supported by the <a href="#resources" class="smpl">target resource</a>. The origin server <em class="bcp14">MUST</em> generate an <a href="#header.allow" class="smpl">Allow</a> header field in a 405 response containing a list of the target resource's currently supported methods. 2659 2662 </p> 2660 <div id="rfc.iref.7 4"></div>2663 <div id="rfc.iref.75"></div> 2661 2664 <h3 id="rfc.section.6.5.6"><a href="#rfc.section.6.5.6">6.5.6</a> <a id="status.406" href="#status.406">406 Not Acceptable</a></h3> 2662 2665 <p id="rfc.section.6.5.6.p.1">The <dfn>406 (Not Acceptable)</dfn> status code indicates that the <a href="#resources" class="smpl">target resource</a> does not have a current representation that would be acceptable to the user agent, according to the <a href="#proactive.negotiation" class="smpl">proactive negotiation</a> header fields received in the request (<a href="#request.conneg" title="Content Negotiation">Section 5.3</a>), and the server is unwilling to supply a default representation. … … 2666 2669 for such automatic selection, as described in <a href="#status.300" id="rfc.xref.status.300.2" title="300 Multiple Choices">Section 6.4.1</a>. 2667 2670 </p> 2668 <div id="rfc.iref.7 4"></div>2671 <div id="rfc.iref.75"></div> 2669 2672 <h3 id="rfc.section.6.5.7"><a href="#rfc.section.6.5.7">6.5.7</a> <a id="status.408" href="#status.408">408 Request Timeout</a></h3> 2670 2673 <p id="rfc.section.6.5.7.p.1">The <dfn>408 (Request Timeout)</dfn> status code indicates that the server did not receive a complete request message within the time that it was prepared to wait. … … 2672 2675 the client has an outstanding request in transit, the client <em class="bcp14">MAY</em> repeat that request on a new connection. 2673 2676 </p> 2674 <div id="rfc.iref.7 4"></div>2677 <div id="rfc.iref.75"></div> 2675 2678 <h3 id="rfc.section.6.5.8"><a href="#rfc.section.6.5.8">6.5.8</a> <a id="status.409" href="#status.409">409 Conflict</a></h3> 2676 2679 <p id="rfc.section.6.5.8.p.1">The <dfn>409 (Conflict)</dfn> status code indicates that the request could not be completed due to a conflict with the current state of the resource. This … … 2682 2685 contain information useful for merging the differences based on the revision history. 2683 2686 </p> 2684 <div id="rfc.iref.7 4"></div>2687 <div id="rfc.iref.75"></div> 2685 2688 <h3 id="rfc.section.6.5.9"><a href="#rfc.section.6.5.9">6.5.9</a> <a id="status.410" href="#status.410">410 Gone</a></h3> 2686 2689 <p id="rfc.section.6.5.9.p.1">The <dfn>410 (Gone)</dfn> status code indicates that access to the <a href="#resources" class="smpl">target resource</a> is no longer available at the origin server and that this condition is likely to be permanent. If the origin server does not … … 2695 2698 <p id="rfc.section.6.5.9.p.3">Caches <em class="bcp14">MAY</em> use a heuristic (see <a href="p6-cache.html#heuristic.freshness" title="Calculating Heuristic Freshness">Section 4.1.2</a> of <a href="#Part6" id="rfc.xref.Part6.14"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to determine freshness for 410 responses. 2696 2699 </p> 2697 <div id="rfc.iref.7 4"></div>2700 <div id="rfc.iref.75"></div> 2698 2701 <h3 id="rfc.section.6.5.10"><a href="#rfc.section.6.5.10">6.5.10</a> <a id="status.411" href="#status.411">411 Length Required</a></h3> 2699 2702 <p id="rfc.section.6.5.10.p.1">The <dfn>411 (Length Required)</dfn> status code indicates that the server refuses to accept the request without a defined <a href="p1-messaging.html#header.content-length" class="smpl">Content-Length</a> (<a href="p1-messaging.html#header.content-length" title="Content-Length">Section 3.3.2</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>). The client <em class="bcp14">MAY</em> repeat the request if it adds a valid Content-Length header field containing the length of the message body in the request 2700 2703 message. 2701 2704 </p> 2702 <div id="rfc.iref.7 4"></div>2705 <div id="rfc.iref.75"></div> 2703 2706 <h3 id="rfc.section.6.5.11"><a href="#rfc.section.6.5.11">6.5.11</a> <a id="status.413" href="#status.413">413 Payload Too Large</a></h3> 2704 2707 <p id="rfc.section.6.5.11.p.1">The <dfn>413 (Payload Too Large)</dfn> status code indicates that the server is refusing to process a request because the request payload is larger than the server … … 2707 2710 <p id="rfc.section.6.5.11.p.2">If the condition is temporary, the server <em class="bcp14">SHOULD</em> generate a <a href="#header.retry-after" class="smpl">Retry-After</a> header field to indicate that it is temporary and after what time the client <em class="bcp14">MAY</em> try again. 2708 2711 </p> 2709 <div id="rfc.iref.7 4"></div>2712 <div id="rfc.iref.75"></div> 2710 2713 <h3 id="rfc.section.6.5.12"><a href="#rfc.section.6.5.12">6.5.12</a> <a id="status.414" href="#status.414">414 URI Too Long</a></h3> 2711 2714 <p id="rfc.section.6.5.12.p.1">The <dfn>414 (URI Too Long)</dfn> status code indicates that the server is refusing to service the request because the request-target (<a href="p1-messaging.html#request-target" title="Request Target">Section 5.3</a> of <a href="#Part1" id="rfc.xref.Part1.26"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a>) is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly … … 2714 2717 attempting to exploit potential security holes. 2715 2718 </p> 2716 <div id="rfc.iref.7 4"></div>2719 <div id="rfc.iref.75"></div> 2717 2720 <h3 id="rfc.section.6.5.13"><a href="#rfc.section.6.5.13">6.5.13</a> <a id="status.415" href="#status.415">415 Unsupported Media Type</a></h3> 2718 2721 <p id="rfc.section.6.5.13.p.1">The <dfn>415 (Unsupported Media Type)</dfn> status code indicates that the origin server is refusing to service the request because the payload is in a format not supported 2719 2722 by the <a href="#resources" class="smpl">target resource</a> for this method. The format problem might be due to the request's indicated <a href="#header.content-type" class="smpl">Content-Type</a> or <a href="#header.content-encoding" class="smpl">Content-Encoding</a>, or as a result of inspecting the data directly. 2720 2723 </p> 2721 <div id="rfc.iref.7 4"></div>2724 <div id="rfc.iref.75"></div> 2722 2725 <h3 id="rfc.section.6.5.14"><a href="#rfc.section.6.5.14">6.5.14</a> <a id="status.417" href="#status.417">417 Expectation Failed</a></h3> 2723 2726 <p id="rfc.section.6.5.14.p.1">The <dfn>417 (Expectation Failed)</dfn> status code indicates that the expectation given in the request's <a href="#header.expect" class="smpl">Expect</a> header field (<a href="#header.expect" id="rfc.xref.header.expect.2" title="Expect">Section 5.1.1</a>) could not be met by at least one of the inbound servers. 2724 2727 </p> 2725 <div id="rfc.iref.7 4"></div>2728 <div id="rfc.iref.75"></div> 2726 2729 <h3 id="rfc.section.6.5.15"><a href="#rfc.section.6.5.15">6.5.15</a> <a id="status.426" href="#status.426">426 Upgrade Required</a></h3> 2727 2730 <p id="rfc.section.6.5.15.p.1">The <dfn>426 (Upgrade Required)</dfn> status code indicates that the server refuses to perform the request using the current protocol but might be willing to do … … 2737 2740 <span id="s426body">This service requires use of the HTTP/3.0 protocol. 2738 2741 </span></pre><h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a> <a id="status.5xx" href="#status.5xx">Server Error 5xx</a></h2> 2739 <div id="rfc.iref.7 4"></div>2740 <div id="rfc.iref.s. 6"></div>2742 <div id="rfc.iref.75"></div> 2743 <div id="rfc.iref.s.7"></div> 2741 2744 <p id="rfc.section.6.6.p.1">The <dfn>5xx (Server Error)</dfn> class of status code indicates that the server is aware that it has erred or is incapable of performing the requested method. 2742 2745 Except when responding to a HEAD request, the server <em class="bcp14">SHOULD</em> send a representation containing an explanation of the error situation, and whether it is a temporary or permanent condition. 2743 2746 User agents <em class="bcp14">SHOULD</em> display any included representation to the user. These response codes are applicable to any request method. 2744 2747 </p> 2745 <div id="rfc.iref.7 5"></div>2748 <div id="rfc.iref.76"></div> 2746 2749 <h3 id="rfc.section.6.6.1"><a href="#rfc.section.6.6.1">6.6.1</a> <a id="status.500" href="#status.500">500 Internal Server Error</a></h3> 2747 2750 <p id="rfc.section.6.6.1.p.1">The <dfn>500 (Internal Server Error)</dfn> status code indicates that the server encountered an unexpected condition that prevented it from fulfilling the request. 2748 2751 </p> 2749 <div id="rfc.iref.7 5"></div>2752 <div id="rfc.iref.76"></div> 2750 2753 <h3 id="rfc.section.6.6.2"><a href="#rfc.section.6.6.2">6.6.2</a> <a id="status.501" href="#status.501">501 Not Implemented</a></h3> 2751 2754 <p id="rfc.section.6.6.2.p.1">The <dfn>501 (Not Implemented)</dfn> status code indicates that the server does not support the functionality required to fulfill the request. This is the appropriate 2752 2755 response when the server does not recognize the request method and is not capable of supporting it for any resource. 2753 2756 </p> 2754 <div id="rfc.iref.7 5"></div>2757 <div id="rfc.iref.76"></div> 2755 2758 <h3 id="rfc.section.6.6.3"><a href="#rfc.section.6.6.3">6.6.3</a> <a id="status.502" href="#status.502">502 Bad Gateway</a></h3> 2756 2759 <p id="rfc.section.6.6.3.p.1">The <dfn>502 (Bad Gateway)</dfn> status code indicates that the server, while acting as a gateway or proxy, received an invalid response from an inbound server 2757 2760 it accessed while attempting to fulfill the request. 2758 2761 </p> 2759 <div id="rfc.iref.7 5"></div>2762 <div id="rfc.iref.76"></div> 2760 2763 <h3 id="rfc.section.6.6.4"><a href="#rfc.section.6.6.4">6.6.4</a> <a id="status.503" href="#status.503">503 Service Unavailable</a></h3> 2761 2764 <p id="rfc.section.6.6.4.p.1">The <dfn>503 (Service Unavailable)</dfn> status code indicates that the server is currently unable to handle the request due to a temporary overload or scheduled maintenance, … … 2767 2770 </p> 2768 2771 </div> 2769 <div id="rfc.iref.7 5"></div>2772 <div id="rfc.iref.76"></div> 2770 2773 <h3 id="rfc.section.6.6.5"><a href="#rfc.section.6.6.5">6.6.5</a> <a id="status.504" href="#status.504">504 Gateway Timeout</a></h3> 2771 2774 <p id="rfc.section.6.6.5.p.1">The <dfn>504 (Gateway Timeout)</dfn> status code indicates that the server, while acting as a gateway or proxy, did not receive a timely response from an upstream 2772 2775 server it needed to access in order to complete the request. 2773 2776 </p> 2774 <div id="rfc.iref.7 5"></div>2777 <div id="rfc.iref.76"></div> 2775 2778 <h3 id="rfc.section.6.6.6"><a href="#rfc.section.6.6.6">6.6.6</a> <a id="status.505" href="#status.505">505 HTTP Version Not Supported</a></h3> 2776 2779 <p id="rfc.section.6.6.6.p.1">The <dfn>505 (HTTP Version Not Supported)</dfn> status code indicates that the server does not support, or refuses to support, the protocol version that was used in the request … … 3037 3040 reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 7.2</a> of <a href="#Part6" id="rfc.xref.Part6.20"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching. 3038 3041 </p> 3039 <div id="rfc.iref.s.7"></div> 3040 <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a> <a id="selected.representation" href="#selected.representation">Selected Representation Header Fields</a></h2> 3041 <p id="rfc.section.7.2.p.1">We use the term "<dfn>selected representation</dfn>" to refer to the representation of the <a href="#resources" class="smpl">target resource</a> in a <a href="#status.200" class="smpl">200 (OK)</a> response to <a href="#GET" class="smpl">GET</a>, or the representation that would have been selected in a successful response if the request had used the method <a href="#GET" class="smpl">GET</a> and excluded any conditional request header fields. 3042 </p> 3043 <p id="rfc.section.7.2.p.2">The following header fields define metadata about the selected representation at the conclusion of handling the request. In 3044 other words, for a successful response to a state-changing method, these fields describe the new representation that has replaced 3045 the prior selected representation. For example, an ETag header field in a 201 response communicates the entity-tag of the 3046 newly created resource's representation, so that it can be used in later conditional requests to prevent the "lost update" 3047 problem <a href="#Part4" id="rfc.xref.Part4.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. 3042 <div id="rfc.iref.s.8"></div> 3043 <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a> <a id="response.validator" href="#response.validator">Validator Header Fields</a></h2> 3044 <p id="rfc.section.7.2.p.1">Validator header fields convey metadata about the <a href="#representations" class="smpl">selected representation</a> (<a href="#representations" title="Representations">Section 3</a>). In responses to safe requests, validator fields describe the selected representation chosen by the origin server while 3045 handling the response. Note that, depending on the status code semantics, the <a href="#representations" class="smpl">selected representation</a> for a given response is not necessarily the same as the representation enclosed as response payload. 3046 </p> 3047 <p id="rfc.section.7.2.p.2">In a successful response to a state-changing request, validator fields describe the new representation that has replaced the 3048 prior <a href="#representations" class="smpl">selected representation</a> as a result of processing the request. 3049 </p> 3050 <p id="rfc.section.7.2.p.3">For example, an ETag header field in a 201 response communicates the entity-tag of the newly created resource's representation, 3051 so that it can be used in later conditional requests to prevent the "lost update" problem <a href="#Part4" id="rfc.xref.Part4.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a>. 3048 3052 </p> 3049 3053 <div id="rfc.table.u.11"> … … 3129 3133 to the generic message handling rules. 3130 3134 </p> 3131 <div id="rfc.iref.s. 8"></div>3135 <div id="rfc.iref.s.9"></div> 3132 3136 <h3 id="rfc.section.7.4.2"><a href="#rfc.section.7.4.2">7.4.2</a> <a id="header.server" href="#header.server">Server</a></h3> 3133 3137 <p id="rfc.section.7.4.2.p.1">The "Server" header field contains information about the software used by the origin server to handle the request, which is … … 4395 4399 <ul class="ind"> 4396 4400 <li><a id="rfc.index.1" href="#rfc.index.1"><b>1</b></a><ul> 4397 <li>100 Continue (status code) <a href="#rfc.xref.status.100.1">5.1.1.1</a>, <a href="#rfc.xref.status.100.2">5.1.1.1</a>, <a href="#rfc.xref.status.100.3">6.1</a>, <a href="#rfc.iref.7 1"><b>6.2.1</b></a>, <a href="#rfc.xref.status.100.4">8.2.3</a></li>4398 <li>100-continue (expect value) <a href="#rfc.iref.4 4"><b>5.1.1.1</b></a></li>4399 <li>101 Switching Protocols (status code) <a href="#rfc.xref.status.101.1">6.1</a>, <a href="#rfc.iref.7 1"><b>6.2.2</b></a>, <a href="#rfc.xref.status.101.2">8.2.3</a></li>4400 <li>1xx Informational (status code class) <a href="#rfc.iref.7 0"><b>6.2</b></a></li>4401 <li>100 Continue (status code) <a href="#rfc.xref.status.100.1">5.1.1.1</a>, <a href="#rfc.xref.status.100.2">5.1.1.1</a>, <a href="#rfc.xref.status.100.3">6.1</a>, <a href="#rfc.iref.72"><b>6.2.1</b></a>, <a href="#rfc.xref.status.100.4">8.2.3</a></li> 4402 <li>100-continue (expect value) <a href="#rfc.iref.45"><b>5.1.1.1</b></a></li> 4403 <li>101 Switching Protocols (status code) <a href="#rfc.xref.status.101.1">6.1</a>, <a href="#rfc.iref.72"><b>6.2.2</b></a>, <a href="#rfc.xref.status.101.2">8.2.3</a></li> 4404 <li>1xx Informational (status code class) <a href="#rfc.iref.71"><b>6.2</b></a></li> 4401 4405 </ul> 4402 4406 </li> 4403 4407 <li><a id="rfc.index.2" href="#rfc.index.2"><b>2</b></a><ul> 4404 <li>200 OK (status code) <a href="#rfc.xref.status.200.1">6.1</a>, <a href="#rfc.iref.7 2"><b>6.3.1</b></a>, <a href="#rfc.xref.status.200.2">8.2.3</a></li>4405 <li>201 Created (status code) <a href="#rfc.xref.status.201.1">6.1</a>, <a href="#rfc.iref.7 2"><b>6.3.2</b></a>, <a href="#rfc.xref.status.201.2">8.2.3</a>, <a href="#rfc.xref.status.201.3">B</a></li>4406 <li>202 Accepted (status code) <a href="#rfc.xref.status.202.1">6.1</a>, <a href="#rfc.iref.7 2"><b>6.3.3</b></a>, <a href="#rfc.xref.status.202.2">8.2.3</a></li>4407 <li>203 Non-Authoritative Information (status code) <a href="#rfc.xref.status.203.1">6.1</a>, <a href="#rfc.iref.7 2"><b>6.3.4</b></a>, <a href="#rfc.xref.status.203.2">8.2.3</a>, <a href="#rfc.xref.status.203.3">B</a></li>4408 <li>204 No Content (status code) <a href="#rfc.xref.status.204.1">6.1</a>, <a href="#rfc.iref.7 2"><b>6.3.5</b></a>, <a href="#rfc.xref.status.204.2">8.2.3</a></li>4409 <li>205 Reset Content (status code) <a href="#rfc.xref.status.205.1">6.1</a>, <a href="#rfc.iref.7 2"><b>6.3.6</b></a>, <a href="#rfc.xref.status.205.2">8.2.3</a></li>4410 <li>2xx Successful (status code class) <a href="#rfc.iref.7 1"><b>6.3</b></a></li>4408 <li>200 OK (status code) <a href="#rfc.xref.status.200.1">6.1</a>, <a href="#rfc.iref.73"><b>6.3.1</b></a>, <a href="#rfc.xref.status.200.2">8.2.3</a></li> 4409 <li>201 Created (status code) <a href="#rfc.xref.status.201.1">6.1</a>, <a href="#rfc.iref.73"><b>6.3.2</b></a>, <a href="#rfc.xref.status.201.2">8.2.3</a>, <a href="#rfc.xref.status.201.3">B</a></li> 4410 <li>202 Accepted (status code) <a href="#rfc.xref.status.202.1">6.1</a>, <a href="#rfc.iref.73"><b>6.3.3</b></a>, <a href="#rfc.xref.status.202.2">8.2.3</a></li> 4411 <li>203 Non-Authoritative Information (status code) <a href="#rfc.xref.status.203.1">6.1</a>, <a href="#rfc.iref.73"><b>6.3.4</b></a>, <a href="#rfc.xref.status.203.2">8.2.3</a>, <a href="#rfc.xref.status.203.3">B</a></li> 4412 <li>204 No Content (status code) <a href="#rfc.xref.status.204.1">6.1</a>, <a href="#rfc.iref.73"><b>6.3.5</b></a>, <a href="#rfc.xref.status.204.2">8.2.3</a></li> 4413 <li>205 Reset Content (status code) <a href="#rfc.xref.status.205.1">6.1</a>, <a href="#rfc.iref.73"><b>6.3.6</b></a>, <a href="#rfc.xref.status.205.2">8.2.3</a></li> 4414 <li>2xx Successful (status code class) <a href="#rfc.iref.72"><b>6.3</b></a></li> 4411 4415 </ul> 4412 4416 </li> 4413 4417 <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul> 4414 <li>300 Multiple Choices (status code) <a href="#rfc.xref.status.300.1">6.1</a>, <a href="#rfc.iref.7 3"><b>6.4.1</b></a>, <a href="#rfc.xref.status.300.2">6.5.6</a>, <a href="#rfc.xref.status.300.3">8.2.3</a></li>4415 <li>301 Moved Permanently (status code) <a href="#rfc.xref.status.301.1">6.1</a>, <a href="#rfc.iref.7 3"><b>6.4.2</b></a>, <a href="#rfc.xref.status.301.2">8.2.3</a>, <a href="#rfc.xref.status.301.3">B</a></li>4416 <li>302 Found (status code) <a href="#rfc.xref.status.302.1">6.1</a>, <a href="#rfc.iref.7 3"><b>6.4.3</b></a>, <a href="#rfc.xref.status.302.2">8.2.3</a>, <a href="#rfc.xref.status.302.3">B</a></li>4417 <li>303 See Other (status code) <a href="#rfc.xref.status.303.1">6.1</a>, <a href="#rfc.iref.7 3"><b>6.4.4</b></a>, <a href="#rfc.xref.status.303.2">8.2.3</a>, <a href="#rfc.xref.status.303.3">B</a></li>4418 <li>305 Use Proxy (status code) <a href="#rfc.xref.status.305.1">6.1</a>, <a href="#rfc.iref.7 3"><b>6.4.5</b></a>, <a href="#rfc.xref.status.305.2">8.2.3</a>, <a href="#rfc.xref.status.305.3">B</a></li>4419 <li>306 (Unused) (status code) <a href="#rfc.iref.7 3"><b>6.4.6</b></a>, <a href="#rfc.xref.status.306.1">8.2.3</a></li>4420 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">6.1</a>, <a href="#rfc.iref.7 3"><b>6.4.7</b></a>, <a href="#rfc.xref.status.307.2">8.2.3</a></li>4421 <li>3xx Redirection (status code class) <a href="#rfc.iref.7 2"><b>6.4</b></a>, <a href="#rfc.xref.status.3xx.1">B</a>, <a href="#rfc.xref.status.3xx.2">B</a></li>4418 <li>300 Multiple Choices (status code) <a href="#rfc.xref.status.300.1">6.1</a>, <a href="#rfc.iref.74"><b>6.4.1</b></a>, <a href="#rfc.xref.status.300.2">6.5.6</a>, <a href="#rfc.xref.status.300.3">8.2.3</a></li> 4419 <li>301 Moved Permanently (status code) <a href="#rfc.xref.status.301.1">6.1</a>, <a href="#rfc.iref.74"><b>6.4.2</b></a>, <a href="#rfc.xref.status.301.2">8.2.3</a>, <a href="#rfc.xref.status.301.3">B</a></li> 4420 <li>302 Found (status code) <a href="#rfc.xref.status.302.1">6.1</a>, <a href="#rfc.iref.74"><b>6.4.3</b></a>, <a href="#rfc.xref.status.302.2">8.2.3</a>, <a href="#rfc.xref.status.302.3">B</a></li> 4421 <li>303 See Other (status code) <a href="#rfc.xref.status.303.1">6.1</a>, <a href="#rfc.iref.74"><b>6.4.4</b></a>, <a href="#rfc.xref.status.303.2">8.2.3</a>, <a href="#rfc.xref.status.303.3">B</a></li> 4422 <li>305 Use Proxy (status code) <a href="#rfc.xref.status.305.1">6.1</a>, <a href="#rfc.iref.74"><b>6.4.5</b></a>, <a href="#rfc.xref.status.305.2">8.2.3</a>, <a href="#rfc.xref.status.305.3">B</a></li> 4423 <li>306 (Unused) (status code) <a href="#rfc.iref.74"><b>6.4.6</b></a>, <a href="#rfc.xref.status.306.1">8.2.3</a></li> 4424 <li>307 Temporary Redirect (status code) <a href="#rfc.xref.status.307.1">6.1</a>, <a href="#rfc.iref.74"><b>6.4.7</b></a>, <a href="#rfc.xref.status.307.2">8.2.3</a></li> 4425 <li>3xx Redirection (status code class) <a href="#rfc.iref.73"><b>6.4</b></a>, <a href="#rfc.xref.status.3xx.1">B</a>, <a href="#rfc.xref.status.3xx.2">B</a></li> 4422 4426 </ul> 4423 4427 </li> 4424 4428 <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> 4425 <li>400 Bad Request (status code) <a href="#rfc.xref.status.400.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.1</b></a>, <a href="#rfc.xref.status.400.2">8.2.3</a>, <a href="#rfc.xref.status.400.3">B</a></li>4426 <li>402 Payment Required (status code) <a href="#rfc.xref.status.402.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.2</b></a>, <a href="#rfc.xref.status.402.2">8.2.3</a></li>4427 <li>403 Forbidden (status code) <a href="#rfc.xref.status.403.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.3</b></a>, <a href="#rfc.xref.status.403.2">8.2.3</a></li>4428 <li>404 Not Found (status code) <a href="#rfc.xref.status.404.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.4</b></a>, <a href="#rfc.xref.status.404.2">8.2.3</a></li>4429 <li>405 Method Not Allowed (status code) <a href="#rfc.xref.status.405.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.5</b></a>, <a href="#rfc.xref.status.405.2">8.2.3</a></li>4430 <li>406 Not Acceptable (status code) <a href="#rfc.xref.status.406.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.6</b></a>, <a href="#rfc.xref.status.406.2">8.2.3</a></li>4431 <li>408 Request Timeout (status code) <a href="#rfc.xref.status.408.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.7</b></a>, <a href="#rfc.xref.status.408.2">8.2.3</a></li>4432 <li>409 Conflict (status code) <a href="#rfc.xref.status.409.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.8</b></a>, <a href="#rfc.xref.status.409.2">8.2.3</a></li>4433 <li>410 Gone (status code) <a href="#rfc.xref.status.410.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.9</b></a>, <a href="#rfc.xref.status.410.2">8.2.3</a></li>4434 <li>411 Length Required (status code) <a href="#rfc.xref.status.411.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.10</b></a>, <a href="#rfc.xref.status.411.2">8.2.3</a></li>4435 <li>413 Payload Too Large (status code) <a href="#rfc.xref.status.413.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.11</b></a>, <a href="#rfc.xref.status.413.2">8.2.3</a></li>4436 <li>414 URI Too Long (status code) <a href="#rfc.xref.status.414.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.12</b></a>, <a href="#rfc.xref.status.414.2">8.2.3</a></li>4437 <li>415 Unsupported Media Type (status code) <a href="#rfc.xref.status.415.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.13</b></a>, <a href="#rfc.xref.status.415.2">8.2.3</a></li>4438 <li>417 Expectation Failed (status code) <a href="#rfc.xref.status.417.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.14</b></a>, <a href="#rfc.xref.status.417.2">8.2.3</a></li>4439 <li>426 Upgrade Required (status code) <a href="#rfc.xref.status.426.1">6.1</a>, <a href="#rfc.iref.7 4"><b>6.5.15</b></a>, <a href="#rfc.xref.status.426.2">8.2.3</a>, <a href="#rfc.xref.status.426.3">B</a></li>4440 <li>4xx Client Error (status code class) <a href="#rfc.iref.7 3"><b>6.5</b></a></li>4429 <li>400 Bad Request (status code) <a href="#rfc.xref.status.400.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.1</b></a>, <a href="#rfc.xref.status.400.2">8.2.3</a>, <a href="#rfc.xref.status.400.3">B</a></li> 4430 <li>402 Payment Required (status code) <a href="#rfc.xref.status.402.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.2</b></a>, <a href="#rfc.xref.status.402.2">8.2.3</a></li> 4431 <li>403 Forbidden (status code) <a href="#rfc.xref.status.403.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.3</b></a>, <a href="#rfc.xref.status.403.2">8.2.3</a></li> 4432 <li>404 Not Found (status code) <a href="#rfc.xref.status.404.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.4</b></a>, <a href="#rfc.xref.status.404.2">8.2.3</a></li> 4433 <li>405 Method Not Allowed (status code) <a href="#rfc.xref.status.405.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.5</b></a>, <a href="#rfc.xref.status.405.2">8.2.3</a></li> 4434 <li>406 Not Acceptable (status code) <a href="#rfc.xref.status.406.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.6</b></a>, <a href="#rfc.xref.status.406.2">8.2.3</a></li> 4435 <li>408 Request Timeout (status code) <a href="#rfc.xref.status.408.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.7</b></a>, <a href="#rfc.xref.status.408.2">8.2.3</a></li> 4436 <li>409 Conflict (status code) <a href="#rfc.xref.status.409.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.8</b></a>, <a href="#rfc.xref.status.409.2">8.2.3</a></li> 4437 <li>410 Gone (status code) <a href="#rfc.xref.status.410.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.9</b></a>, <a href="#rfc.xref.status.410.2">8.2.3</a></li> 4438 <li>411 Length Required (status code) <a href="#rfc.xref.status.411.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.10</b></a>, <a href="#rfc.xref.status.411.2">8.2.3</a></li> 4439 <li>413 Payload Too Large (status code) <a href="#rfc.xref.status.413.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.11</b></a>, <a href="#rfc.xref.status.413.2">8.2.3</a></li> 4440 <li>414 URI Too Long (status code) <a href="#rfc.xref.status.414.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.12</b></a>, <a href="#rfc.xref.status.414.2">8.2.3</a></li> 4441 <li>415 Unsupported Media Type (status code) <a href="#rfc.xref.status.415.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.13</b></a>, <a href="#rfc.xref.status.415.2">8.2.3</a></li> 4442 <li>417 Expectation Failed (status code) <a href="#rfc.xref.status.417.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.14</b></a>, <a href="#rfc.xref.status.417.2">8.2.3</a></li> 4443 <li>426 Upgrade Required (status code) <a href="#rfc.xref.status.426.1">6.1</a>, <a href="#rfc.iref.75"><b>6.5.15</b></a>, <a href="#rfc.xref.status.426.2">8.2.3</a>, <a href="#rfc.xref.status.426.3">B</a></li> 4444 <li>4xx Client Error (status code class) <a href="#rfc.iref.74"><b>6.5</b></a></li> 4441 4445 </ul> 4442 4446 </li> 4443 4447 <li><a id="rfc.index.5" href="#rfc.index.5"><b>5</b></a><ul> 4444 <li>500 Internal Server Error (status code) <a href="#rfc.xref.status.500.1">6.1</a>, <a href="#rfc.iref.7 5"><b>6.6.1</b></a>, <a href="#rfc.xref.status.500.2">8.2.3</a></li>4445 <li>501 Not Implemented (status code) <a href="#rfc.xref.status.501.1">6.1</a>, <a href="#rfc.iref.7 5"><b>6.6.2</b></a>, <a href="#rfc.xref.status.501.2">8.2.3</a></li>4446 <li>502 Bad Gateway (status code) <a href="#rfc.xref.status.502.1">6.1</a>, <a href="#rfc.iref.7 5"><b>6.6.3</b></a>, <a href="#rfc.xref.status.502.2">8.2.3</a></li>4447 <li>503 Service Unavailable (status code) <a href="#rfc.xref.status.503.1">6.1</a>, <a href="#rfc.iref.7 5"><b>6.6.4</b></a>, <a href="#rfc.xref.status.503.2">8.2.3</a></li>4448 <li>504 Gateway Timeout (status code) <a href="#rfc.xref.status.504.1">6.1</a>, <a href="#rfc.iref.7 5"><b>6.6.5</b></a>, <a href="#rfc.xref.status.504.2">8.2.3</a></li>4449 <li>505 HTTP Version Not Supported (status code) <a href="#rfc.xref.status.505.1">6.1</a>, <a href="#rfc.iref.7 5"><b>6.6.6</b></a>, <a href="#rfc.xref.status.505.2">8.2.3</a></li>4450 <li>5xx Server Error (status code class) <a href="#rfc.iref.7 4"><b>6.6</b></a></li>4448 <li>500 Internal Server Error (status code) <a href="#rfc.xref.status.500.1">6.1</a>, <a href="#rfc.iref.76"><b>6.6.1</b></a>, <a href="#rfc.xref.status.500.2">8.2.3</a></li> 4449 <li>501 Not Implemented (status code) <a href="#rfc.xref.status.501.1">6.1</a>, <a href="#rfc.iref.76"><b>6.6.2</b></a>, <a href="#rfc.xref.status.501.2">8.2.3</a></li> 4450 <li>502 Bad Gateway (status code) <a href="#rfc.xref.status.502.1">6.1</a>, <a href="#rfc.iref.76"><b>6.6.3</b></a>, <a href="#rfc.xref.status.502.2">8.2.3</a></li> 4451 <li>503 Service Unavailable (status code) <a href="#rfc.xref.status.503.1">6.1</a>, <a href="#rfc.iref.76"><b>6.6.4</b></a>, <a href="#rfc.xref.status.503.2">8.2.3</a></li> 4452 <li>504 Gateway Timeout (status code) <a href="#rfc.xref.status.504.1">6.1</a>, <a href="#rfc.iref.76"><b>6.6.5</b></a>, <a href="#rfc.xref.status.504.2">8.2.3</a></li> 4453 <li>505 HTTP Version Not Supported (status code) <a href="#rfc.xref.status.505.1">6.1</a>, <a href="#rfc.iref.76"><b>6.6.6</b></a>, <a href="#rfc.xref.status.505.2">8.2.3</a></li> 4454 <li>5xx Server Error (status code class) <a href="#rfc.iref.75"><b>6.6</b></a></li> 4451 4455 </ul> 4452 4456 </li> … … 4497 4501 </li> 4498 4502 <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul> 4499 <li>GET method <a href="#rfc. xref.GET.1">3.3</a>, <a href="#rfc.xref.GET.2">4.1</a>, <a href="#rfc.iref.g.16"><b>4.3.1</b></a>, <a href="#rfc.extref.g.4">7.2</a>, <a href="#rfc.extref.g.5">7.2</a>, <a href="#rfc.xref.GET.3">8.1.3</a>, <a href="#rfc.xref.GET.4">B</a></li>4503 <li>GET method <a href="#rfc.extref.g.1">3</a>, <a href="#rfc.extref.g.2">3</a>, <a href="#rfc.xref.GET.1">3.3</a>, <a href="#rfc.xref.GET.2">4.1</a>, <a href="#rfc.iref.g.16"><b>4.3.1</b></a>, <a href="#rfc.xref.GET.3">8.1.3</a>, <a href="#rfc.xref.GET.4">B</a></li> 4500 4504 <li><tt>Grammar</tt> 4501 4505 <ul> … … 4669 4673 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 4670 4674 <li>Referer header field <a href="#rfc.xref.header.referer.1">5.5</a>, <a href="#rfc.iref.r.2"><b>5.5.2</b></a>, <a href="#rfc.xref.header.referer.2">8.3.2</a>, <a href="#rfc.xref.header.referer.3">9.3</a>, <a href="#rfc.xref.header.referer.4">B</a></li> 4671 <li>representation <a href="#rfc.iref.r.1"> 3</a></li>4675 <li>representation <a href="#rfc.iref.r.1"><b>3</b></a></li> 4672 4676 <li><em>REST</em> <a href="#rfc.xref.REST.1">3</a>, <a href="#rfc.xref.REST.2">4.1</a>, <a href="#REST"><b>11.2</b></a></li> 4673 4677 <li>Retry-After header field <a href="#rfc.xref.header.retry-after.1">6.6.4</a>, <a href="#rfc.xref.header.retry-after.2">7.1</a>, <a href="#rfc.iref.r.3"><b>7.1.3</b></a>, <a href="#rfc.xref.header.retry-after.3">8.3.2</a></li> … … 4749 4753 </li> 4750 4754 <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul> 4751 <li>safe <a href="#rfc.iref.s. 1"><b>4.2.1</b></a></li>4752 <li>selected representation <a href="#rfc.iref.s. 7"><b>7.2</b></a></li>4753 <li>Server header field <a href="#rfc.xref.header.server.1">7.4</a>, <a href="#rfc.iref.s. 8"><b>7.4.2</b></a>, <a href="#rfc.xref.header.server.2">8.3.2</a>, <a href="#rfc.xref.header.server.3">9.4</a></li>4755 <li>safe <a href="#rfc.iref.s.2"><b>4.2.1</b></a></li> 4756 <li>selected representation <a href="#rfc.iref.s.1"><b>3</b></a>, <a href="#rfc.iref.s.8">7.2</a></li> 4757 <li>Server header field <a href="#rfc.xref.header.server.1">7.4</a>, <a href="#rfc.iref.s.9"><b>7.4.2</b></a>, <a href="#rfc.xref.header.server.2">8.3.2</a>, <a href="#rfc.xref.header.server.3">9.4</a></li> 4754 4758 <li>Status Codes Classes 4755 4759 <ul> 4756 <li>1xx Informational <a href="#rfc.iref.s. 2"><b>6.2</b></a></li>4757 <li>2xx Successful <a href="#rfc.iref.s. 3"><b>6.3</b></a></li>4758 <li>3xx Redirection <a href="#rfc.iref.s. 4"><b>6.4</b></a>, <a href="#rfc.xref.status.3xx.1">B</a>, <a href="#rfc.xref.status.3xx.2">B</a></li>4759 <li>4xx Client Error <a href="#rfc.iref.s. 5"><b>6.5</b></a></li>4760 <li>5xx Server Error <a href="#rfc.iref.s. 6"><b>6.6</b></a></li>4760 <li>1xx Informational <a href="#rfc.iref.s.3"><b>6.2</b></a></li> 4761 <li>2xx Successful <a href="#rfc.iref.s.4"><b>6.3</b></a></li> 4762 <li>3xx Redirection <a href="#rfc.iref.s.5"><b>6.4</b></a>, <a href="#rfc.xref.status.3xx.1">B</a>, <a href="#rfc.xref.status.3xx.2">B</a></li> 4763 <li>4xx Client Error <a href="#rfc.iref.s.6"><b>6.5</b></a></li> 4764 <li>5xx Server Error <a href="#rfc.iref.s.7"><b>6.6</b></a></li> 4761 4765 </ul> 4762 4766 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2108 r2110 286 286 287 287 <section title="Representations" anchor="representations"> 288 <iref item="representation"/> 288 <iref primary="true" item="representation"/> 289 <iref primary="true" item="selected representation"/> 290 <x:anchor-alias value="representation"/> 291 <x:anchor-alias value="selected representation"/> 289 292 <t> 290 293 If we consider that a resource could be anything, and that the uniform … … 302 305 and that consists of a set of representation metadata and a potentially 303 306 unbounded stream of representation data. 307 </t> 308 <t> 309 We use the term "<x:dfn>selected representation</x:dfn>" to refer to the 310 representation of the <x:ref>target resource</x:ref> in a 311 <x:ref>200 (OK)</x:ref> response to <x:ref>GET</x:ref>, or the 312 representation that would have been selected in a successful response if 313 the request had used the method <x:ref>GET</x:ref> and excluded any 314 conditional request header fields. 304 315 </t> 305 316 … … 2768 2779 <t> 2769 2780 The 201 response payload typically describes and links to the resource(s) 2770 created. See <xref target=" selected.representation"/> fordiscussion of the2771 meaning and purpose of selected representationheader fields, such as2781 created. See <xref target="response.validator"/> for a discussion of the 2782 meaning and purpose of validator header fields, such as 2772 2783 <x:ref>ETag</x:ref> and <x:ref>Last-Modified</x:ref>, in a 201 response. 2773 2784 </t> … … 3941 3952 </section> 3942 3953 3943 <section title="Selected Representation Header Fields" anchor="selected.representation"> 3944 <iref primary="true" item="selected representation"/> 3945 <x:anchor-alias value="selected representation"/> 3946 <t> 3947 We use the term "<x:dfn>selected representation</x:dfn>" to refer to the 3948 representation of the <x:ref>target resource</x:ref> in a 3949 <x:ref>200 (OK)</x:ref> response to <x:ref>GET</x:ref>, or the 3950 representation that would have been selected in a successful response if 3951 the request had used the method <x:ref>GET</x:ref> and excluded any 3952 conditional request header fields. 3953 </t> 3954 <t> 3955 The following header fields define metadata about the selected 3956 representation at the conclusion of handling the request. In other words, 3957 for a successful response to a state-changing method, these fields describe 3958 the new representation that has replaced the prior selected representation. 3954 <section title="Validator Header Fields" anchor="response.validator"> 3955 <iref item="selected representation"/> 3956 <t> 3957 Validator header fields convey metadata about the 3958 <x:ref>selected representation</x:ref> (<xref target="representations"/>). 3959 In responses to safe requests, validator fields describe the selected 3960 representation chosen by the origin server while handling the response. 3961 Note that, depending on the status code semantics, the 3962 <x:ref>selected representation</x:ref> for a given response is not 3963 necessarily the same as the representation enclosed as response payload. 3964 </t> 3965 <t> 3966 In a successful response to a state-changing request, validator fields 3967 describe the new representation that has replaced the prior 3968 <x:ref>selected representation</x:ref> as a result of processing the 3969 request. 3970 </t> 3971 <t> 3959 3972 For example, an ETag header field in a 201 response communicates the 3960 3973 entity-tag of the newly created resource's representation, so that it can
Note: See TracChangeset
for help on using the changeset viewer.
