Changeset 1799
- Timestamp:
- 16/07/12 06:22:34 (9 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 9 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p0-introduction.html
r1798 r1799 393 393 } 394 394 @bottom-center { 395 content: "Expires January 1 7, 2013";395 content: "Expires January 16, 2013"; 396 396 } 397 397 @bottom-right { … … 426 426 <meta name="dct.creator" content="Reschke, J. F."> 427 427 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest"> 428 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 6">428 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 429 429 <meta name="dct.abstract" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1."> 430 430 <meta name="description" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1."> … … 446 446 </tr> 447 447 <tr> 448 <td class="left">Expires: January 1 7, 2013</td>448 <td class="left">Expires: January 16, 2013</td> 449 449 <td class="right">W3C</td> 450 450 </tr> … … 467 467 <tr> 468 468 <td class="left"></td> 469 <td class="right">July 1 6, 2012</td>469 <td class="right">July 15, 2012</td> 470 470 </tr> 471 471 </tbody> … … 490 490 in progress”. 491 491 </p> 492 <p>This Internet-Draft will expire on January 1 7, 2013.</p>492 <p>This Internet-Draft will expire on January 16, 2013.</p> 493 493 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 494 494 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p1-messaging.html
r1798 r1799 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 7, 2013";451 content: "Expires January 16, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 6">494 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2145"> 496 496 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: January 1 7, 2013</td>526 <td class="left">Expires: January 16, 2013</td> 527 527 <td class="right">greenbytes</td> 528 528 </tr> 529 529 <tr> 530 530 <td class="left"></td> 531 <td class="right">July 1 6, 2012</td>531 <td class="right">July 15, 2012</td> 532 532 </tr> 533 533 </tbody> … … 556 556 in progress”. 557 557 </p> 558 <p>This Internet-Draft will expire on January 1 7, 2013.</p>558 <p>This Internet-Draft will expire on January 16, 2013.</p> 559 559 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 560 560 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p2-semantics.html
r1798 r1799 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 7, 2013";451 content: "Expires January 16, 2013"; 452 452 } 453 453 @bottom-right { … … 497 497 <meta name="dct.creator" content="Reschke, J. F."> 498 498 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 499 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 6">499 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 500 500 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 501 501 <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."> … … 528 528 </tr> 529 529 <tr> 530 <td class="left">Expires: January 1 7, 2013</td>530 <td class="left">Expires: January 16, 2013</td> 531 531 <td class="right">greenbytes</td> 532 532 </tr> 533 533 <tr> 534 534 <td class="left"></td> 535 <td class="right">July 1 6, 2012</td>535 <td class="right">July 15, 2012</td> 536 536 </tr> 537 537 </tbody> … … 560 560 in progress”. 561 561 </p> 562 <p>This Internet-Draft will expire on January 1 7, 2013.</p>562 <p>This Internet-Draft will expire on January 16, 2013.</p> 563 563 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 564 564 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p3-payload.html
r1798 r1799 374 374 } 375 375 @bottom-center { 376 content: "Expires January 1 7, 2013";376 content: "Expires January 16, 2013"; 377 377 } 378 378 @bottom-right { … … 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 6">406 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 407 407 <meta name="dct.abstract" content="This part is now obsolete. Please see HTTPbis, Part 2."> 408 408 <meta name="description" content="This part is now obsolete. Please see HTTPbis, Part 2."> … … 424 424 </tr> 425 425 <tr> 426 <td class="left">Expires: January 1 7, 2013</td>426 <td class="left">Expires: January 16, 2013</td> 427 427 <td class="right">W3C</td> 428 428 </tr> … … 437 437 <tr> 438 438 <td class="left"></td> 439 <td class="right">July 1 6, 2012</td>439 <td class="right">July 15, 2012</td> 440 440 </tr> 441 441 </tbody> … … 453 453 in progress”. 454 454 </p> 455 <p>This Internet-Draft will expire on January 1 7, 2013.</p>455 <p>This Internet-Draft will expire on January 16, 2013.</p> 456 456 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 457 457 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p4-conditional.html
r1796 r1799 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 7, 2013";451 content: "Expires January 16, 2013"; 452 452 } 453 453 @bottom-right { … … 475 475 <link rel="Chapter" title="3 Precondition Header Fields" href="#rfc.section.3"> 476 476 <link rel="Chapter" title="4 Status Code Definitions" href="#rfc.section.4"> 477 <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5"> 478 <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6"> 479 <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7"> 480 <link rel="Chapter" href="#rfc.section.8" title="8 References"> 477 <link rel="Chapter" title="5 Precedence" href="#rfc.section.5"> 478 <link rel="Chapter" title="6 IANA Considerations" href="#rfc.section.6"> 479 <link rel="Chapter" title="7 Security Considerations" href="#rfc.section.7"> 480 <link rel="Chapter" title="8 Acknowledgments" href="#rfc.section.8"> 481 <link rel="Chapter" href="#rfc.section.9" title="9 References"> 481 482 <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A"> 482 483 <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B"> … … 490 491 <meta name="dct.creator" content="Reschke, J. F."> 491 492 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 492 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 6">493 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 493 494 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 494 495 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false."> … … 516 517 </tr> 517 518 <tr> 518 <td class="left">Expires: January 1 7, 2013</td>519 <td class="left">Expires: January 16, 2013</td> 519 520 <td class="right">J. Reschke, Editor</td> 520 521 </tr> … … 525 526 <tr> 526 527 <td class="left"></td> 527 <td class="right">July 1 6, 2012</td>528 <td class="right">July 15, 2012</td> 528 529 </tr> 529 530 </tbody> … … 552 553 in progress”. 553 554 </p> 554 <p>This Internet-Draft will expire on January 1 7, 2013.</p>555 <p>This Internet-Draft will expire on January 16, 2013.</p> 555 556 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 556 557 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 604 605 </ul> 605 606 </li> 606 <li>5. <a href="#IANA.considerations">IANA Considerations</a><ul> 607 <li>5.1 <a href="#status.code.registration">Status Code Registration</a></li> 608 <li>5.2 <a href="#header.field.registration">Header Field Registration</a></li> 607 <li>5. <a href="#precedence">Precedence</a></li> 608 <li>6. <a href="#IANA.considerations">IANA Considerations</a><ul> 609 <li>6.1 <a href="#status.code.registration">Status Code Registration</a></li> 610 <li>6.2 <a href="#header.field.registration">Header Field Registration</a></li> 609 611 </ul> 610 612 </li> 611 <li> 6. <a href="#security.considerations">Security Considerations</a></li>612 <li> 7. <a href="#acks">Acknowledgments</a></li>613 <li> 8. <a href="#rfc.references">References</a><ul>614 <li> 8.1 <a href="#rfc.references.1">Normative References</a></li>615 <li> 8.2 <a href="#rfc.references.2">Informative References</a></li>613 <li>7. <a href="#security.considerations">Security Considerations</a></li> 614 <li>8. <a href="#acks">Acknowledgments</a></li> 615 <li>9. <a href="#rfc.references">References</a><ul> 616 <li>9.1 <a href="#rfc.references.1">Normative References</a></li> 617 <li>9.2 <a href="#rfc.references.2">Informative References</a></li> 616 618 </ul> 617 619 </li> … … 968 970 </ul> 969 971 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="header.field.definitions" href="#header.field.definitions">Precondition Header Fields</a></h1> 970 <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields for applying preconditions on requests.</p> 972 <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields for applying preconditions on requests. <a href="#precedence" title="Precedence">Section 5</a> defines the order of evaluation when more than one precondition is present in a request. 973 </p> 971 974 <div id="rfc.iref.i.1"></div> 972 975 <div id="rfc.iref.h.3"></div> … … 996 999 If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz" 997 1000 If-Match: * 998 </pre><p id="rfc.section.3.1.p.11">The result of a request having both an If-Match header field and either an <a href="#header.if-none-match" class="smpl">If-None-Match</a> or an <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> header field is undefined by this specification. 999 </p> 1000 <div id="rfc.iref.i.2"></div> 1001 </pre><div id="rfc.iref.i.2"></div> 1001 1002 <div id="rfc.iref.h.4"></div> 1002 1003 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="header.if-none-match" href="#header.if-none-match">If-None-Match</a></h2> … … 1032 1033 If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz" 1033 1034 If-None-Match: * 1034 </pre><p id="rfc.section.3.2.p.11">The result of a request having both an If-None-Match header field and either an <a href="#header.if-match" class="smpl">If-Match</a> or an <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> header field is undefined by this specification. 1035 </p> 1036 <div id="rfc.iref.i.3"></div> 1035 </pre><div id="rfc.iref.i.3"></div> 1037 1036 <div id="rfc.iref.h.5"></div> 1038 1037 <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> <a id="header.if-modified-since" href="#header.if-modified-since">If-Modified-Since</a></h2> 1039 <p id="rfc.section.3.3.p.1">The "If-Modified-Since" header field can be used to make a request method conditional by modification date: if the selected1040 representation has not been modified since the time specified in this field, then do not perform the request method; instead,1041 respond as detailed below.1038 <p id="rfc.section.3.3.p.1">The "If-Modified-Since" header field can be used with GET or HEAD to make the method conditional by modification date: if 1039 the selected representation has not been modified since the time specified in this field, then do not perform the request 1040 method; instead, respond as detailed below. 1042 1041 </p> 1043 1042 <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span> <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> = <a href="#notation" class="smpl">HTTP-date</a> … … 1075 1074 </li> 1076 1075 </ul> 1077 <p id="rfc.section.3.3.p.7">The result of a request having both an If-Modified-Since header field and either an <a href="#header.if-match" class="smpl">If-Match</a> or an <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> header field is undefined by this specification.1078 </p>1079 1076 <div id="rfc.iref.i.4"></div> 1080 1077 <div id="rfc.iref.h.6"></div> … … 1089 1086 </p> 1090 1087 <p id="rfc.section.3.4.p.6">If the specified date is invalid, the header field <em class="bcp14">MUST</em> be ignored. 1091 </p>1092 <p id="rfc.section.3.4.p.7">The result of a request having both an If-Unmodified-Since header field and either an <a href="#header.if-none-match" class="smpl">If-None-Match</a> or an <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> header field is undefined by this specification.1093 1088 </p> 1094 1089 <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a> <a id="header.if-range" href="#header.if-range">If-Range</a></h2> … … 1124 1119 and metadata) and thus prevent the request method from being applied if the target resource is in an unexpected state. 1125 1120 </p> 1126 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1127 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2> 1128 <p id="rfc.section.5.1.p.1">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: 1121 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="precedence" href="#precedence">Precedence</a></h1> 1122 <p id="rfc.section.5.p.1">When more than one conditional request header field is present in a request, the order in which the fields are evaluated becomes 1123 important. In practice, the fields defined in this document are consistently implemented in a single, logical order, due to 1124 the fact that entity tags are presumed to be more accurate than date validators. For example, the only reason to send both <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> and <a href="#header.if-none-match" class="smpl">If-None-Match</a> in the same GET request is to support intermediary caches that might not have implemented <a href="#header.if-none-match" class="smpl">If-None-Match</a>, so it makes sense to ignore the <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> when entity tags are understood and available for the selected representation. 1125 </p> 1126 <p id="rfc.section.5.p.2">The general rule of conditional precedence is that exact match conditions are evaluated before cache-validating conditions 1127 and, within that order, last-modified conditions are only evaluated if the corresponding entity tag condition is not present 1128 (or not applicable because the selected representation does not have an entity tag). 1129 </p> 1130 <p id="rfc.section.5.p.3">Specifically, the fields defined by this specification are evaluated as follows: </p> 1131 <ol> 1132 <li>When <a href="#header.if-match" class="smpl">If-Match</a> is present, evaluate it: 1133 <ul> 1134 <li>if true, continue to step 3</li> 1135 <li>if false, respond <a href="#status.412" class="smpl">412 (Precondition Failed)</a></li> 1136 </ul> 1137 </li> 1138 <li>When <a href="#header.if-match" class="smpl">If-Match</a> is not present and <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> is present, evaluate it: 1139 <ul> 1140 <li>if true, continue to step 3</li> 1141 <li>if false, respond <a href="#status.412" class="smpl">412 (Precondition Failed)</a></li> 1142 </ul> 1143 </li> 1144 <li>When the method is GET and both <a href="p5-range.html#range.retrieval.requests" class="smpl">Range</a> and <a href="p5-range.html#header.if-range" class="smpl">If-Range</a> are present, evaluate it: 1145 <ul> 1146 <li>if the validator matches, respond 206 (Partial Content)</li> 1147 <li>if the validator does not match, respond <a href="p2-semantics.html#status.200" class="smpl">200 (OK)</a></li> 1148 </ul> 1149 </li> 1150 <li>When <a href="#header.if-none-match" class="smpl">If-None-Match</a> is present, evaluate it: 1151 <ul> 1152 <li>if true, all conditions are met</li> 1153 <li>if false for GET/HEAD, respond <a href="#status.304" class="smpl">304 (Not Modified)</a></li> 1154 <li>if false for other methods, respond <a href="#status.412" class="smpl">412 (Precondition Failed)</a></li> 1155 </ul> 1156 </li> 1157 <li>When the method is GET or HEAD, <a href="#header.if-none-match" class="smpl">If-None-Match</a> is not present, and <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> is present, evaluate it: 1158 <ul> 1159 <li>if true, all conditions are met</li> 1160 <li>if false, respond <a href="#status.304" class="smpl">304 (Not Modified)</a></li> 1161 </ul> 1162 </li> 1163 </ol> 1164 <p id="rfc.section.5.p.4">Any extension to HTTP/1.1 that defines additional conditional request header fields ought to define its own expectations regarding 1165 the order for evaluating such fields in relation to those defined in this document and other conditionals that might be found 1166 in practice. 1167 </p> 1168 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 1169 <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2> 1170 <p id="rfc.section.6.1.p.1">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: 1129 1171 </p> 1130 1172 <div id="rfc.table.1"> … … 1154 1196 </table> 1155 1197 </div> 1156 <h2 id="rfc.section. 5.2"><a href="#rfc.section.5.2">5.2</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>1157 <p id="rfc.section. 5.2.p.1">The Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):1198 <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2> 1199 <p id="rfc.section.6.2.p.1">The Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>): 1158 1200 </p> 1159 1201 <div id="rfc.table.2"> … … 1214 1256 </table> 1215 1257 </div> 1216 <p id="rfc.section. 5.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>1217 <h1 id="rfc.section. 6"><a href="#rfc.section.6">6.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>1218 <p id="rfc.section. 6.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.1219 </p> 1220 <h1 id="rfc.section. 7"><a href="#rfc.section.7">7.</a> <a id="acks" href="#acks">Acknowledgments</a></h1>1221 <p id="rfc.section. 7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.1222 </p> 1223 <h1 id="rfc.references"><a id="rfc.section. 8" href="#rfc.section.8">8.</a> References1258 <p id="rfc.section.6.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 1259 <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 1260 <p id="rfc.section.7.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1261 </p> 1262 <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a> <a id="acks" href="#acks">Acknowledgments</a></h1> 1263 <p id="rfc.section.8.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. 1264 </p> 1265 <h1 id="rfc.references"><a id="rfc.section.9" href="#rfc.section.9">9.</a> References 1224 1266 </h1> 1225 <h2 id="rfc.references.1"><a href="#rfc.section. 8.1" id="rfc.section.8.1">8.1</a> Normative References1267 <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References 1226 1268 </h2> 1227 1269 <table> … … 1257 1299 </tr> 1258 1300 </table> 1259 <h2 id="rfc.references.2"><a href="#rfc.section. 8.2" id="rfc.section.8.2">8.2</a> Informative References1301 <h2 id="rfc.references.2"><a href="#rfc.section.9.2" id="rfc.section.9.2">9.2</a> Informative References 1260 1302 </h2> 1261 1303 <table> … … 1340 1382 <ul class="ind"> 1341 1383 <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul> 1342 <li>304 Not Modified (status code) <a href="#rfc.iref.27"><b>4.1</b></a>, <a href="#rfc.xref.status.304.1"> 5.1</a></li>1384 <li>304 Not Modified (status code) <a href="#rfc.iref.27"><b>4.1</b></a>, <a href="#rfc.xref.status.304.1">6.1</a></li> 1343 1385 </ul> 1344 1386 </li> 1345 1387 <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> 1346 <li>412 Precondition Failed (status code) <a href="#rfc.iref.28"><b>4.2</b></a>, <a href="#rfc.xref.status.412.1"> 5.1</a></li>1388 <li>412 Precondition Failed (status code) <a href="#rfc.iref.28"><b>4.2</b></a>, <a href="#rfc.xref.status.412.1">6.1</a></li> 1347 1389 </ul> 1348 1390 </li> 1349 1391 <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul> 1350 <li>ETag header field <a href="#rfc.xref.header.etag.1">2</a>, <a href="#rfc.iref.e.1"><b>2.3</b></a>, <a href="#rfc.xref.header.etag.2"> 5.2</a>, <a href="#rfc.xref.header.etag.3">A</a></li>1392 <li>ETag header field <a href="#rfc.xref.header.etag.1">2</a>, <a href="#rfc.iref.e.1"><b>2.3</b></a>, <a href="#rfc.xref.header.etag.2">6.2</a>, <a href="#rfc.xref.header.etag.3">A</a></li> 1351 1393 </ul> 1352 1394 </li> … … 1371 1413 <li>Header Fields 1372 1414 <ul> 1373 <li>ETag <a href="#rfc.xref.header.etag.1">2</a>, <a href="#rfc.iref.h.2"><b>2.3</b></a>, <a href="#rfc.xref.header.etag.2"> 5.2</a>, <a href="#rfc.xref.header.etag.3">A</a></li>1374 <li>If-Match <a href="#rfc.iref.h.3"><b>3.1</b></a>, <a href="#rfc.xref.header.if-match.1"> 5.2</a></li>1375 <li>If-Modified-Since <a href="#rfc.iref.h.5"><b>3.3</b></a>, <a href="#rfc.xref.header.if-modified-since.1"> 5.2</a></li>1376 <li>If-None-Match <a href="#rfc.iref.h.4"><b>3.2</b></a>, <a href="#rfc.xref.header.if-none-match.1"> 5.2</a>, <a href="#rfc.xref.header.if-none-match.2">A</a></li>1377 <li>If-Unmodified-Since <a href="#rfc.iref.h.6"><b>3.4</b></a>, <a href="#rfc.xref.header.if-unmodified-since.1"> 5.2</a></li>1378 <li>Last-Modified <a href="#rfc.xref.header.last-modified.1">2</a>, <a href="#rfc.iref.h.1"><b>2.2</b></a>, <a href="#rfc.xref.header.last-modified.2"> 5.2</a></li>1415 <li>ETag <a href="#rfc.xref.header.etag.1">2</a>, <a href="#rfc.iref.h.2"><b>2.3</b></a>, <a href="#rfc.xref.header.etag.2">6.2</a>, <a href="#rfc.xref.header.etag.3">A</a></li> 1416 <li>If-Match <a href="#rfc.iref.h.3"><b>3.1</b></a>, <a href="#rfc.xref.header.if-match.1">6.2</a></li> 1417 <li>If-Modified-Since <a href="#rfc.iref.h.5"><b>3.3</b></a>, <a href="#rfc.xref.header.if-modified-since.1">6.2</a></li> 1418 <li>If-None-Match <a href="#rfc.iref.h.4"><b>3.2</b></a>, <a href="#rfc.xref.header.if-none-match.1">6.2</a>, <a href="#rfc.xref.header.if-none-match.2">A</a></li> 1419 <li>If-Unmodified-Since <a href="#rfc.iref.h.6"><b>3.4</b></a>, <a href="#rfc.xref.header.if-unmodified-since.1">6.2</a></li> 1420 <li>Last-Modified <a href="#rfc.xref.header.last-modified.1">2</a>, <a href="#rfc.iref.h.1"><b>2.2</b></a>, <a href="#rfc.xref.header.last-modified.2">6.2</a></li> 1379 1421 </ul> 1380 1422 </li> … … 1382 1424 </li> 1383 1425 <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul> 1384 <li>If-Match header field <a href="#rfc.iref.i.1"><b>3.1</b></a>, <a href="#rfc.xref.header.if-match.1"> 5.2</a></li>1385 <li>If-Modified-Since header field <a href="#rfc.iref.i.3"><b>3.3</b></a>, <a href="#rfc.xref.header.if-modified-since.1"> 5.2</a></li>1386 <li>If-None-Match header field <a href="#rfc.iref.i.2"><b>3.2</b></a>, <a href="#rfc.xref.header.if-none-match.1"> 5.2</a>, <a href="#rfc.xref.header.if-none-match.2">A</a></li>1387 <li>If-Unmodified-Since header field <a href="#rfc.iref.i.4"><b>3.4</b></a>, <a href="#rfc.xref.header.if-unmodified-since.1"> 5.2</a></li>1426 <li>If-Match header field <a href="#rfc.iref.i.1"><b>3.1</b></a>, <a href="#rfc.xref.header.if-match.1">6.2</a></li> 1427 <li>If-Modified-Since header field <a href="#rfc.iref.i.3"><b>3.3</b></a>, <a href="#rfc.xref.header.if-modified-since.1">6.2</a></li> 1428 <li>If-None-Match header field <a href="#rfc.iref.i.2"><b>3.2</b></a>, <a href="#rfc.xref.header.if-none-match.1">6.2</a>, <a href="#rfc.xref.header.if-none-match.2">A</a></li> 1429 <li>If-Unmodified-Since header field <a href="#rfc.iref.i.4"><b>3.4</b></a>, <a href="#rfc.xref.header.if-unmodified-since.1">6.2</a></li> 1388 1430 </ul> 1389 1431 </li> 1390 1432 <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul> 1391 <li>Last-Modified header field <a href="#rfc.xref.header.last-modified.1">2</a>, <a href="#rfc.iref.l.1"><b>2.2</b></a>, <a href="#rfc.xref.header.last-modified.2"> 5.2</a></li>1433 <li>Last-Modified header field <a href="#rfc.xref.header.last-modified.1">2</a>, <a href="#rfc.iref.l.1"><b>2.2</b></a>, <a href="#rfc.xref.header.last-modified.2">6.2</a></li> 1392 1434 </ul> 1393 1435 </li> … … 1397 1439 </li> 1398 1440 <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul> 1399 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">1.2</a>, <a href="#rfc.xref.Part1.5">1.2</a>, <a href="#rfc.xref.Part1.6">1.2</a>, <a href="#rfc.xref.Part1.7">2.3.3</a>, <a href="#rfc.xref.Part1.8"> 6</a>, <a href="#rfc.xref.Part1.9">7</a>, <a href="#Part1"><b>8.1</b></a><ul>1441 <li><em>Part1</em> <a href="#rfc.xref.Part1.1">1</a>, <a href="#rfc.xref.Part1.2">1.1</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">1.2</a>, <a href="#rfc.xref.Part1.5">1.2</a>, <a href="#rfc.xref.Part1.6">1.2</a>, <a href="#rfc.xref.Part1.7">2.3.3</a>, <a href="#rfc.xref.Part1.8">7</a>, <a href="#rfc.xref.Part1.9">8</a>, <a href="#Part1"><b>9.1</b></a><ul> 1400 1442 <li><em>Section 1.2</em> <a href="#rfc.xref.Part1.3">1.2</a></li> 1401 1443 <li><em>Section 2</em> <a href="#rfc.xref.Part1.2">1.1</a></li> … … 1403 1445 <li><em>Section 3.2.4</em> <a href="#rfc.xref.Part1.6">1.2</a></li> 1404 1446 <li><em>Section 4</em> <a href="#rfc.xref.Part1.7">2.3.3</a></li> 1405 <li><em>Section 9</em> <a href="#rfc.xref.Part1.9"> 7</a></li>1447 <li><em>Section 9</em> <a href="#rfc.xref.Part1.9">8</a></li> 1406 1448 </ul> 1407 1449 </li> 1408 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">1.2</a>, <a href="#rfc.xref.Part2.3">1.2</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">2.3.3</a>, <a href="#rfc.xref.Part2.6">4.1</a>, <a href="#Part2"><b> 8.1</b></a><ul>1450 <li><em>Part2</em> <a href="#rfc.xref.Part2.1">1</a>, <a href="#rfc.xref.Part2.2">1.2</a>, <a href="#rfc.xref.Part2.3">1.2</a>, <a href="#rfc.xref.Part2.4">2.3.3</a>, <a href="#rfc.xref.Part2.5">2.3.3</a>, <a href="#rfc.xref.Part2.6">4.1</a>, <a href="#Part2"><b>9.1</b></a><ul> 1409 1451 <li><em>Section 5.1</em> <a href="#rfc.xref.Part2.3">1.2</a></li> 1410 1452 <li><em>Section 8</em> <a href="#rfc.xref.Part2.4">2.3.3</a></li> … … 1413 1455 </ul> 1414 1456 </li> 1415 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">3.3</a>, <a href="#rfc.xref.Part5.2">3.5</a>, <a href="#Part5"><b> 8.1</b></a><ul>1457 <li><em>Part5</em> <a href="#rfc.xref.Part5.1">3.3</a>, <a href="#rfc.xref.Part5.2">3.5</a>, <a href="#Part5"><b>9.1</b></a><ul> 1416 1458 <li><em>Section 5.3</em> <a href="#rfc.xref.Part5.2">3.5</a></li> 1417 1459 <li><em>Section 5.4</em> <a href="#rfc.xref.Part5.1">3.3</a></li> 1418 1460 </ul> 1419 1461 </li> 1420 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">2.2.1</a>, <a href="#rfc.xref.Part6.3">2.3.1</a>, <a href="#Part6"><b> 8.1</b></a></li>1462 <li><em>Part6</em> <a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">2.2.1</a>, <a href="#rfc.xref.Part6.3">2.3.1</a>, <a href="#Part6"><b>9.1</b></a></li> 1421 1463 </ul> 1422 1464 </li> 1423 1465 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 1424 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b> 8.1</b></a></li>1425 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">2.3</a>, <a href="#RFC2616"><b> 8.2</b></a><ul>1466 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>9.1</b></a></li> 1467 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">2.3</a>, <a href="#RFC2616"><b>9.2</b></a><ul> 1426 1468 <li><em>Section 3.11</em> <a href="#rfc.xref.RFC2616.1">2.3</a></li> 1427 1469 </ul> 1428 1470 </li> 1429 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1"> 5.2</a>, <a href="#RFC3864"><b>8.2</b></a></li>1430 <li><em>RFC4918</em> <a href="#rfc.xref.RFC4918.1">2</a>, <a href="#RFC4918"><b> 8.2</b></a></li>1431 <li><em>RFC5234</em> <a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b> 8.1</b></a><ul>1471 <li><em>RFC3864</em> <a href="#rfc.xref.RFC3864.1">6.2</a>, <a href="#RFC3864"><b>9.2</b></a></li> 1472 <li><em>RFC4918</em> <a href="#rfc.xref.RFC4918.1">2</a>, <a href="#RFC4918"><b>9.2</b></a></li> 1473 <li><em>RFC5234</em> <a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b>9.1</b></a><ul> 1432 1474 <li><em>Appendix B.1</em> <a href="#rfc.xref.RFC5234.2">1.2</a></li> 1433 1475 </ul> … … 1439 1481 <li>Status Codes 1440 1482 <ul> 1441 <li>304 Not Modified <a href="#rfc.iref.s.2"><b>4.1</b></a>, <a href="#rfc.xref.status.304.1"> 5.1</a></li>1442 <li>412 Precondition Failed <a href="#rfc.iref.s.3"><b>4.2</b></a>, <a href="#rfc.xref.status.412.1"> 5.1</a></li>1483 <li>304 Not Modified <a href="#rfc.iref.s.2"><b>4.1</b></a>, <a href="#rfc.xref.status.304.1">6.1</a></li> 1484 <li>412 Precondition Failed <a href="#rfc.iref.s.3"><b>4.2</b></a>, <a href="#rfc.xref.status.412.1">6.1</a></li> 1443 1485 </ul> 1444 1486 </li> -
draft-ietf-httpbis/latest/p4-conditional.xml
r1796 r1799 751 751 This section defines the syntax and semantics of HTTP/1.1 header fields 752 752 for applying preconditions on requests. 753 <xref target="precedence"/> defines the order of evaluation when 754 more than one precondition is present in a request. 753 755 </t> 754 756 … … 807 809 If-Match: * 808 810 </artwork></figure> 809 <t>810 The result of a request having both an If-Match header field and811 either an <x:ref>If-None-Match</x:ref> or an <x:ref>If-Modified-Since</x:ref>812 header field is undefined by this specification.813 </t>814 811 </section> 815 812 … … 885 882 If-None-Match: * 886 883 </artwork></figure> 887 <t>888 The result of a request having both an If-None-Match header field and889 either an <x:ref>If-Match</x:ref> or an <x:ref>If-Unmodified-Since</x:ref>890 header field is undefined by this specification.891 </t>892 884 </section> 893 885 … … 897 889 <x:anchor-alias value="If-Modified-Since"/> 898 890 <t> 899 The "If-Modified-Since" header field can be used to make a request900 method conditional by modification date: if the selected representation891 The "If-Modified-Since" header field can be used with GET or HEAD to make 892 the method conditional by modification date: if the selected representation 901 893 has not been modified since the time specified in this field, then 902 894 do not perform the request method; instead, respond as detailed below. … … 968 960 </list> 969 961 </t> 970 <t>971 The result of a request having both an If-Modified-Since header field972 and either an <x:ref>If-Match</x:ref> or an <x:ref>If-Unmodified-Since</x:ref>973 header field is undefined by this specification.974 </t>975 962 </section> 976 963 … … 1006 993 <t> 1007 994 If the specified date is invalid, the header field &MUST; be ignored. 1008 </t>1009 <t>1010 The result of a request having both an If-Unmodified-Since header1011 field and either an <x:ref>If-None-Match</x:ref> or an <x:ref>If-Modified-Since</x:ref>1012 header field is undefined by this specification.1013 995 </t> 1014 996 </section> … … 1088 1070 </t> 1089 1071 </section> 1072 </section> 1073 1074 <section title="Precedence" anchor="precedence"> 1075 <t> 1076 When more than one conditional request header field is present in a request, 1077 the order in which the fields are evaluated becomes important. In practice, 1078 the fields defined in this document are consistently implemented in a 1079 single, logical order, due to the fact that entity tags are presumed to be 1080 more accurate than date validators. For example, the only reason to send 1081 both <x:ref>If-Modified-Since</x:ref> and <x:ref>If-None-Match</x:ref> in the same GET request is to 1082 support intermediary caches that might not have implemented <x:ref>If-None-Match</x:ref>, 1083 so it makes sense to ignore the <x:ref>If-Modified-Since</x:ref> when entity tags are 1084 understood and available for the selected representation. 1085 </t> 1086 <t> 1087 The general rule of conditional precedence is that exact match conditions 1088 are evaluated before cache-validating conditions and, within that order, 1089 last-modified conditions are only evaluated if the corresponding 1090 entity tag condition is not present (or not applicable because the 1091 selected representation does not have an entity tag). 1092 </t> 1093 <t> 1094 Specifically, the fields defined by this specification are evaluated 1095 as follows: 1096 <list style="numbers"> 1097 <t>When <x:ref>If-Match</x:ref> is present, evaluate it: 1098 <list style="symbols"> 1099 <t>if true, continue to step 3</t> 1100 <t>if false, respond <x:ref>412 (Precondition Failed)</x:ref></t> 1101 </list> 1102 </t> 1103 <t>When <x:ref>If-Match</x:ref> is not present and 1104 <x:ref>If-Unmodified-Since</x:ref> is present, evaluate it: 1105 <list style="symbols"> 1106 <t>if true, continue to step 3</t> 1107 <t>if false, respond <x:ref>412 (Precondition Failed)</x:ref></t> 1108 </list> 1109 </t> 1110 <t>When the method is GET and both <x:ref>Range</x:ref> and 1111 <x:ref>If-Range</x:ref> are present, evaluate it: 1112 <list style="symbols"> 1113 <t>if the validator matches, respond <x:ref>206 (Partial Content)</x:ref></t> 1114 <t>if the validator does not match, respond <x:ref>200 (OK)</x:ref></t> 1115 </list> 1116 </t> 1117 <t>When <x:ref>If-None-Match</x:ref> is present, evaluate it: 1118 <list style="symbols"> 1119 <t>if true, all conditions are met</t> 1120 <t>if false for GET/HEAD, respond <x:ref>304 (Not Modified)</x:ref></t> 1121 <t>if false for other methods, respond <x:ref>412 (Precondition Failed)</x:ref></t> 1122 </list> 1123 </t> 1124 <t>When the method is GET or HEAD, 1125 <x:ref>If-None-Match</x:ref> is not present, and 1126 <x:ref>If-Modified-Since</x:ref> is present, evaluate it: 1127 <list style="symbols"> 1128 <t>if true, all conditions are met</t> 1129 <t>if false, respond <x:ref>304 (Not Modified)</x:ref></t> 1130 </list> 1131 </t> 1132 </list> 1133 </t> 1134 <t> 1135 Any extension to HTTP/1.1 that defines additional conditional request 1136 header fields ought to define its own expectations regarding the order 1137 for evaluating such fields in relation to those defined in this document 1138 and other conditionals that might be found in practice. 1139 </t> 1090 1140 </section> 1091 1141 -
draft-ietf-httpbis/latest/p5-range.html
r1798 r1799 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 7, 2013";451 content: "Expires January 16, 2013"; 452 452 } 453 453 @bottom-right { … … 492 492 <meta name="dct.creator" content="Reschke, J. F."> 493 493 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 494 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 6">494 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 495 495 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 496 496 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range requests and the rules for constructing and combining responses to those requests."> … … 518 518 </tr> 519 519 <tr> 520 <td class="left">Expires: January 1 7, 2013</td>520 <td class="left">Expires: January 16, 2013</td> 521 521 <td class="right">J. Reschke, Editor</td> 522 522 </tr> … … 527 527 <tr> 528 528 <td class="left"></td> 529 <td class="right">July 1 6, 2012</td>529 <td class="right">July 15, 2012</td> 530 530 </tr> 531 531 </tbody> … … 554 554 in progress”. 555 555 </p> 556 <p>This Internet-Draft will expire on January 1 7, 2013.</p>556 <p>This Internet-Draft will expire on January 16, 2013.</p> 557 557 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 558 558 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p6-cache.html
r1796 r1799 452 452 } 453 453 @bottom-center { 454 content: "Expires January 1 7, 2013";454 content: "Expires January 16, 2013"; 455 455 } 456 456 @bottom-right { … … 498 498 <meta name="dct.creator" content="Reschke, J. F."> 499 499 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 500 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 6">500 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 501 501 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 502 502 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 524 524 </tr> 525 525 <tr> 526 <td class="left">Expires: January 1 7, 2013</td>526 <td class="left">Expires: January 16, 2013</td> 527 527 <td class="right">M. Nottingham, Editor</td> 528 528 </tr> … … 541 541 <tr> 542 542 <td class="left"></td> 543 <td class="right">July 1 6, 2012</td>543 <td class="right">July 15, 2012</td> 544 544 </tr> 545 545 </tbody> … … 570 570 in progress”. 571 571 </p> 572 <p>This Internet-Draft will expire on January 1 7, 2013.</p>572 <p>This Internet-Draft will expire on January 16, 2013.</p> 573 573 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 574 574 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p7-auth.html
r1796 r1799 449 449 } 450 450 @bottom-center { 451 content: "Expires January 1 7, 2013";451 content: "Expires January 16, 2013"; 452 452 } 453 453 @bottom-right { … … 489 489 <meta name="dct.creator" content="Reschke, J. F."> 490 490 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 491 <meta name="dct.issued" scheme="ISO8601" content="2012-07-1 6">491 <meta name="dct.issued" scheme="ISO8601" content="2012-07-15"> 492 492 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 493 493 <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 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines the HTTP Authentication framework."> … … 520 520 </tr> 521 521 <tr> 522 <td class="left">Expires: January 1 7, 2013</td>522 <td class="left">Expires: January 16, 2013</td> 523 523 <td class="right">greenbytes</td> 524 524 </tr> 525 525 <tr> 526 526 <td class="left"></td> 527 <td class="right">July 1 6, 2012</td>527 <td class="right">July 15, 2012</td> 528 528 </tr> 529 529 </tbody> … … 552 552 in progress”. 553 553 </p> 554 <p>This Internet-Draft will expire on January 1 7, 2013.</p>554 <p>This Internet-Draft will expire on January 16, 2013.</p> 555 555 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 556 556 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
Note: See TracChangeset
for help on using the changeset viewer.