source: draft-ietf-httpbis/11/p4-conditional.html

Last change on this file was 2726, checked in by julian.reschke@…, 8 years ago

update to latest version of rfc2629.xslt, regen all HTML

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 107.0 KB
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 4: Conditional Requests</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
10a.smpl {
11  color: black;
13a:hover {
14  text-decoration: underline;
16a:active {
17  text-decoration: underline;
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
24body {
25  color: black;
26  font-family: cambria, helvetica, arial, sans-serif;
27  font-size: 11pt;
28  margin-right: 2em;
30cite {
31  font-style: normal;
33div.note {
34  margin-left: 2em;
36dl {
37  margin-left: 2em;
39ul.empty {
40  list-style-type: none;
42ul.empty li {
43  margin-top: .5em;
45dl p {
46  margin-left: 0em;
48dt {
49  margin-top: .5em;
51h1 {
52  font-size: 130%;
53  line-height: 21pt;
54  page-break-after: avoid;
55} {
57  page-break-before: always;
59h2 {
60  font-size: 120%;
61  line-height: 15pt;
62  page-break-after: avoid;
64h3 {
65  font-size: 110%;
66  page-break-after: avoid;
68h4, h5, h6 {
69  page-break-after: avoid;
71h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
72  color: black;
74img {
75  margin-left: 3em;
77li {
78  margin-left: 2em;
80ol {
81  margin-left: 2em;
82} {
84  list-style-type: lower-alpha;
85} {
87  list-style-type: upper-alpha;
89ol p {
90  margin-left: 0em;
92p {
93  margin-left: 2em;
95pre {
96  margin-left: 3em;
97  background-color: lightyellow;
98  padding: .25em;
99  page-break-inside: avoid;
101pre.text2 {
102  border-style: dotted;
103  border-width: 1px;
104  background-color: #f0f0f0;
105  width: 69em;
107pre.inline {
108  background-color: white;
109  padding: 0em;
111pre.text {
112  border-style: dotted;
113  border-width: 1px;
114  background-color: #f8f8f8;
115  width: 69em;
117pre.drawing {
118  border-style: solid;
119  border-width: 1px;
120  background-color: #f8f8f8;
121  padding: 2em;
123table {
124  margin-left: 2em;
125} {
127  vertical-align: top;
128  border-color: gray;
129} th {
131  border-color: gray;
132} td {
134  border-color: gray;
136table.all {
137  border-style: solid;
138  border-width: 2px;
140table.full {
141  border-style: solid;
142  border-width: 2px;
143} td {
145  vertical-align: top;
147table.all td {
148  border-style: solid;
149  border-width: 1px;
151table.full td {
152  border-style: none solid;
153  border-width: 1px;
154} th {
156  vertical-align: top;
158table.all th {
159  border-style: solid;
160  border-width: 1px;
162table.full th {
163  border-style: solid;
164  border-width: 1px 1px 2px 1px;
166table.headers th {
167  border-style: none none solid none;
168  border-width: 2px;
170table.left {
171  margin-right: auto;
173table.right {
174  margin-left: auto;
175} {
177  margin-left: auto;
178  margin-right: auto;
180caption {
181  caption-side: bottom;
182  font-weight: bold;
183  font-size: 10pt;
184  margin-top: .5em;
187table.header {
188  border-spacing: 1px;
189  width: 95%;
190  font-size: 11pt;
191  color: white;
192} {
194  vertical-align: top;
196td.topnowrap {
197  vertical-align: top;
198  white-space: nowrap;
200table.header td {
201  background-color: gray;
202  width: 50%;
204table.header a {
205  color: white;
207td.reference {
208  vertical-align: top;
209  white-space: nowrap;
210  padding-right: 1em;
212thead {
213  display:table-header-group;
215ul.toc, ul.toc ul {
216  list-style: none;
217  margin-left: 1.5em;
218  padding-left: 0em;
220ul.toc li {
221  line-height: 150%;
222  font-weight: bold;
223  margin-left: 0em;
225ul.toc li li {
226  line-height: normal;
227  font-weight: normal;
228  font-size: 10pt;
229  margin-left: 0em;
231li.excluded {
232  font-size: 0pt;
234ul p {
235  margin-left: 0em;
237.title, .filename, h1, h2, h3, h4 {
238  font-family: candara, helvetica, arial, sans-serif;
240samp, tt, code, pre {
241  font: consolas, monospace;
243ul.ind, ul.ind ul {
244  list-style: none;
245  margin-left: 1.5em;
246  padding-left: 0em;
247  page-break-before: avoid;
249ul.ind li {
250  font-weight: bold;
251  line-height: 200%;
252  margin-left: 0em;
254ul.ind li li {
255  font-weight: normal;
256  line-height: 150%;
257  margin-left: 0em;
259.avoidbreak {
260  page-break-inside: avoid;
262.bcp14 {
263  font-style: normal;
264  text-transform: lowercase;
265  font-variant: small-caps;
267.comment {
268  background-color: yellow;
269} {
271  text-align: center;
273.error {
274  color: red;
275  font-style: italic;
276  font-weight: bold;
278.figure {
279  font-weight: bold;
280  text-align: center;
281  font-size: 10pt;
283.filename {
284  color: #333333;
285  font-size: 75%;
286  font-weight: bold;
287  line-height: 21pt;
288  text-align: center;
290.fn {
291  font-weight: bold;
293.left {
294  text-align: left;
296.right {
297  text-align: right;
299.title {
300  color: green;
301  font-size: 150%;
302  line-height: 18pt;
303  font-weight: bold;
304  text-align: center;
305  margin-top: 36pt;
307.warning {
308  font-size: 130%;
309  background-color: yellow;
313@media print {
314  .noprint {
315    display: none;
316  }
318  a {
319    color: black;
320    text-decoration: none;
321  }
323  table.header {
324    width: 90%;
325  }
327  td.header {
328    width: 50%;
329    color: black;
330    background-color: white;
331    vertical-align: top;
332    font-size: 110%;
333  }
335  ul.toc a:nth-child(2)::after {
336    content: leader('.') target-counter(attr(href), page);
337  }
339  ul.ind li li a {
340    content: target-counter(attr(href), page);
341  }
343  .print2col {
344    column-count: 2;
345    -moz-column-count: 2;
346    column-fill: auto;
347  }
350@page {
351  @top-left {
352       content: "Internet-Draft";
353  }
354  @top-right {
355       content: "August 2010";
356  }
357  @top-center {
358       content: "HTTP/1.1, Part 4";
359  }
360  @bottom-left {
361       content: "Fielding, et al.";
362  }
363  @bottom-center {
364       content: "Expires February 5, 2011";
365  }
366  @bottom-right {
367       content: "[Page " counter(page) "]";
368  }
371@page:first {
372    @top-left {
373      content: normal;
374    }
375    @top-right {
376      content: normal;
377    }
378    @top-center {
379      content: normal;
380    }
382</style><link rel="Contents" href="#rfc.toc">
383      <link rel="Author" href="#rfc.authors">
384      <link rel="Copyright" href="#rfc.copyrightnotice">
385      <link rel="Index" href="#rfc.index">
386      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
387      <link rel="Chapter" title="2 Entity-Tags" href="#rfc.section.2">
388      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
389      <link rel="Chapter" title="4 Weak and Strong Validators" href="#rfc.section.4">
390      <link rel="Chapter" title="5 Rules for When to Use Entity-tags and Last-Modified Dates" href="#rfc.section.5">
391      <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6">
392      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
393      <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
394      <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9">
395      <link rel="Chapter" href="#rfc.section.10" title="10 References">
396      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
397      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
398      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
399      <meta name="generator" content=", Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica">
400      <link rel="schema.dct" href="">
401      <meta name="dct.creator" content="Fielding, R.">
402      <meta name="dct.creator" content="Gettys, J.">
403      <meta name="dct.creator" content="Mogul, J.">
404      <meta name="dct.creator" content="Frystyk, H.">
405      <meta name="dct.creator" content="Masinter, L.">
406      <meta name="dct.creator" content="Leach, P.">
407      <meta name="dct.creator" content="Berners-Lee, T.">
408      <meta name="dct.creator" content="Lafon, Y.">
409      <meta name="dct.creator" content="Reschke, J. F.">
410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-11">
411      <meta name="dct.issued" scheme="ISO8601" content="2010-08-04">
412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
413      <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 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
414      <meta name="description" 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 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
415   </head>
416   <body>
417      <table class="header">
418         <tbody>
419            <tr>
420               <td class="left">HTTPbis Working Group</td>
421               <td class="right">R. Fielding, Editor</td>
422            </tr>
423            <tr>
424               <td class="left">Internet-Draft</td>
425               <td class="right">Day Software</td>
426            </tr>
427            <tr>
428               <td class="left">Obsoletes: <a href="">2616</a> (if approved)
429               </td>
430               <td class="right">J. Gettys</td>
431            </tr>
432            <tr>
433               <td class="left">Intended status: Standards Track</td>
434               <td class="right">Alcatel-Lucent</td>
435            </tr>
436            <tr>
437               <td class="left">Expires: February 5, 2011</td>
438               <td class="right">J. Mogul</td>
439            </tr>
440            <tr>
441               <td class="left"></td>
442               <td class="right">HP</td>
443            </tr>
444            <tr>
445               <td class="left"></td>
446               <td class="right">H. Frystyk</td>
447            </tr>
448            <tr>
449               <td class="left"></td>
450               <td class="right">Microsoft</td>
451            </tr>
452            <tr>
453               <td class="left"></td>
454               <td class="right">L. Masinter</td>
455            </tr>
456            <tr>
457               <td class="left"></td>
458               <td class="right">Adobe Systems</td>
459            </tr>
460            <tr>
461               <td class="left"></td>
462               <td class="right">P. Leach</td>
463            </tr>
464            <tr>
465               <td class="left"></td>
466               <td class="right">Microsoft</td>
467            </tr>
468            <tr>
469               <td class="left"></td>
470               <td class="right">T. Berners-Lee</td>
471            </tr>
472            <tr>
473               <td class="left"></td>
474               <td class="right">W3C/MIT</td>
475            </tr>
476            <tr>
477               <td class="left"></td>
478               <td class="right">Y. Lafon, Editor</td>
479            </tr>
480            <tr>
481               <td class="left"></td>
482               <td class="right">W3C</td>
483            </tr>
484            <tr>
485               <td class="left"></td>
486               <td class="right">J. Reschke, Editor</td>
487            </tr>
488            <tr>
489               <td class="left"></td>
490               <td class="right">greenbytes</td>
491            </tr>
492            <tr>
493               <td class="left"></td>
494               <td class="right">August 4, 2010</td>
495            </tr>
496         </tbody>
497      </table>
498      <p class="title">HTTP/1.1, part 4: Conditional Requests<br><span class="filename">draft-ietf-httpbis-p4-conditional-11</span></p>
499      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
500      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
501         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the
502         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
503         4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.
504      </p>
505      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
506      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list ( The current issues
507         list is at &lt;<a href=""></a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href=""></a>&gt;.
508      </p>
509      <p>The changes in this draft are summarized in <a href="#changes.since.10" title="Since draft-ietf-httpbis-p4-conditional-10">Appendix&nbsp;C.12</a>.
510      </p>
511      <div id="rfc.status">
512         <h1><a href="#rfc.status">Status of This Memo</a></h1>
513         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
514         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
515            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href=""></a>.
516         </p>
517         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
518            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
519            in progress”.
520         </p>
521         <p>This Internet-Draft will expire on February 5, 2011.</p>
522      </div>
523      <div id="rfc.copyrightnotice">
524         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
525         <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
526         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href=""></a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
527            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
528            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
529            BSD License.
530         </p>
531         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
532            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
533            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
534            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
535            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
536            it into languages other than English.
537         </p>
538      </div>
539      <hr class="noprint">
540      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
541      <ul class="toc">
542         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
543               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
544               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
545                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
546                     <li><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
547                  </ul>
548               </li>
549            </ul>
550         </li>
551         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#entity.tags">Entity-Tags</a><ul>
552               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#example.entity.tag.vs.conneg">Example: Entity-tags varying on Content-Negotiated Resources</a></li>
553            </ul>
554         </li>
555         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
556               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
557               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
558            </ul>
559         </li>
560         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#weak.and.strong.validators">Weak and Strong Validators</a></li>
561         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="">Rules for When to Use Entity-tags and Last-Modified Dates</a></li>
562         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
563               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.etag">ETag</a></li>
564               <li><a href="#rfc.section.6.2">6.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-match">If-Match</a></li>
565               <li><a href="#rfc.section.6.3">6.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></li>
566               <li><a href="#rfc.section.6.4">6.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-none-match">If-None-Match</a></li>
567               <li><a href="#rfc.section.6.5">6.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></li>
568               <li><a href="#rfc.section.6.6">6.6</a>&nbsp;&nbsp;&nbsp;<a href="#header.last-modified">Last-Modified</a></li>
569            </ul>
570         </li>
571         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
572               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
573               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
574            </ul>
575         </li>
576         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
577         <li><a href="#rfc.section.9">9.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
578         <li><a href="#rfc.section.10">10.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
579               <li><a href="#rfc.section.10.1">10.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
580               <li><a href="#rfc.section.10.2">10.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
581            </ul>
582         </li>
583         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
584         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
585         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
586               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
587               <li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p4-conditional-00</a></li>
588               <li><a href="#rfc.section.C.3">C.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p4-conditional-01</a></li>
589               <li><a href="#rfc.section.C.4">C.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p4-conditional-02</a></li>
590               <li><a href="#rfc.section.C.5">C.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p4-conditional-03</a></li>
591               <li><a href="#rfc.section.C.6">C.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p4-conditional-04</a></li>
592               <li><a href="#rfc.section.C.7">C.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p4-conditional-05</a></li>
593               <li><a href="#rfc.section.C.8">C.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p4-conditional-06</a></li>
594               <li><a href="#rfc.section.C.9">C.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p4-conditional-07</a></li>
595               <li><a href="#rfc.section.C.10">C.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p4-conditional-08</a></li>
596               <li><a href="#rfc.section.C.11">C.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p4-conditional-09</a></li>
597               <li><a href="#rfc.section.C.12">C.12</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p4-conditional-10</a></li>
598            </ul>
599         </li>
600         <li><a href="#rfc.index">Index</a></li>
601         <li><a href="#rfc.authors">Authors' Addresses</a></li>
602      </ul>
603      <div id="introduction">
604         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
605         <p id="rfc.section.1.p.1">This document defines HTTP/1.1 response metadata for indicating potential changes to payload content, including modification
606            time stamps and opaque entity-tags, and the HTTP conditional request mechanisms that allow preconditions to be placed on a
607            request method. Conditional GET requests allow for efficient cache updates. Other conditional request methods are used to
608            protect against overwriting or misunderstanding the state of a resource that has been changed unbeknownst to the requesting
609            client.
610         </p>
611         <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
612            errata changes. The next draft will reorganize the sections to better reflect the content. In particular, the sections on
613            resource metadata will be discussed first and then followed by each conditional request-header, concluding with a definition
614            of precedence and the expectation of ordering strong validator checks before weak validator checks. It is likely that more
615            content from <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a> will migrate to this part, where appropriate. The current mess reflects how widely dispersed these topics and associated requirements
616            had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
617         </p>
618         <div id="intro.requirements">
619            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
620            <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
621               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
622            </p>
623            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
624               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
625               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
626               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
627            </p>
628         </div>
629         <div id="notation">
630            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
631            <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF, with the list rule expanded.
632            </p>
633            <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
634               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
635               and WSP (whitespace).
636            </p>
637            <div id="core.rules">
638               <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a href="#core.rules">Core Rules</a></h3>
639               <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
640               </p>
641               <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
642  <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
644            <div id="abnf.dependencies">
645               <h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
646               <p id="rfc.section.1.2.2.p.1">The ABNF rules below are defined in other parts:</p>
647               <div id="rfc.figure.u.2"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="" title="Date/Time Formats: Full Date">Section 6.1</a>&gt;
649         </div>
650      </div>
651      <div id="entity.tags">
652         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#entity.tags">Entity-Tags</a></h1>
653         <p id="rfc.section.2.p.1">Entity-tags are used for comparing two or more representations of the same resource. HTTP/1.1 uses entity-tags in the ETag
654            (<a href="#header.etag" id="rfc.xref.header.etag.1" title="ETag">Section&nbsp;6.1</a>), If-Match (<a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;6.2</a>), If-None-Match (<a href="#header.if-none-match" id="rfc.xref.header.if-none-match.1" title="If-None-Match">Section&nbsp;6.4</a>), and If-Range (<a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) header fields. The definition of how they are used and compared as cache validators is in <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>. An entity-tag consists of an opaque quoted string, possibly prefixed by a weakness indicator.
655         </p>
656         <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  <a href="#entity.tags" class="smpl">entity-tag</a> = [ <a href="#entity.tags" class="smpl">weak</a> ] <a href="#entity.tags" class="smpl">opaque-tag</a>
657  <a href="#entity.tags" class="smpl">weak</a>       = %x57.2F ; "W/", case-sensitive
658  <a href="#entity.tags" class="smpl">opaque-tag</a> = <a href="#core.rules" class="smpl">quoted-string</a>
659</pre><p id="rfc.section.2.p.3">A "strong entity-tag" <em class="bcp14">MAY</em> be shared by two representations of a resource only if they are equivalent by octet equality.
660         </p>
661         <p id="rfc.section.2.p.4">A "weak entity-tag", indicated by the "W/" prefix, <em class="bcp14">MAY</em> be shared by two representations of a resource only if the representations are equivalent and could be substituted for each
662            other with no significant change in semantics. A weak entity-tag can only be used for weak comparison.
663         </p>
664         <p id="rfc.section.2.p.5">An entity-tag <em class="bcp14">MUST</em> be unique across all versions of all representations associated with a particular resource. A given entity-tag value <em class="bcp14">MAY</em> be used for representations obtained by requests on different URIs. The use of the same entity-tag value in conjunction with
665            representations obtained by requests on different URIs does not imply the equivalence of those representations.
666         </p>
667         <div id="example.entity.tag.vs.conneg">
668            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#example.entity.tag.vs.conneg">Example: Entity-tags varying on Content-Negotiated Resources</a></h2>
669            <p id="rfc.section.2.1.p.1">Consider a resource that is subject to content negotiation (<a href="p3-payload.html#content.negotiation" title="Content Negotiation">Section 5</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>), and where the representations returned upon a GET request vary based on the Accept-Encoding request header field (<a href="p3-payload.html#header.accept-encoding" title="Accept-Encoding">Section 6.3</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>):
670            </p>
671            <div id="rfc.figure.u.4"></div>
672            <p>&gt;&gt; Request:</p><pre class="text2">GET /index HTTP/1.1
674Accept-Encoding: gzip
676</pre><p id="rfc.section.2.1.p.3">In this case, the response might or might not use the gzip content coding. If it does not, the response might look like:</p>
677            <div id="rfc.figure.u.5"></div>
678            <p>&gt;&gt; Response:</p><pre class="text">HTTP/1.1 200 OK
679Date: Thu, 26 Mar 2010 00:05:00 GMT
680ETag: "123-a"
681Content-Length: 70
682Vary: Accept-Encoding
683Content-Type: text/plain
685<span id="exbody">Hello World!
686Hello World!
687Hello World!
688Hello World!
689Hello World!
690</span></pre><p id="rfc.section.2.1.p.5">An alternative representation that does use gzip content coding would be:</p>
691            <div id="rfc.figure.u.6"></div>
692            <p>&gt;&gt; Response:</p><pre class="text">HTTP/1.1 200 OK
693Date: Thu, 26 Mar 2010 00:05:00 GMT
694ETag: "123-b"
695Content-Length: 43
696Vary: Accept-Encoding
697Content-Type: text/plain
698Content-Encoding: gzip
700<em>...binary data...</em></pre><div class="note" id="rfc.section.2.1.p.7">
701               <p><b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation must be distinct
702                  from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
703                  (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 6.2</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) apply only during message transfer and do not require distinct entity-tags.
704               </p>
705            </div>
706         </div>
707      </div>
708      <div id="status.code.definitions">
709         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
710         <div id="status.304">
711            <div id="rfc.iref.3.1"></div>
712            <div id="rfc.iref.s.1"></div>
713            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#status.304">304 Not Modified</a></h2>
714            <p id="rfc.section.3.1.p.1">If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server <em class="bcp14">SHOULD</em> respond with this status code. The 304 response <em class="bcp14">MUST NOT</em> contain a message-body, and thus is always terminated by the first empty line after the header fields.
715            </p>
716            <p id="rfc.section.3.1.p.2">A 304 response <em class="bcp14">MUST</em> include a Date header field (<a href="" title="Date">Section 9.3</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) unless its omission is required by <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 9.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. If a 200 response to the same request would have included any of the header fields Cache-Control, Content-Location, ETag,
717               Expires, Last-Modified, or Vary, then those same header fields <em class="bcp14">MUST</em> be sent in a 304 response.
718            </p>
719            <p id="rfc.section.3.1.p.3">Since the goal of a 304 response is to minimize information transfer when the recipient already has one or more cached representations,
720               the response <em class="bcp14">SHOULD NOT</em> include representation metadata other than the above listed fields unless said metadata exists for the purpose of guiding
721               cache updates (e.g., future HTTP extensions).
722            </p>
723            <p id="rfc.section.3.1.p.4">If a 304 response includes an entity-tag that indicates a representation not currently cached, then the recipient <em class="bcp14">MUST NOT</em> use the 304 to update its own cache. If that conditional request originated with an outbound client, such as a user agent
724               with its own cache sending a conditional GET to a shared proxy, then the 304 response <em class="bcp14">MAY</em> be forwarded to the outbound client. Otherwise, disregard the response and repeat the request without the conditional.
725            </p>
726            <p id="rfc.section.3.1.p.5">If a cache uses a received 304 response to update a cache entry, the cache <em class="bcp14">MUST</em> update the entry to reflect any new field values given in the response.
727            </p>
728         </div>
729         <div id="status.412">
730            <div id="rfc.iref.4.1"></div>
731            <div id="rfc.iref.s.2"></div>
732            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#status.412">412 Precondition Failed</a></h2>
733            <p id="rfc.section.3.2.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This
734               response code allows the client to place preconditions on the current resource metadata (header field data) and thus prevent
735               the requested method from being applied to a resource other than the one intended.
736            </p>
737         </div>
738      </div>
739      <div id="weak.and.strong.validators">
740         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#weak.and.strong.validators">Weak and Strong Validators</a></h1>
741         <p id="rfc.section.4.p.1">Since both origin servers and caches will compare two validators to decide if they represent the same or different representations,
742            one normally would expect that if the representation (including both representation header fields and representation body)
743            changes in any way, then the associated validator would change as well. If this is true, then we call this validator a "strong
744            validator".
745         </p>
746         <p id="rfc.section.4.p.2">However, there might be cases when a server prefers to change the validator only on semantically significant changes, and
747            not when insignificant aspects of the representation change. A validator that does not always change when the representation
748            changes is a "weak validator".
749         </p>
750         <p id="rfc.section.4.p.3">An entity-tag is normally a strong validator, but the protocol provides a mechanism to tag an entity-tag as "weak". One can
751            think of a strong validator as one that changes whenever the sequence of bits in a representation changes, while a weak value
752            changes whenever the meaning of a representation changes. Alternatively, one can think of a strong validator as part of an
753            identifier for a specific representation, whereas a weak validator is part of an identifier for a set of semantically equivalent
754            representations.
755         </p>
756         <ul class="empty">
757            <li><b>Note:</b> One example of a strong validator is an integer that is incremented in stable storage every time a representation is changed.
758            </li>
759            <li>A representation's modification time, if defined with only one-second resolution, could be a weak validator, since it is possible
760               that the representation might be modified twice during a single second.
761            </li>
762            <li>Support for weak validators is optional. However, weak validators allow for more efficient caching of equivalent objects;
763               for example, a hit counter on a site is probably good enough if it is updated every few days or weeks, and any value during
764               that period is likely "good enough" to be equivalent.
765            </li>
766         </ul>
767         <p id="rfc.section.4.p.4">A "use" of a validator is either when a client generates a request and includes the validator in a validating header field,
768            or when a server compares two validators.
769         </p>
770         <p id="rfc.section.4.p.5">Strong validators are usable in any context. Weak validators are only usable in contexts that do not depend on exact equality
771            of a representation. For example, either kind is usable for a normal conditional GET. However, only a strong validator is
772            usable for a sub-range retrieval, since otherwise the client might end up with an internally inconsistent representation.
773         </p>
774         <p id="rfc.section.4.p.6">Clients <em class="bcp14">MUST NOT</em> use weak validators in range requests (<a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>).
775         </p>
776         <p id="rfc.section.4.p.7">The only function that HTTP/1.1 defines on validators is comparison. There are two validator comparison functions, depending
777            on whether the comparison context allows the use of weak validators or not:
778         </p>
779         <ul>
780            <li>The strong comparison function: in order to be considered equal, both opaque-tags <em class="bcp14">MUST</em> be identical character-by-character, and both <em class="bcp14">MUST NOT</em> be weak.
781            </li>
782            <li>The weak comparison function: in order to be considered equal, both opaque-tags <em class="bcp14">MUST</em> be identical character-by-character, but either or both of them <em class="bcp14">MAY</em> be tagged as "weak" without affecting the result.
783            </li>
784         </ul>
785         <p id="rfc.section.4.p.8">The example below shows the results for a set of entity-tag pairs, and both the weak and strong comparison function results:</p>
786         <div id="rfc.table.u.1">
787            <table class="tt full left" cellpadding="3" cellspacing="0">
788               <thead>
789                  <tr>
790                     <th>ETag 1</th>
791                     <th>ETag 2</th>
792                     <th>Strong Comparison</th>
793                     <th>Weak Comparison</th>
794                  </tr>
795               </thead>
796               <tbody>
797                  <tr>
798                     <td class="left">W/"1"</td>
799                     <td class="left">W/"1"</td>
800                     <td class="left">no match</td>
801                     <td class="left">match</td>
802                  </tr>
803                  <tr>
804                     <td class="left">W/"1"</td>
805                     <td class="left">W/"2"</td>
806                     <td class="left">no match</td>
807                     <td class="left">no match</td>
808                  </tr>
809                  <tr>
810                     <td class="left">W/"1"</td>
811                     <td class="left">"1"</td>
812                     <td class="left">no match</td>
813                     <td class="left">match</td>
814                  </tr>
815                  <tr>
816                     <td class="left">"1"</td>
817                     <td class="left">"1"</td>
818                     <td class="left">match</td>
819                     <td class="left">match</td>
820                  </tr>
821               </tbody>
822            </table>
823         </div>
824         <p id="rfc.section.4.p.9">An entity-tag is strong unless it is explicitly tagged as weak. <a href="#entity.tags" title="Entity-Tags">Section&nbsp;2</a> gives the syntax for entity-tags.
825         </p>
826         <p id="rfc.section.4.p.10">A Last-Modified time, when used as a validator in a request, is implicitly weak unless it is possible to deduce that it is
827            strong, using the following rules:
828         </p>
829         <ul>
830            <li>The validator is being compared by an origin server to the actual current validator for the representation and,</li>
831            <li>That origin server reliably knows that the associated representation did not change twice during the second covered by the
832               presented validator.
833            </li>
834         </ul>
835         <p id="rfc.section.4.p.11">or </p>
836         <ul>
837            <li>The validator is about to be used by a client in an If-Modified-Since or If-Unmodified-Since header, because the client has
838               a cache entry for the associated representation, and
839            </li>
840            <li>That cache entry includes a Date value, which gives the time when the origin server sent the original response, and</li>
841            <li>The presented Last-Modified time is at least 60 seconds before the Date value.</li>
842         </ul>
843         <p id="rfc.section.4.p.12">or </p>
844         <ul>
845            <li>The validator is being compared by an intermediate cache to the validator stored in its cache entry for the representation,
846               and
847            </li>
848            <li>That cache entry includes a Date value, which gives the time when the origin server sent the original response, and</li>
849            <li>The presented Last-Modified time is at least 60 seconds before the Date value.</li>
850         </ul>
851         <p id="rfc.section.4.p.13">This method relies on the fact that if two different responses were sent by the origin server during the same second, but
852            both had the same Last-Modified time, then at least one of those responses would have a Date value equal to its Last-Modified
853            time. The arbitrary 60-second limit guards against the possibility that the Date and Last-Modified values are generated from
854            different clocks, or at somewhat different times during the preparation of the response. An implementation <em class="bcp14">MAY</em> use a value larger than 60 seconds, if it is believed that 60 seconds is too short.
855         </p>
856         <p id="rfc.section.4.p.14">If a client wishes to perform a sub-range retrieval on a value for which it has only a Last-Modified time and no opaque validator,
857            it <em class="bcp14">MAY</em> do this only if the Last-Modified time is strong in the sense described here.
858         </p>
859         <p id="rfc.section.4.p.15">A cache or origin server receiving a conditional range request (<a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) <em class="bcp14">MUST</em> use the strong comparison function to evaluate the condition.
860         </p>
861         <p id="rfc.section.4.p.16">These rules allow HTTP/1.1 caches and clients to safely perform sub-range retrievals on values that have been obtained from
862            HTTP/1.0 servers.
863         </p>
864      </div>
865      <div id="">
866         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="">Rules for When to Use Entity-tags and Last-Modified Dates</a></h1>
867         <p id="rfc.section.5.p.1">We adopt a set of rules and recommendations for origin servers, clients, and caches regarding when various validator types
868            ought to be used, and for what purposes.
869         </p>
870         <p id="rfc.section.5.p.2">HTTP/1.1 origin servers: </p>
871         <ul>
872            <li><em class="bcp14">SHOULD</em> send an entity-tag validator unless it is not feasible to generate one.
873            </li>
874            <li><em class="bcp14">MAY</em> send a weak entity-tag instead of a strong entity-tag, if performance considerations support the use of weak entity-tags,
875               or if it is unfeasible to send a strong entity-tag.
876            </li>
877            <li><em class="bcp14">SHOULD</em> send a Last-Modified value if it is feasible to send one, unless the risk of a breakdown in semantic transparency that could
878               result from using this date in an If-Modified-Since header would lead to serious problems.
879            </li>
880         </ul>
881         <p id="rfc.section.5.p.3">In other words, the preferred behavior for an HTTP/1.1 origin server is to send both a strong entity-tag and a Last-Modified
882            value.
883         </p>
884         <p id="rfc.section.5.p.4">In order to be legal, a strong entity-tag <em class="bcp14">MUST</em> change whenever the associated representation changes in any way. A weak entity-tag <em class="bcp14">SHOULD</em> change whenever the associated representation changes in a semantically significant way.
885         </p>
886         <div class="note" id="rfc.section.5.p.5">
887            <p><b>Note:</b> In order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity-tag value
888               for two different representations, or reusing a specific weak entity-tag value for two semantically different representations.
889               Cache entries might persist for arbitrarily long periods, regardless of expiration times, so it might be inappropriate to
890               expect that a cache will never again attempt to validate an entry using a validator that it obtained at some point in the
891               past.
892            </p>
893         </div>
894         <p id="rfc.section.5.p.6">HTTP/1.1 clients: </p>
895         <ul>
896            <li><em class="bcp14">MUST</em> use that entity-tag in any cache-conditional request (using If-Match or If-None-Match) if an entity-tag has been provided
897               by the origin server.
898            </li>
899            <li><em class="bcp14">SHOULD</em> use the Last-Modified value in non-subrange cache-conditional requests (using If-Modified-Since) if only a Last-Modified value
900               has been provided by the origin server.
901            </li>
902            <li><em class="bcp14">MAY</em> use the Last-Modified value in subrange cache-conditional requests (using If-Unmodified-Since) if only a Last-Modified value
903               has been provided by an HTTP/1.0 origin server. The user agent <em class="bcp14">SHOULD</em> provide a way to disable this, in case of difficulty.
904            </li>
905            <li><em class="bcp14">SHOULD</em> use both validators in cache-conditional requests if both an entity-tag and a Last-Modified value have been provided by the
906               origin server. This allows both HTTP/1.0 and HTTP/1.1 caches to respond appropriately.
907            </li>
908         </ul>
909         <p id="rfc.section.5.p.7">An HTTP/1.1 origin server, upon receiving a conditional request that includes both a Last-Modified date (e.g., in an If-Modified-Since
910            or If-Unmodified-Since header field) and one or more entity-tags (e.g., in an If-Match, If-None-Match, or If-Range header
911            field) as cache validators, <em class="bcp14">MUST NOT</em> return a response status code of 304 (Not Modified) unless doing so is consistent with all of the conditional header fields
912            in the request.
913         </p>
914         <p id="rfc.section.5.p.8">An HTTP/1.1 caching proxy, upon receiving a conditional request that includes both a Last-Modified date and one or more entity-tags
915            as cache validators, <em class="bcp14">MUST NOT</em> return a locally cached response to the client unless that cached response is consistent with all of the conditional header
916            fields in the request.
917         </p>
918         <ul class="empty">
919            <li><b>Note:</b> The general principle behind these rules is that HTTP/1.1 servers and clients ought to transmit as much non-redundant information
920               as is available in their responses and requests. HTTP/1.1 systems receiving this information will make the most conservative
921               assumptions about the validators they receive.
922            </li>
923            <li>HTTP/1.0 clients and caches will ignore entity-tags. Generally, last-modified values received or used by these systems will
924               support transparent and efficient caching, and so HTTP/1.1 origin servers should provide Last-Modified values. In those rare
925               cases where the use of a Last-Modified value as a validator by an HTTP/1.0 system could result in a serious problem, then
926               HTTP/1.1 origin servers should not provide one.
927            </li>
928         </ul>
929      </div>
930      <div id="header.fields">
931         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
932         <p id="rfc.section.6.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to conditional requests.</p>
933         <div id="header.etag">
934            <div id="rfc.iref.e.1"></div>
935            <div id="rfc.iref.h.1"></div>
936            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#header.etag">ETag</a></h2>
937            <p id="rfc.section.6.1.p.1">The "ETag" response-header field provides the current value of the entity-tag (see <a href="#entity.tags" title="Entity-Tags">Section&nbsp;2</a>) for one representation of the target resource. An entity-tag is intended for use as a resource-local identifier for differentiating
938               between representations of the same resource that vary over time or via content negotiation (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>).
939            </p>
940            <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span>  <a href="#header.etag" class="smpl">ETag</a>   = "ETag" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.etag" class="smpl">ETag-v</a>
941  <a href="#header.etag" class="smpl">ETag-v</a> = <a href="#entity.tags" class="smpl">entity-tag</a>
942</pre><div id="rfc.figure.u.8"></div>
943            <p>Examples:</p><pre class="text">  ETag: "xyzzy"
944  ETag: W/"xyzzy"
945  ETag: ""
946</pre><p id="rfc.section.6.1.p.4">An entity-tag provides an "opaque" cache validator that allows for more reliable validation than modification dates in situations
947               where it is inconvenient to store modification dates, where the one-second resolution of HTTP date values is not sufficient,
948               or where the origin server wishes to avoid certain paradoxes that might arise from the use of modification dates.
949            </p>
950            <p id="rfc.section.6.1.p.5">The principle behind entity-tags is that only the service author knows the semantics of a resource well enough to select an
951               appropriate cache validation mechanism, and the specification of any validator comparison function more complex than byte-equality
952               would open up a can of worms. Thus, comparisons of any other headers (except Last-Modified, for compatibility with HTTP/1.0)
953               are never used for purposes of validating a cache entry.
954            </p>
955         </div>
956         <div id="header.if-match">
957            <div id="rfc.iref.i.1"></div>
958            <div id="rfc.iref.h.2"></div>
959            <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a href="#header.if-match">If-Match</a></h2>
960            <p id="rfc.section.6.2.p.1">The "If-Match" request-header field is used to make a request method conditional. A client that has one or more representations
961               previously obtained from the resource can verify that one of those representations is current by including a list of their
962               associated entity-tags in the If-Match header field.
963            </p>
964            <p id="rfc.section.6.2.p.2">This allows efficient updates of cached information with a minimum amount of transaction overhead. It is also used when updating
965               resources, to prevent inadvertent modification of the wrong version of a resource. As a special case, the value "*" matches
966               any current representation of the resource.
967            </p>
968            <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.6"></span><span id="rfc.iref.g.7"></span>  <a href="#header.if-match" class="smpl">If-Match</a>   = "If-Match" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-match" class="smpl">If-Match-v</a>
969  <a href="#header.if-match" class="smpl">If-Match-v</a> = "*" / 1#<a href="#entity.tags" class="smpl">entity-tag</a>
970</pre><p id="rfc.section.6.2.p.4">If any of the entity-tags match the entity-tag of the representation that would have been returned in the response to a similar
971               GET request (without the If-Match header) on that resource, or if "*" is given and any current representation exists for that
972               resource, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-Match header field did not exist.
973            </p>
974            <p id="rfc.section.6.2.p.5">If none of the entity-tags match, or if "*" is given and no current representation exists, the server <em class="bcp14">MUST NOT</em> perform the requested method, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed) response. This behavior is most useful when the client wants to prevent an updating method,
975               such as PUT, from modifying a resource that has changed since the client last retrieved it.
976            </p>
977            <p id="rfc.section.6.2.p.6">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status code, then the
978               If-Match header <em class="bcp14">MUST</em> be ignored.
979            </p>
980            <p id="rfc.section.6.2.p.7">The meaning of "If-Match: *" is that the method <em class="bcp14">SHOULD</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">MUST NOT</em> be performed if the representation does not exist.
981            </p>
982            <p id="rfc.section.6.2.p.8">A request intended to update a resource (e.g., a PUT) <em class="bcp14">MAY</em> include an If-Match header field to signal that the request method <em class="bcp14">MUST NOT</em> be applied if the representation corresponding to the If-Match value (a single entity-tag) is no longer a representation of
983               that resource. This allows the user to indicate that they do not wish the request to be successful if the resource has been
984               changed without their knowledge. Examples:
985            </p>
986            <div id="rfc.figure.u.10"></div><pre class="text">  If-Match: "xyzzy"
987  If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
988  If-Match: *
989</pre><p id="rfc.section.6.2.p.10">The result of a request having both an If-Match header field and either an If-None-Match or an If-Modified-Since header fields
990               is undefined by this specification.
991            </p>
992         </div>
993         <div id="header.if-modified-since">
994            <div id="rfc.iref.i.2"></div>
995            <div id="rfc.iref.h.3"></div>
996            <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></h2>
997            <p id="rfc.section.6.3.p.1">The "If-Modified-Since" request-header field is used to make a request method conditional by date: if the representation that
998               would have been transferred in a 200 response to a GET request has not been modified since the time specified in this field,
999               then do not perform the method; instead, respond as detailed below.
1000            </p>
1001            <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.8"></span><span id="rfc.iref.g.9"></span>  <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a>   = "If-Modified-Since" ":" <a href="#core.rules" class="smpl">OWS</a>
1002                        <a href="#header.if-modified-since" class="smpl">If-Modified-Since-v</a>
1003  <a href="#header.if-modified-since" class="smpl">If-Modified-Since-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
1004</pre><p id="rfc.section.6.3.p.3">An example of the field is:</p>
1005            <div id="rfc.figure.u.12"></div><pre class="text">  If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
1006</pre><p id="rfc.section.6.3.p.5">A GET method with an If-Modified-Since header and no Range header requests that the representation be transferred only if
1007               it has been modified since the date given by the If-Modified-Since header. The algorithm for determining this includes the
1008               following cases:
1009            </p>
1010            <ol>
1011               <li>If the request would normally result in anything other than a 200 (OK) status code, or if the passed If-Modified-Since date
1012                  is invalid, the response is exactly the same as for a normal GET. A date which is later than the server's current time is
1013                  invalid.
1014               </li>
1015               <li>If the representation has been modified since the If-Modified-Since date, the response is exactly the same as for a normal
1016                  GET.
1017               </li>
1018               <li>If the representation has not been modified since a valid If-Modified-Since date, the server <em class="bcp14">SHOULD</em> return a 304 (Not Modified) response.
1019               </li>
1020            </ol>
1021            <p id="rfc.section.6.3.p.6">The purpose of this feature is to allow efficient updates of cached information with a minimum amount of transaction overhead. </p>
1022            <ul class="empty">
1023               <li><b>Note:</b> The Range request-header field modifies the meaning of If-Modified-Since; see <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> for full details.
1024               </li>
1025               <li><b>Note:</b> If-Modified-Since times are interpreted by the server, whose clock might not be synchronized with the client.
1026               </li>
1027               <li><b>Note:</b> When handling an If-Modified-Since header field, some servers will use an exact date comparison function, rather than a less-than
1028                  function, for deciding whether to send a 304 (Not Modified) response. To get best results when sending an If-Modified-Since
1029                  header field for cache validation, clients are advised to use the exact date string received in a previous Last-Modified header
1030                  field whenever possible.
1031               </li>
1032               <li><b>Note:</b> If a client uses an arbitrary date in the If-Modified-Since header instead of a date taken from the Last-Modified header for
1033                  the same request, the client needs to be aware that this date is interpreted in the server's understanding of time. Unsynchronized
1034                  clocks and rounding problems, due to the different encodings of time between the client and server, are concerns. This includes
1035                  the possibility of race conditions if the document has changed between the time it was first requested and the If-Modified-Since
1036                  date of a subsequent request, and the possibility of clock-skew-related problems if the If-Modified-Since date is derived
1037                  from the client's clock without correction to the server's clock. Corrections for different time bases between client and
1038                  server are at best approximate due to network latency.
1039               </li>
1040            </ul>
1041            <p id="rfc.section.6.3.p.7">The result of a request having both an If-Modified-Since header field and either an If-Match or an If-Unmodified-Since header
1042               fields is undefined by this specification.
1043            </p>
1044         </div>
1045         <div id="header.if-none-match">
1046            <div id="rfc.iref.i.3"></div>
1047            <div id="rfc.iref.h.4"></div>
1048            <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a href="#header.if-none-match">If-None-Match</a></h2>
1049            <p id="rfc.section.6.4.p.1">The "If-None-Match" request-header field is used to make a request method conditional. A client that has one or more representations
1050               previously obtained from the resource can verify that none of those representations is current by including a list of their
1051               associated entity-tags in the If-None-Match header field.
1052            </p>
1053            <p id="rfc.section.6.4.p.2">This allows efficient updates of cached information with a minimum amount of transaction overhead. It is also used to prevent
1054               a method (e.g., PUT) from inadvertently modifying an existing resource when the client believes that the resource does not
1055               exist.
1056            </p>
1057            <p id="rfc.section.6.4.p.3">As a special case, the value "*" matches any current representation of the resource.</p>
1058            <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.10"></span><span id="rfc.iref.g.11"></span>  <a href="#header.if-none-match" class="smpl">If-None-Match</a>   = "If-None-Match" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.if-none-match" class="smpl">If-None-Match-v</a>
1059  <a href="#header.if-none-match" class="smpl">If-None-Match-v</a> = "*" / 1#<a href="#entity.tags" class="smpl">entity-tag</a>
1060</pre><p id="rfc.section.6.4.p.5">If any of the entity-tags match the entity-tag of the representation that would have been returned in the response to a similar
1061               GET request (without the If-None-Match header) on that resource, or if "*" is given and any current representation exists
1062               for that resource, then the server <em class="bcp14">MUST NOT</em> perform the requested method, unless required to do so because the resource's modification date fails to match that supplied
1063               in an If-Modified-Since header field in the request. Instead, if the request method was GET or HEAD, the server <em class="bcp14">SHOULD</em> respond with a 304 (Not Modified) response, including the cache-related header fields (particularly ETag) of one of the representations
1064               that matched. For all other request methods, the server <em class="bcp14">MUST</em> respond with a 412 (Precondition Failed) status code.
1065            </p>
1066            <p id="rfc.section.6.4.p.6">If none of the entity-tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity-tags match, then the server <em class="bcp14">MUST NOT</em> return a 304 (Not Modified) response.
1067            </p>
1068            <p id="rfc.section.6.4.p.7">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status code, then
1069               the If-None-Match header <em class="bcp14">MUST</em> be ignored. (See <a href="" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section&nbsp;5</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
1070            </p>
1071            <p id="rfc.section.6.4.p.8">The meaning of "If-None-Match: *" is that the method <em class="bcp14">MUST NOT</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 3.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">SHOULD</em> be performed if the representation does not exist. This feature is intended to be useful in preventing races between PUT operations.
1072            </p>
1073            <p id="rfc.section.6.4.p.9">Examples:</p>
1074            <div id="rfc.figure.u.14"></div><pre class="text">  If-None-Match: "xyzzy"
1075  If-None-Match: W/"xyzzy"
1076  If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
1077  If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
1078  If-None-Match: *
1079</pre><p id="rfc.section.6.4.p.11">The result of a request having both an If-None-Match header field and either an If-Match or an If-Unmodified-Since header
1080               fields is undefined by this specification.
1081            </p>
1082         </div>
1083         <div id="header.if-unmodified-since">
1084            <div id="rfc.iref.i.4"></div>
1085            <div id="rfc.iref.h.5"></div>
1086            <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></h2>
1087            <p id="rfc.section.6.5.p.1">The "If-Unmodified-Since" request-header field is used to make a request method conditional. If the representation that would
1088               have been transferred in a 200 response to a GET request on the same resource has not been modified since the time specified
1089               in this field, the server <em class="bcp14">SHOULD</em> perform the requested operation as if the If-Unmodified-Since header were not present.
1090            </p>
1091            <p id="rfc.section.6.5.p.2">If the representation has been modified since the specified time, the server <em class="bcp14">MUST NOT</em> perform the requested operation, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed).
1092            </p>
1093            <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.12"></span><span id="rfc.iref.g.13"></span>  <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a>   = "If-Unmodified-Since" ":" <a href="#core.rules" class="smpl">OWS</a>
1094                          <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since-v</a>
1095  <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
1096</pre><p id="rfc.section.6.5.p.4">An example of the field is:</p>
1097            <div id="rfc.figure.u.16"></div><pre class="text">  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
1098</pre><p id="rfc.section.6.5.p.6">If the request normally (i.e., without the If-Unmodified-Since header) would result in anything other than a 2xx or 412 status
1099               code, the If-Unmodified-Since header <em class="bcp14">SHOULD</em> be ignored.
1100            </p>
1101            <p id="rfc.section.6.5.p.7">If the specified date is invalid, the header is ignored.</p>
1102            <p id="rfc.section.6.5.p.8">The result of a request having both an If-Unmodified-Since header field and either an If-None-Match or an If-Modified-Since
1103               header fields is undefined by this specification.
1104            </p>
1105         </div>
1106         <div id="header.last-modified">
1107            <div id="rfc.iref.l.1"></div>
1108            <div id="rfc.iref.h.6"></div>
1109            <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a href="#header.last-modified">Last-Modified</a></h2>
1110            <p id="rfc.section.6.6.p.1">The "Last-Modified" header field indicates the date and time at which the origin server believes the representation was last
1111               modified.
1112            </p>
1113            <div id="rfc.figure.u.17"></div><pre class="inline"><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#header.last-modified" class="smpl">Last-Modified</a>   = "Last-Modified" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.last-modified" class="smpl">Last-Modified-v</a>
1114  <a href="#header.last-modified" class="smpl">Last-Modified-v</a> = <a href="#abnf.dependencies" class="smpl">HTTP-date</a>
1115</pre><p id="rfc.section.6.6.p.3">An example of its use is</p>
1116            <div id="rfc.figure.u.18"></div><pre class="text">  Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
1117</pre><p id="rfc.section.6.6.p.5">The exact meaning of this header field depends on the implementation of the origin server and the nature of the original resource.
1118               For files, it might be just the file system last-modified time. For representations with dynamically included parts, it might
1119               be the most recent of the set of last-modify times for its component parts. For database gateways, it might be the last-update
1120               time stamp of the record. For virtual objects, it might be the last time the internal state changed.
1121            </p>
1122            <p id="rfc.section.6.6.p.6">An origin server <em class="bcp14">MUST NOT</em> send a Last-Modified date which is later than the server's time of message origination. In such cases, where the resource's
1123               last modification would indicate some time in the future, the server <em class="bcp14">MUST</em> replace that date with the message origination date.
1124            </p>
1125            <p id="rfc.section.6.6.p.7">An origin server <em class="bcp14">SHOULD</em> obtain the Last-Modified value of the representation as close as possible to the time that it generates the Date value of
1126               its response. This allows a recipient to make an accurate assessment of the representation's modification time, especially
1127               if the representation changes near the time that the response is generated.
1128            </p>
1129            <p id="rfc.section.6.6.p.8">HTTP/1.1 servers <em class="bcp14">SHOULD</em> send Last-Modified whenever feasible.
1130            </p>
1131            <p id="rfc.section.6.6.p.9">The Last-Modified header field value is often used as a cache validator. In simple terms, a cache entry is considered to be
1132               valid if the representation has not been modified since the Last-Modified value.
1133            </p>
1134         </div>
1135      </div>
1136      <div id="IANA.considerations">
1137         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
1138         <div id="status.code.registration">
1139            <h2 id="rfc.section.7.1"><a href="#rfc.section.7.1">7.1</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
1140            <p id="rfc.section.7.1.p.1">The HTTP Status Code Registry located at &lt;<a href=""></a>&gt; shall be updated with the registrations below:
1141            </p>
1142            <div id="rfc.table.1">
1143               <div id="iana.status.code.registration.table"></div>
1144               <table class="tt full left" cellpadding="3" cellspacing="0">
1145                  <thead>
1146                     <tr>
1147                        <th>Value</th>
1148                        <th>Description</th>
1149                        <th>Reference</th>
1150                     </tr>
1151                  </thead>
1152                  <tbody>
1153                     <tr>
1154                        <td class="left">304</td>
1155                        <td class="left">Not Modified</td>
1156                        <td class="left"><a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;3.1</a>
1157                        </td>
1158                     </tr>
1159                     <tr>
1160                        <td class="left">412</td>
1161                        <td class="left">Precondition Failed</td>
1162                        <td class="left"><a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;3.2</a>
1163                        </td>
1164                     </tr>
1165                  </tbody>
1166               </table>
1167            </div>
1168         </div>
1169         <div id="header.field.registration">
1170            <h2 id="rfc.section.7.2"><a href="#rfc.section.7.2">7.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
1171            <p id="rfc.section.7.2.p.1">The Message Header Field Registry located at &lt;<a href=""></a>&gt; 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>):
1172            </p>
1173            <div id="rfc.table.2">
1174               <div id="iana.header.registration.table"></div>
1175               <table class="tt full left" cellpadding="3" cellspacing="0">
1176                  <thead>
1177                     <tr>
1178                        <th>Header Field Name</th>
1179                        <th>Protocol</th>
1180                        <th>Status</th>
1181                        <th>Reference</th>
1182                     </tr>
1183                  </thead>
1184                  <tbody>
1185                     <tr>
1186                        <td class="left">ETag</td>
1187                        <td class="left">http</td>
1188                        <td class="left">standard</td>
1189                        <td class="left"><a href="#header.etag" id="rfc.xref.header.etag.2" title="ETag">Section&nbsp;6.1</a>
1190                        </td>
1191                     </tr>
1192                     <tr>
1193                        <td class="left">If-Match</td>
1194                        <td class="left">http</td>
1195                        <td class="left">standard</td>
1196                        <td class="left"><a href="#header.if-match" id="rfc.xref.header.if-match.2" title="If-Match">Section&nbsp;6.2</a>
1197                        </td>
1198                     </tr>
1199                     <tr>
1200                        <td class="left">If-Modified-Since</td>
1201                        <td class="left">http</td>
1202                        <td class="left">standard</td>
1203                        <td class="left"><a href="#header.if-modified-since" id="rfc.xref.header.if-modified-since.1" title="If-Modified-Since">Section&nbsp;6.3</a>
1204                        </td>
1205                     </tr>
1206                     <tr>
1207                        <td class="left">If-None-Match</td>
1208                        <td class="left">http</td>
1209                        <td class="left">standard</td>
1210                        <td class="left"><a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">Section&nbsp;6.4</a>
1211                        </td>
1212                     </tr>
1213                     <tr>
1214                        <td class="left">If-Unmodified-Since</td>
1215                        <td class="left">http</td>
1216                        <td class="left">standard</td>
1217                        <td class="left"><a href="#header.if-unmodified-since" id="rfc.xref.header.if-unmodified-since.1" title="If-Unmodified-Since">Section&nbsp;6.5</a>
1218                        </td>
1219                     </tr>
1220                     <tr>
1221                        <td class="left">Last-Modified</td>
1222                        <td class="left">http</td>
1223                        <td class="left">standard</td>
1224                        <td class="left"><a href="#header.last-modified" id="rfc.xref.header.last-modified.1" title="Last-Modified">Section&nbsp;6.6</a>
1225                        </td>
1226                     </tr>
1227                  </tbody>
1228               </table>
1229            </div>
1230            <p id="rfc.section.7.2.p.2">The change controller is: "IETF ( - Internet Engineering Task Force".</p>
1231         </div>
1232      </div>
1233      <div id="security.considerations">
1234         <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
1235         <p id="rfc.section.8.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
1236         </p>
1237      </div>
1238      <div id="ack">
1239         <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
1240      </div>
1241      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
1242      </h1>
1243      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
1244      </h2>
1245      <table>
1246         <tr>
1247            <td class="reference"><b id="Part1">[Part1]</b></td>
1248            <td class="top"><a href="" title="Day Software">Fielding, R., Ed.</a>, <a href="" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="" title="Microsoft Corporation">Frystyk, H.</a>, <a href="" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, <a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-11 (work in progress), August&nbsp;2010.
1249            </td>
1250         </tr>
1251         <tr>
1252            <td class="reference"><b id="Part3">[Part3]</b></td>
1253            <td class="top"><a href="" title="Day Software">Fielding, R., Ed.</a>, <a href="" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="" title="Microsoft Corporation">Frystyk, H.</a>, <a href="" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, <a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-11 (work in progress), August&nbsp;2010.
1254            </td>
1255         </tr>
1256         <tr>
1257            <td class="reference"><b id="Part5">[Part5]</b></td>
1258            <td class="top"><a href="" title="Day Software">Fielding, R., Ed.</a>, <a href="" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="" title="Microsoft Corporation">Frystyk, H.</a>, <a href="" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, <a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-11 (work in progress), August&nbsp;2010.
1259            </td>
1260         </tr>
1261         <tr>
1262            <td class="reference"><b id="Part6">[Part6]</b></td>
1263            <td class="top"><a href="" title="Day Software">Fielding, R., Ed.</a>, <a href="" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="" title="Microsoft Corporation">Frystyk, H.</a>, <a href="" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, <a href="" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="">Nottingham, M., Ed.</a>, and <a href="" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-11 (work in progress), August&nbsp;2010.
1264            </td>
1265         </tr>
1266         <tr>
1267            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1268            <td class="top"><a href="" title="Harvard University">Bradner, S.</a>, “<a href="">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
1269            </td>
1270         </tr>
1271         <tr>
1272            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1273            <td class="top"><a href="" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="" title="THUS plc.">P. Overell</a>, “<a href="">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
1274            </td>
1275         </tr>
1276      </table>
1277      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
1278      </h2>
1279      <table>
1280         <tr>
1281            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1282            <td class="top"><a href="" title="University of California, Irvine">Fielding, R.</a>, <a href="" title="W3C">Gettys, J.</a>, <a href="" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="" title="Xerox Corporation">Masinter, L.</a>, <a href="" title="Microsoft Corporation">Leach, P.</a>, and <a href="" title="W3C">T. Berners-Lee</a>, “<a href="">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
1283            </td>
1284         </tr>
1285         <tr>
1286            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1287            <td class="top"><a href="" title="Nine by Nine">Klyne, G.</a>, <a href="" title="BEA Systems">Nottingham, M.</a>, and <a href="" title="HP Labs">J. Mogul</a>, “<a href="">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
1288            </td>
1289         </tr>
1290      </table>
1291      <div id="changes.from.rfc.2616">
1292         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h1>
1293         <p id="rfc.section.A.p.1">Allow weak entity-tags in all requests except range requests (Sections <a href="#weak.and.strong.validators" title="Weak and Strong Validators">4</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.3" title="If-None-Match">6.4</a>).
1294         </p>
1295      </div>
1296      <div id="collected.abnf">
1297         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
1298         <div id="rfc.figure.u.19"></div><pre class="inline"><a href="#header.etag" class="smpl">ETag</a> = "ETag:" OWS ETag-v
1299<a href="#header.etag" class="smpl">ETag-v</a> = entity-tag
1301<a href="#abnf.dependencies" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part1], Section 6.1&gt;
1303<a href="#header.if-match" class="smpl">If-Match</a> = "If-Match:" OWS If-Match-v
1304<a href="#header.if-match" class="smpl">If-Match-v</a> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1305 entity-tag ] ) )
1306<a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> = "If-Modified-Since:" OWS If-Modified-Since-v
1307<a href="#header.if-modified-since" class="smpl">If-Modified-Since-v</a> = HTTP-date
1308<a href="#header.if-none-match" class="smpl">If-None-Match</a> = "If-None-Match:" OWS If-None-Match-v
1309<a href="#header.if-none-match" class="smpl">If-None-Match-v</a> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1310 entity-tag ] ) )
1311<a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> = "If-Unmodified-Since:" OWS
1312 If-Unmodified-Since-v
1313<a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since-v</a> = HTTP-date
1315<a href="#header.last-modified" class="smpl">Last-Modified</a> = "Last-Modified:" OWS Last-Modified-v
1316<a href="#header.last-modified" class="smpl">Last-Modified-v</a> = HTTP-date
1318<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
1320<a href="#entity.tags" class="smpl">entity-tag</a> = [ weak ] opaque-tag
1322<a href="#entity.tags" class="smpl">opaque-tag</a> = quoted-string
1324<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
1326<a href="#entity.tags" class="smpl">weak</a> = %x57.2F ; W/
1327</pre><div id="rfc.figure.u.20"></div>
1328         <p>ABNF diagnostics:</p><pre class="inline">; ETag defined but not used
1329; If-Match defined but not used
1330; If-Modified-Since defined but not used
1331; If-None-Match defined but not used
1332; If-Unmodified-Since defined but not used
1333; Last-Modified defined but not used
1335      <div id="change.log">
1336         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1337         <div>
1338            <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
1339            </h2>
1340            <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
1341            </p>
1342         </div>
1343         <div>
1344            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p4-conditional-00
1345            </h2>
1346            <p id="rfc.section.C.2.p.1">Closed issues: </p>
1347            <ul>
1348               <li>&lt;<a href=""></a>&gt;: "Normative and Informative references"
1349               </li>
1350            </ul>
1351            <p id="rfc.section.C.2.p.2">Other changes: </p>
1352            <ul>
1353               <li>Move definitions of 304 and 412 condition codes from Part2.</li>
1354            </ul>
1355         </div>
1356         <div>
1357            <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p4-conditional-01
1358            </h2>
1359            <p id="rfc.section.C.3.p.1">Ongoing work on ABNF conversion (&lt;<a href=""></a>&gt;):
1360            </p>
1361            <ul>
1362               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1363            </ul>
1364         </div>
1365         <div id="changes.since.02">
1366            <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p4-conditional-02</a></h2>
1367            <p id="rfc.section.C.4.p.1">Closed issues: </p>
1368            <ul>
1369               <li>&lt;<a href=""></a>&gt;: "Weak ETags on non-GET requests"
1370               </li>
1371            </ul>
1372            <p id="rfc.section.C.4.p.2">Ongoing work on IANA Message Header Registration (&lt;<a href=""></a>&gt;):
1373            </p>
1374            <ul>
1375               <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
1376            </ul>
1377         </div>
1378         <div id="changes.since.03">
1379            <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p4-conditional-03</a></h2>
1380            <p id="rfc.section.C.5.p.1">Closed issues: </p>
1381            <ul>
1382               <li>&lt;<a href=""></a>&gt;: "Examples for ETag matching"
1383               </li>
1384               <li>&lt;<a href=""></a>&gt;: "'entity value' undefined"
1385               </li>
1386               <li>&lt;<a href=""></a>&gt;: "bogus 2068 Date header reference"
1387               </li>
1388            </ul>
1389         </div>
1390         <div id="changes.since.04">
1391            <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p4-conditional-04</a></h2>
1392            <p id="rfc.section.C.6.p.1">Ongoing work on ABNF conversion (&lt;<a href=""></a>&gt;):
1393            </p>
1394            <ul>
1395               <li>Use "/" instead of "|" for alternatives.</li>
1396               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1397               <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
1398            </ul>
1399         </div>
1400         <div id="changes.since.05">
1401            <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p4-conditional-05</a></h2>
1402            <p id="rfc.section.C.7.p.1">Final work on ABNF conversion (&lt;<a href=""></a>&gt;):
1403            </p>
1404            <ul>
1405               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1406            </ul>
1407         </div>
1408         <div id="changes.since.06">
1409            <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p4-conditional-06</a></h2>
1410            <p id="rfc.section.C.8.p.1">Closed issues: </p>
1411            <ul>
1412               <li>&lt;<a href=""></a>&gt;: "case-sensitivity of etag weakness indicator"
1413               </li>
1414            </ul>
1415         </div>
1416         <div id="changes.since.07">
1417            <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p4-conditional-07</a></h2>
1418            <p id="rfc.section.C.9.p.1">Closed issues: </p>
1419            <ul>
1420               <li>&lt;<a href=""></a>&gt;: "Weak ETags on non-GET requests" (If-Match still was defined to require strong matching)
1421               </li>
1422               <li>&lt;<a href=""></a>&gt;: "move IANA registrations for optional status codes"
1423               </li>
1424            </ul>
1425         </div>
1426         <div id="changes.since.08">
1427            <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p4-conditional-08</a></h2>
1428            <p id="rfc.section.C.10.p.1">No significant changes.</p>
1429         </div>
1430         <div id="changes.since.09">
1431            <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p4-conditional-09</a></h2>
1432            <p id="rfc.section.C.11.p.1">No significant changes.</p>
1433         </div>
1434         <div id="changes.since.10">
1435            <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p4-conditional-10</a></h2>
1436            <p id="rfc.section.C.12.p.1">Closed issues: </p>
1437            <ul>
1438               <li>&lt;<a href=""></a>&gt;: "Clarify 'Requested Variant'"
1439               </li>
1440               <li>&lt;<a href=""></a>&gt;: "Clarify entity / representation / variant terminology"
1441               </li>
1442               <li>&lt;<a href=""></a>&gt;: "consider removing the 'changes from 2068' sections"
1443               </li>
1444            </ul>
1445         </div>
1446      </div>
1447      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1448      <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a>
1449      </p>
1450      <div class="print2col">
1451         <ul class="ind">
1452            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
1453                  <li>304 Not Modified (status code)&nbsp;&nbsp;<a href="#rfc.iref.3.1"><b>3.1</b></a>, <a href="#rfc.xref.status.304.1">7.1</a></li>
1454               </ul>
1455            </li>
1456            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1457                  <li>412 Precondition Failed (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>3.2</b></a>, <a href="#rfc.xref.status.412.1">7.1</a></li>
1458               </ul>
1459            </li>
1460            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
1461                  <li>ETag header&nbsp;&nbsp;<a href="#rfc.xref.header.etag.1">2</a>, <a href="#rfc.iref.e.1"><b>6.1</b></a>, <a href="#rfc.xref.header.etag.2">7.2</a></li>
1462               </ul>
1463            </li>
1464            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1465                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1466                     <ul>
1467                        <li><tt>entity-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
1468                        <li><tt>ETag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>6.1</b></a></li>
1469                        <li><tt>ETag-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>6.1</b></a></li>
1470                        <li><tt>If-Match</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>6.2</b></a></li>
1471                        <li><tt>If-Match-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>6.2</b></a></li>
1472                        <li><tt>If-Modified-Since</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>6.3</b></a></li>
1473                        <li><tt>If-Modified-Since-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>6.3</b></a></li>
1474                        <li><tt>If-None-Match</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>6.4</b></a></li>
1475                        <li><tt>If-None-Match-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.11"><b>6.4</b></a></li>
1476                        <li><tt>If-Unmodified-Since</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.12"><b>6.5</b></a></li>
1477                        <li><tt>If-Unmodified-Since-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.13"><b>6.5</b></a></li>
1478                        <li><tt>Last-Modified</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.14"><b>6.6</b></a></li>
1479                        <li><tt>Last-Modified-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.15"><b>6.6</b></a></li>
1480                        <li><tt>opaque-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2</b></a></li>
1481                        <li><tt>weak</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2</b></a></li>
1482                     </ul>
1483                  </li>
1484               </ul>
1485            </li>
1486            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1487                  <li>Headers&nbsp;&nbsp;
1488                     <ul>
1489                        <li>ETag&nbsp;&nbsp;<a href="#rfc.xref.header.etag.1">2</a>, <a href="#rfc.iref.h.1"><b>6.1</b></a>, <a href="#rfc.xref.header.etag.2">7.2</a></li>
1490                        <li>If-Match&nbsp;&nbsp;<a href="#rfc.xref.header.if-match.1">2</a>, <a href="#rfc.iref.h.2"><b>6.2</b></a>, <a href="#rfc.xref.header.if-match.2">7.2</a></li>
1491                        <li>If-Modified-Since&nbsp;&nbsp;<a href="#rfc.iref.h.3"><b>6.3</b></a>, <a href="#rfc.xref.header.if-modified-since.1">7.2</a></li>
1492                        <li>If-None-Match&nbsp;&nbsp;<a href="#rfc.xref.header.if-none-match.1">2</a>, <a href="#rfc.iref.h.4"><b>6.4</b></a>, <a href="#rfc.xref.header.if-none-match.2">7.2</a>, <a href="#rfc.xref.header.if-none-match.3">A</a></li>
1493                        <li>If-Unmodified-Since&nbsp;&nbsp;<a href="#rfc.iref.h.5"><b>6.5</b></a>, <a href="#rfc.xref.header.if-unmodified-since.1">7.2</a></li>
1494                        <li>Last-Modified&nbsp;&nbsp;<a href="#rfc.iref.h.6"><b>6.6</b></a>, <a href="#rfc.xref.header.last-modified.1">7.2</a></li>
1495                     </ul>
1496                  </li>
1497               </ul>
1498            </li>
1499            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1500                  <li>If-Match header&nbsp;&nbsp;<a href="#rfc.xref.header.if-match.1">2</a>, <a href="#rfc.iref.i.1"><b>6.2</b></a>, <a href="#rfc.xref.header.if-match.2">7.2</a></li>
1501                  <li>If-Modified-Since header&nbsp;&nbsp;<a href="#rfc.iref.i.2"><b>6.3</b></a>, <a href="#rfc.xref.header.if-modified-since.1">7.2</a></li>
1502                  <li>If-None-Match header&nbsp;&nbsp;<a href="#rfc.xref.header.if-none-match.1">2</a>, <a href="#rfc.iref.i.3"><b>6.4</b></a>, <a href="#rfc.xref.header.if-none-match.2">7.2</a>, <a href="#rfc.xref.header.if-none-match.3">A</a></li>
1503                  <li>If-Unmodified-Since header&nbsp;&nbsp;<a href="#rfc.iref.i.4"><b>6.5</b></a>, <a href="#rfc.xref.header.if-unmodified-since.1">7.2</a></li>
1504               </ul>
1505            </li>
1506            <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
1507                  <li>Last-Modified header&nbsp;&nbsp;<a href="#rfc.iref.l.1"><b>6.6</b></a>, <a href="#rfc.xref.header.last-modified.1">7.2</a></li>
1508               </ul>
1509            </li>
1510            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1511                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.2</a>, <a href="#rfc.xref.Part1.6">2.1</a>, <a href="#rfc.xref.Part1.7">3.1</a>, <a href="#rfc.xref.Part1.8">3.1</a>, <a href="#rfc.xref.Part1.9">8</a>, <a href="#Part1"><b>10.1</b></a><ul>
1512                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
1513                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a></li>
1514                        <li><em>Section 6.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2.2</a></li>
1515                        <li><em>Section 6.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2.1</a></li>
1516                        <li><em>Section 9.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">3.1</a></li>
1517                        <li><em>Section 9.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">3.1</a></li>
1518                     </ul>
1519                  </li>
1520                  <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">2.1</a>, <a href="#rfc.xref.Part3.2">2.1</a>, <a href="#Part3"><b>10.1</b></a><ul>
1521                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">2.1</a></li>
1522                        <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.2">2.1</a></li>
1523                     </ul>
1524                  </li>
1525                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2</a>, <a href="#rfc.xref.Part5.2">4</a>, <a href="#rfc.xref.Part5.3">4</a>, <a href="#rfc.xref.Part5.4">6.3</a>, <a href="#Part5"><b>10.1</b></a><ul>
1526                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">2</a></li>
1527                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.4">6.3</a></li>
1528                     </ul>
1529                  </li>
1530                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">6.2</a>, <a href="#rfc.xref.Part6.3">6.4</a>, <a href="#Part6"><b>10.1</b></a><ul>
1531                        <li><em>Section 3.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.2">6.2</a>, <a href="#rfc.xref.Part6.3">6.4</a></li>
1532                     </ul>
1533                  </li>
1534               </ul>
1535            </li>
1536            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1537                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>10.1</b></a></li>
1538                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>10.2</b></a>, <a href="#rfc.xref.RFC2616.2">C.1</a></li>
1539                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">7.2</a>, <a href="#RFC3864"><b>10.2</b></a></li>
1540                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b>10.1</b></a><ul>
1541                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
1542                     </ul>
1543                  </li>
1544               </ul>
1545            </li>
1546            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1547                  <li>Status Codes&nbsp;&nbsp;
1548                     <ul>
1549                        <li>304 Not Modified&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>3.1</b></a>, <a href="#rfc.xref.status.304.1">7.1</a></li>
1550                        <li>412 Precondition Failed&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>3.2</b></a>, <a href="#rfc.xref.status.412.1">7.1</a></li>
1551                     </ul>
1552                  </li>
1553               </ul>
1554            </li>
1555         </ul>
1556      </div>
1557      <div class="avoidbreak">
1558         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1559         <p><b>Roy T. Fielding</b>
1560            (editor)
1561            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1562         <p><b>Jim Gettys</b><br>Alcatel-Lucent Bell Labs<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1563         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>Email: <a href=""></a></p>
1564         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>Email: <a href=""></a></p>
1565         <p><b>Larry Masinter</b><br>Adobe Systems, Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1566         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>Email: <a href=""></a></p>
1567         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1568         <p><b>Yves Lafon</b>
1569            (editor)
1570            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1571         <p><b>Julian F. Reschke</b>
1572            (editor)
1573            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><br>Email: <a href=""></a><br>URI: <a href=""></a></p>
1574      </div>
1575   </body>
Note: See TracBrowser for help on using the repository browser.