![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 1042 for draft-ietf-httpbis/latest
- Timestamp:
- 22/10/10 02:05:57 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
-
p2-semantics.html (modified) (16 diffs)
-
p2-semantics.xml (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1040 r1042 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2010-10-2 0">405 <meta name="dct.issued" scheme="ISO8601" content="2010-10-22"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: April 2 3, 2011</td>436 <td class="left">Expires: April 25, 2011</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">October 2 0, 2010</td>489 <td class="right">October 22, 2010</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire on April 2 3, 2011.</p>516 <p>This Internet-Draft will expire on April 25, 2011.</p> 517 517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518 518 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 796 796 and currently defined methods are inadequate, it may be appropriate to register a new method. 797 797 </p> 798 <p id="rfc.section.2.1.1.p.2">New methods <em class="bcp14">SHOULD</em> be potentially applicable to any resource. I.e., they should not be specific to any particular media type, "type" of resource, 799 or application. 798 <p id="rfc.section.2.1.1.p.2">HTTP methods are generic; that is, they are potentially applicable to any resource, not just one particular media type, "type" 799 of resource, or application. As such, it is preferred that new HTTP methods be registered in a document that isn't specific 800 to a single application, so that this is clear. 800 801 </p> 801 802 <p id="rfc.section.2.1.1.p.3">Due to the parsing rules defined in <a href="p1-messaging.html#message.body" title="Message Body">Section 3.3</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, definitions of HTTP methods cannot prohibit the presence of a message-body on either the request or the response message … … 803 804 can specify that only zero-length bodies (as opposed to absent bodies) are allowed. 804 805 </p> 805 <p id="rfc.section.2.1.1.p.4">New method s <em class="bcp14">MUST</em> define whether they are safe (<a href="#safe.methods" title="Safe Methods">Section 7.1.1</a>) and whether they are idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section 7.1.2</a>). They <em class="bcp14">MUST</em> also state whether they can be cached (<a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>); in particular what conditions a cache may store the response, and under what conditions such a stored response may be used806 <p id="rfc.section.2.1.1.p.4">New method definitions need to indicate whether they are safe (<a href="#safe.methods" title="Safe Methods">Section 7.1.1</a>) and whether they are idempotent (<a href="#idempotent.methods" title="Idempotent Methods">Section 7.1.2</a>). They also need to state whether they can be cached (<a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>); in particular what conditions a cache may store the response, and under what conditions such a stored response may be used 806 807 to satisfy a subsequent request. 807 </p>808 <p id="rfc.section.2.1.1.p.5">New methods <em class="bcp14">SHOULD</em> explain how conditional request headers (<a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>) affect the response (if there is any effect).809 </p>810 <p id="rfc.section.2.1.1.p.6">HTTP methods <em class="bcp14">SHOULD</em> be registered in a document that isn't specific to a single application or other use of HTTP, so that it's clear that they811 are not specific to that application or extension.812 808 </p> 813 809 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="request.header.fields" href="#request.header.fields">Request Header Fields</a></h1> … … 824 820 / <a href="#header.from" class="smpl">From</a> ; <a href="#header.from" id="rfc.xref.header.from.1" title="From">Section 9.3</a> 825 821 / <a href="#abnf.dependencies" class="smpl">Host</a> ; <a href="#Part1" id="rfc.xref.Part1.19"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#header.host" title="Host">Section 9.4</a> 826 / <a href="#abnf.dependencies" class="smpl">If-Match</a> ; <a href="#Part4" id="rfc.xref.Part4. 7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a>827 / <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> ; <a href="#Part4" id="rfc.xref.Part4. 8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a>828 / <a href="#abnf.dependencies" class="smpl">If-None-Match</a> ; <a href="#Part4" id="rfc.xref.Part4. 9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a>822 / <a href="#abnf.dependencies" class="smpl">If-Match</a> ; <a href="#Part4" id="rfc.xref.Part4.6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-match" title="If-Match">Section 6.2</a> 823 / <a href="#abnf.dependencies" class="smpl">If-Modified-Since</a> ; <a href="#Part4" id="rfc.xref.Part4.7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-modified-since" title="If-Modified-Since">Section 6.3</a> 824 / <a href="#abnf.dependencies" class="smpl">If-None-Match</a> ; <a href="#Part4" id="rfc.xref.Part4.8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-none-match" title="If-None-Match">Section 6.4</a> 829 825 / <a href="#abnf.dependencies" class="smpl">If-Range</a> ; <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> 830 / <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a> ; <a href="#Part4" id="rfc.xref.Part4. 10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a>826 / <a href="#abnf.dependencies" class="smpl">If-Unmodified-Since</a> ; <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.if-unmodified-since" title="If-Unmodified-Since">Section 6.5</a> 831 827 / <a href="#header.max-forwards" class="smpl">Max-Forwards</a> ; <a href="#header.max-forwards" id="rfc.xref.header.max-forwards.1" title="Max-Forwards">Section 9.5</a> 832 828 / <a href="#abnf.dependencies" class="smpl">Proxy-Authorization</a> ; <a href="#Part7" id="rfc.xref.Part7.6"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> … … 840 836 <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> <a id="status.code.and.reason.phrase" href="#status.code.and.reason.phrase">Status Code and Reason Phrase</a></h1> 841 837 <p id="rfc.section.4.p.1">The Status-Code element is a 3-digit integer result code of the attempt to understand and satisfy the request. The status 842 codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section 8</a>, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part4" id="rfc.xref.Part4.1 1"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>.838 codes listed below are defined in <a href="#status.codes" title="Status Code Definitions">Section 8</a>, <a href="p4-conditional.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part4" id="rfc.xref.Part4.10"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p5-range.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part5" id="rfc.xref.Part5.6"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>, and <a href="p7-auth.html#status.code.definitions" title="Status Code Definitions">Section 3</a> of <a href="#Part7" id="rfc.xref.Part7.7"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>. 843 839 </p> 844 840 <p id="rfc.section.4.p.2">The Reason-Phrase is intended to give a short textual description of the Status-Code. The Status-Code is intended for use … … 862 858 / "302" ; <a href="#status.302" id="rfc.xref.status.302.1" title="302 Found">Section 8.3.3</a>: Found 863 859 / "303" ; <a href="#status.303" id="rfc.xref.status.303.1" title="303 See Other">Section 8.3.4</a>: See Other 864 / "304" ; <a href="#Part4" id="rfc.xref.Part4.1 2"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a>: Not Modified860 / "304" ; <a href="#Part4" id="rfc.xref.Part4.11"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a>: Not Modified 865 861 / "305" ; <a href="#status.305" id="rfc.xref.status.305.1" title="305 Use Proxy">Section 8.3.6</a>: Use Proxy 866 862 / "307" ; <a href="#status.307" id="rfc.xref.status.307.1" title="307 Temporary Redirect">Section 8.3.8</a>: Temporary Redirect … … 877 873 / "410" ; <a href="#status.410" id="rfc.xref.status.410.1" title="410 Gone">Section 8.4.11</a>: Gone 878 874 / "411" ; <a href="#status.411" id="rfc.xref.status.411.1" title="411 Length Required">Section 8.4.12</a>: Length Required 879 / "412" ; <a href="#Part4" id="rfc.xref.Part4.1 3"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a>: Precondition Failed875 / "412" ; <a href="#Part4" id="rfc.xref.Part4.12"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a>: Precondition Failed 880 876 / "413" ; <a href="#status.413" id="rfc.xref.status.413.1" title="413 Request Entity Too Large">Section 8.4.14</a>: Request Entity Too Large 881 877 / "414" ; <a href="#status.414" id="rfc.xref.status.414.1" title="414 URI Too Long">Section 8.4.15</a>: URI Too Long … … 926 922 / <a href="#abnf.dependencies" class="smpl">Age</a> ; <a href="#Part6" id="rfc.xref.Part6.5"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>, <a href="p6-cache.html#header.age" title="Age">Section 3.1</a> 927 923 / <a href="#header.allow" class="smpl">Allow</a> ; <a href="#header.allow" id="rfc.xref.header.allow.2" title="Allow">Section 9.1</a> 928 / <a href="#abnf.dependencies" class="smpl">ETag</a> ; <a href="#Part4" id="rfc.xref.Part4.1 4"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a>924 / <a href="#abnf.dependencies" class="smpl">ETag</a> ; <a href="#Part4" id="rfc.xref.Part4.13"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>, <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> 929 925 / <a href="#header.location" class="smpl">Location</a> ; <a href="#header.location" id="rfc.xref.header.location.1" title="Location">Section 9.4</a> 930 926 / <a href="#abnf.dependencies" class="smpl">Proxy-Authenticate</a> ; <a href="#Part7" id="rfc.xref.Part7.10"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, <a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> … … 1202 1198 </p> 1203 1199 <p id="rfc.section.8.2.2.p.2">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity-tag for the representation of the resource 1204 just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.1 5"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).1200 just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 6.1</a> of <a href="#Part4" id="rfc.xref.Part4.14"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>). 1205 1201 </p> 1206 1202 <div id="rfc.iref.29"></div> … … 1337 1333 <h3 id="rfc.section.8.3.5"><a href="#rfc.section.8.3.5">8.3.5</a> <a id="status.304" href="#status.304">304 Not Modified</a></h3> 1338 1334 <p id="rfc.section.8.3.5.p.1">The response to the request has not been modified since the conditions indicated by the client's conditional GET request, 1339 as defined in <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.1 6"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.1335 as defined in <a href="p4-conditional.html#status.304" title="304 Not Modified">Section 3.1</a> of <a href="#Part4" id="rfc.xref.Part4.15"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1340 1336 </p> 1341 1337 <div id="rfc.iref.39"></div> … … 1469 1465 <h3 id="rfc.section.8.4.13"><a href="#rfc.section.8.4.13">8.4.13</a> <a id="status.412" href="#status.412">412 Precondition Failed</a></h3> 1470 1466 <p id="rfc.section.8.4.13.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server, as 1471 defined in <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.1 7"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>.1467 defined in <a href="p4-conditional.html#status.412" title="412 Precondition Failed">Section 3.2</a> of <a href="#Part4" id="rfc.xref.Part4.16"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>. 1472 1468 </p> 1473 1469 <div id="rfc.iref.55"></div> … … 2460 2456 <p id="rfc.section.C.2.p.2">Other changes: </p> 2461 2457 <ul> 2462 <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.1 8"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>2458 <li>Move definitions of 304 and 412 condition codes to <a href="#Part4" id="rfc.xref.Part4.17"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a> 2463 2459 </li> 2464 2460 </ul> … … 2819 2815 </ul> 2820 2816 </li> 2821 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.6"> 2.1.1</a>, <a class="iref" href="#rfc.xref.Part4.7">3</a>, <a class="iref" href="#rfc.xref.Part4.8">3</a>, <a class="iref" href="#rfc.xref.Part4.9">3</a>, <a class="iref" href="#rfc.xref.Part4.10">3</a>, <a class="iref" href="#rfc.xref.Part4.11">4</a>, <a class="iref" href="#rfc.xref.Part4.12">4</a>, <a class="iref" href="#rfc.xref.Part4.13">4</a>, <a class="iref" href="#rfc.xref.Part4.14">5</a>, <a class="iref" href="#rfc.xref.Part4.15">8.2.2</a>, <a class="iref" href="#rfc.xref.Part4.16">8.3.5</a>, <a class="iref" href="#rfc.xref.Part4.17">8.4.13</a>, <a class="iref" href="#Part4"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part4.18">C.2</a><ul class="ind">2822 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part4.1 1">4</a></li>2823 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part4.1 2">4</a>, <a class="iref" href="#rfc.xref.Part4.16">8.3.5</a></li>2824 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part4.1 3">4</a>, <a class="iref" href="#rfc.xref.Part4.17">8.4.13</a></li>2825 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.1 4">5</a>, <a class="iref" href="#rfc.xref.Part4.15">8.2.2</a></li>2826 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part4.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4. 7">3</a></li>2827 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part4.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4. 8">3</a></li>2828 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part4.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4. 9">3</a></li>2829 <li class="indline1"><em>Section 6.5</em> <a class="iref" href="#rfc.xref.Part4.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4. 10">3</a></li>2817 <li class="indline1"><em>Part4</em> <a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.6">3</a>, <a class="iref" href="#rfc.xref.Part4.7">3</a>, <a class="iref" href="#rfc.xref.Part4.8">3</a>, <a class="iref" href="#rfc.xref.Part4.9">3</a>, <a class="iref" href="#rfc.xref.Part4.10">4</a>, <a class="iref" href="#rfc.xref.Part4.11">4</a>, <a class="iref" href="#rfc.xref.Part4.12">4</a>, <a class="iref" href="#rfc.xref.Part4.13">5</a>, <a class="iref" href="#rfc.xref.Part4.14">8.2.2</a>, <a class="iref" href="#rfc.xref.Part4.15">8.3.5</a>, <a class="iref" href="#rfc.xref.Part4.16">8.4.13</a>, <a class="iref" href="#Part4"><b>13.1</b></a>, <a class="iref" href="#rfc.xref.Part4.17">C.2</a><ul class="ind"> 2818 <li class="indline1"><em>Section 3</em> <a class="iref" href="#rfc.xref.Part4.10">4</a></li> 2819 <li class="indline1"><em>Section 3.1</em> <a class="iref" href="#rfc.xref.Part4.11">4</a>, <a class="iref" href="#rfc.xref.Part4.15">8.3.5</a></li> 2820 <li class="indline1"><em>Section 3.2</em> <a class="iref" href="#rfc.xref.Part4.12">4</a>, <a class="iref" href="#rfc.xref.Part4.16">8.4.13</a></li> 2821 <li class="indline1"><em>Section 6.1</em> <a class="iref" href="#rfc.xref.Part4.1">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.13">5</a>, <a class="iref" href="#rfc.xref.Part4.14">8.2.2</a></li> 2822 <li class="indline1"><em>Section 6.2</em> <a class="iref" href="#rfc.xref.Part4.2">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.6">3</a></li> 2823 <li class="indline1"><em>Section 6.3</em> <a class="iref" href="#rfc.xref.Part4.3">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.7">3</a></li> 2824 <li class="indline1"><em>Section 6.4</em> <a class="iref" href="#rfc.xref.Part4.4">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.8">3</a></li> 2825 <li class="indline1"><em>Section 6.5</em> <a class="iref" href="#rfc.xref.Part4.5">1.2.2</a>, <a class="iref" href="#rfc.xref.Part4.9">3</a></li> 2830 2826 </ul> 2831 2827 </li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1040 r1042 489 489 </t> 490 490 <t> 491 New methods &SHOULD; be potentially applicable to any resource. I.e., 492 they should not be specific to any particular media type, "type" of 493 resource, or application. 491 HTTP methods are generic; that is, they are potentially applicable to any 492 resource, not just one particular media type, "type" of resource, or 493 application. As such, it is preferred that new HTTP methods be registered 494 in a document that isn't specific to a single application, so that this is 495 clear. 494 496 </t> 495 497 <t> … … 501 503 </t> 502 504 <t> 503 New method s &MUST; define whether they are safe (<xref505 New method definitions need to indicate whether they are safe (<xref 504 506 target="safe.methods"/>) and whether they are idempotent (<xref 505 target="idempotent.methods"/>). They &MUST; also state whether they can be507 target="idempotent.methods"/>). They also need to state whether they can be 506 508 cached (&caching;); in particular what conditions a cache may store the 507 509 response, and under what conditions such a stored response may be used to 508 510 satisfy a subsequent request. 509 </t>510 <t>511 New methods &SHOULD; explain how conditional request headers512 (&conditional;) affect the response (if there is any effect).513 </t>514 <t>515 HTTP methods &SHOULD; be registered in a document that isn't specific to516 a single application or other use of HTTP, so that it's clear that they are517 not specific to that application or extension.518 511 </t> 519 512 </section>
Note: See TracChangeset
for help on using the changeset viewer.
