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

Last change on this file was 2726, checked in by julian.reschke@…, 6 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: 114.4 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 4: Conditional Requests</title><script>
7var buttonsAdded = false;
8
9function initFeedback() {
10  var fb = document.createElement("div");
11  fb.className = "feedback noprint";
12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
14
15  var bodyl = document.getElementsByTagName("body");
16  bodyl.item(0).appendChild(fb);
17}
18
19function feedback() {
20  toggleButtonsToElementsByName("h1");
21  toggleButtonsToElementsByName("h2");
22  toggleButtonsToElementsByName("h3");
23  toggleButtonsToElementsByName("h4");
24
25  buttonsAdded = !buttonsAdded;
26}
27
28function toggleButtonsToElementsByName(name) {
29  var list = document.getElementsByTagName(name);
30  for (var i = 0; i < list.length; i++) {
31    toggleButton(list.item(i));
32  }
33}
34
35function toggleButton(node) {
36  if (! buttonsAdded) {
37
38    // docname
39    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
40
41    var id = node.getAttribute("id");
42    // better id available?
43    var titlelinks = node.getElementsByTagName("a");
44    for (var i = 0; i < titlelinks.length; i++) {
45      var tl = titlelinks.item(i);
46      if (tl.getAttribute("id")) {
47        id = tl.getAttribute("id");
48      }
49    }
50
51    // ref
52    var ref = window.location.toString();
53    var hash = ref.indexOf("#");
54    if (hash != -1) {
55      ref = ref.substring(0, hash);
56    }
57    if (id != "") {
58      ref += "#" + id;
59    }
60
61    // docname
62    var docname = "draft-ietf-httpbis-p4-conditional-19";
63
64    // section
65    var section = node.textContent;
66    section = section.replace("\u00a0", " ");
67
68    // build URI from template
69    var uri = template.replace("{docname}", encodeURIComponent(docname));
70    uri = uri.replace("{section}", encodeURIComponent(section));
71    uri = uri.replace("{ref}", encodeURIComponent(ref));
72
73    var button = document.createElement("a");
74    button.className = "fbbutton noprint";
75    button.setAttribute("href", uri);
76    button.appendChild(document.createTextNode("send feedback"));
77    node.appendChild(button);
78  }
79  else {
80    var buttons = node.getElementsByTagName("a");
81    for (var i = 0; i < buttons.length; i++) {
82      var b = buttons.item(i);
83      if (b.className == "fbbutton noprint") {
84        node.removeChild(b);
85      }
86    }
87  }
88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
89a {
90  text-decoration: none;
91}
92a.smpl {
93  color: black;
94}
95a:hover {
96  text-decoration: underline;
97}
98a:active {
99  text-decoration: underline;
100}
101address {
102  margin-top: 1em;
103  margin-left: 2em;
104  font-style: normal;
105}
106body {
107  color: black;
108  font-family: cambria, helvetica, arial, sans-serif;
109  font-size: 11pt;
110  margin-right: 2em;
111}
112cite {
113  font-style: normal;
114}
115div.note {
116  margin-left: 2em;
117}
118dl {
119  margin-left: 2em;
120}
121ul.empty {
122  list-style-type: none;
123}
124ul.empty li {
125  margin-top: .5em;
126}
127dl p {
128  margin-left: 0em;
129}
130dt {
131  margin-top: .5em;
132}
133h1 {
134  font-size: 130%;
135  line-height: 21pt;
136  page-break-after: avoid;
137}
138h1.np {
139  page-break-before: always;
140}
141h2 {
142  font-size: 120%;
143  line-height: 15pt;
144  page-break-after: avoid;
145}
146h3 {
147  font-size: 110%;
148  page-break-after: avoid;
149}
150h4, h5, h6 {
151  page-break-after: avoid;
152}
153h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
154  color: black;
155}
156img {
157  margin-left: 3em;
158}
159li {
160  margin-left: 2em;
161}
162ol {
163  margin-left: 2em;
164}
165ol.la {
166  list-style-type: lower-alpha;
167}
168ol.ua {
169  list-style-type: upper-alpha;
170}
171ol p {
172  margin-left: 0em;
173}
174p {
175  margin-left: 2em;
176}
177pre {
178  margin-left: 3em;
179  background-color: lightyellow;
180  padding: .25em;
181  page-break-inside: avoid;
182}
183pre.text2 {
184  border-style: dotted;
185  border-width: 1px;
186  background-color: #f0f0f0;
187  width: 69em;
188}
189pre.inline {
190  background-color: white;
191  padding: 0em;
192}
193pre.text {
194  border-style: dotted;
195  border-width: 1px;
196  background-color: #f8f8f8;
197  width: 69em;
198}
199pre.drawing {
200  border-style: solid;
201  border-width: 1px;
202  background-color: #f8f8f8;
203  padding: 2em;
204}
205table {
206  margin-left: 2em;
207}
208table.tt {
209  vertical-align: top;
210  border-color: gray;
211}
212table.tt th {
213  border-color: gray;
214}
215table.tt td {
216  border-color: gray;
217}
218table.all {
219  border-style: solid;
220  border-width: 2px;
221}
222table.full {
223  border-style: solid;
224  border-width: 2px;
225}
226table.tt td {
227  vertical-align: top;
228}
229table.all td {
230  border-style: solid;
231  border-width: 1px;
232}
233table.full td {
234  border-style: none solid;
235  border-width: 1px;
236}
237table.tt th {
238  vertical-align: top;
239}
240table.all th {
241  border-style: solid;
242  border-width: 1px;
243}
244table.full th {
245  border-style: solid;
246  border-width: 1px 1px 2px 1px;
247}
248table.headers th {
249  border-style: none none solid none;
250  border-width: 2px;
251}
252table.left {
253  margin-right: auto;
254}
255table.right {
256  margin-left: auto;
257}
258table.center {
259  margin-left: auto;
260  margin-right: auto;
261}
262caption {
263  caption-side: bottom;
264  font-weight: bold;
265  font-size: 10pt;
266  margin-top: .5em;
267}
268
269table.header {
270  border-spacing: 1px;
271  width: 95%;
272  font-size: 11pt;
273  color: white;
274}
275td.top {
276  vertical-align: top;
277}
278td.topnowrap {
279  vertical-align: top;
280  white-space: nowrap;
281}
282table.header td {
283  background-color: gray;
284  width: 50%;
285}
286table.header a {
287  color: white;
288}
289td.reference {
290  vertical-align: top;
291  white-space: nowrap;
292  padding-right: 1em;
293}
294thead {
295  display:table-header-group;
296}
297ul.toc, ul.toc ul {
298  list-style: none;
299  margin-left: 1.5em;
300  padding-left: 0em;
301}
302ul.toc li {
303  line-height: 150%;
304  font-weight: bold;
305  margin-left: 0em;
306}
307ul.toc li li {
308  line-height: normal;
309  font-weight: normal;
310  font-size: 10pt;
311  margin-left: 0em;
312}
313li.excluded {
314  font-size: 0pt;
315}
316ul p {
317  margin-left: 0em;
318}
319.title, .filename, h1, h2, h3, h4 {
320  font-family: candara, helvetica, arial, sans-serif;
321}
322samp, tt, code, pre {
323  font: consolas, monospace;
324}
325ul.ind, ul.ind ul {
326  list-style: none;
327  margin-left: 1.5em;
328  padding-left: 0em;
329  page-break-before: avoid;
330}
331ul.ind li {
332  font-weight: bold;
333  line-height: 200%;
334  margin-left: 0em;
335}
336ul.ind li li {
337  font-weight: normal;
338  line-height: 150%;
339  margin-left: 0em;
340}
341.avoidbreak {
342  page-break-inside: avoid;
343}
344.bcp14 {
345  font-style: normal;
346  text-transform: lowercase;
347  font-variant: small-caps;
348}
349.comment {
350  background-color: yellow;
351}
352.center {
353  text-align: center;
354}
355.error {
356  color: red;
357  font-style: italic;
358  font-weight: bold;
359}
360.figure {
361  font-weight: bold;
362  text-align: center;
363  font-size: 10pt;
364}
365.filename {
366  color: #333333;
367  font-size: 75%;
368  font-weight: bold;
369  line-height: 21pt;
370  text-align: center;
371}
372.fn {
373  font-weight: bold;
374}
375.left {
376  text-align: left;
377}
378.right {
379  text-align: right;
380}
381.title {
382  color: green;
383  font-size: 150%;
384  line-height: 18pt;
385  font-weight: bold;
386  text-align: center;
387  margin-top: 36pt;
388}
389.warning {
390  font-size: 130%;
391  background-color: yellow;
392}
393.feedback {
394  position: fixed;
395  bottom: 1%;
396  right: 1%;
397  padding: 3px 5px;
398  color: white;
399  border-radius: 5px;
400  background: #a00000;
401  border: 1px solid silver;
402}
403.fbbutton {
404  margin-left: 1em;
405  color: #303030;
406  font-size: small;
407  font-weight: normal;
408  background: #d0d000;
409  padding: 1px 4px;
410  border: 1px solid silver;
411  border-radius: 5px;
412}
413
414@media print {
415  .noprint {
416    display: none;
417  }
418
419  a {
420    color: black;
421    text-decoration: none;
422  }
423
424  table.header {
425    width: 90%;
426  }
427
428  td.header {
429    width: 50%;
430    color: black;
431    background-color: white;
432    vertical-align: top;
433    font-size: 110%;
434  }
435
436  ul.toc a:nth-child(2)::after {
437    content: leader('.') target-counter(attr(href), page);
438  }
439
440  ul.ind li li a {
441    content: target-counter(attr(href), page);
442  }
443
444  .print2col {
445    column-count: 2;
446    -moz-column-count: 2;
447    column-fill: auto;
448  }
449}
450
451@page {
452  @top-left {
453       content: "Internet-Draft";
454  }
455  @top-right {
456       content: "March 2012";
457  }
458  @top-center {
459       content: "HTTP/1.1, Part 4";
460  }
461  @bottom-left {
462       content: "Fielding, et al.";
463  }
464  @bottom-center {
465       content: "Expires September 13, 2012";
466  }
467  @bottom-right {
468       content: "[Page " counter(page) "]";
469  }
470}
471
472@page:first {
473    @top-left {
474      content: normal;
475    }
476    @top-right {
477      content: normal;
478    }
479    @top-center {
480      content: normal;
481    }
482}
483</style><link rel="Contents" href="#rfc.toc">
484      <link rel="Author" href="#rfc.authors">
485      <link rel="Copyright" href="#rfc.copyrightnotice">
486      <link rel="Index" href="#rfc.index">
487      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
488      <link rel="Chapter" title="2 Validators" href="#rfc.section.2">
489      <link rel="Chapter" title="3 Precondition Header Fields" href="#rfc.section.3">
490      <link rel="Chapter" title="4 Status Code Definitions" href="#rfc.section.4">
491      <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5">
492      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
493      <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
494      <link rel="Chapter" href="#rfc.section.8" title="8 References">
495      <link rel="Appendix" title="A Changes from RFC 2616" href="#rfc.section.A">
496      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
497      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
498      <link href="p3-payload.html" rel="prev">
499      <link href="p5-range.html" rel="next">
500      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
501      <link rel="schema.dct" href="http://purl.org/dc/terms/">
502      <meta name="dct.creator" content="Fielding, R.">
503      <meta name="dct.creator" content="Lafon, Y.">
504      <meta name="dct.creator" content="Reschke, J. F.">
505      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-19">
506      <meta name="dct.issued" scheme="ISO8601" content="2012-03-12">
507      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
508      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 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.">
509      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 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.">
510   </head>
511   <body onload="initFeedback();">
512      <table class="header">
513         <tbody>
514            <tr>
515               <td class="left">HTTPbis Working Group</td>
516               <td class="right">R. Fielding, Editor</td>
517            </tr>
518            <tr>
519               <td class="left">Internet-Draft</td>
520               <td class="right">Adobe</td>
521            </tr>
522            <tr>
523               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
524               </td>
525               <td class="right">Y. Lafon, Editor</td>
526            </tr>
527            <tr>
528               <td class="left">Intended status: Standards Track</td>
529               <td class="right">W3C</td>
530            </tr>
531            <tr>
532               <td class="left">Expires: September 13, 2012</td>
533               <td class="right">J. Reschke, Editor</td>
534            </tr>
535            <tr>
536               <td class="left"></td>
537               <td class="right">greenbytes</td>
538            </tr>
539            <tr>
540               <td class="left"></td>
541               <td class="right">March 12, 2012</td>
542            </tr>
543         </tbody>
544      </table>
545      <p class="title">HTTP/1.1, part 4: Conditional Requests<br><span class="filename">draft-ietf-httpbis-p4-conditional-19</span></p>
546      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
547      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information
548         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the
549         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
550      </p>
551      <p>Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those
552         requests.
553      </p>
554      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
555      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
556         at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
557      </p>
558      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
559      </p>
560      <p>The changes in this draft are summarized in <a href="#changes.since.18" title="Since draft-ietf-httpbis-p4-conditional-18">Appendix&nbsp;C.20</a>.
561      </p>
562      <div id="rfc.status">
563         <h1><a href="#rfc.status">Status of This Memo</a></h1>
564         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
565         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
566            working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
567         </p>
568         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
569            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
570            in progress”.
571         </p>
572         <p>This Internet-Draft will expire on September 13, 2012.</p>
573      </div>
574      <div id="rfc.copyrightnotice">
575         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
576         <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
577         <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
578            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
579            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
580            BSD License.
581         </p>
582         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
583            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
584            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
585            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
586            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
587            it into languages other than English.
588         </p>
589      </div>
590      <hr class="noprint">
591      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
592      <ul class="toc">
593         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
594               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
595               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a></li>
596            </ul>
597         </li>
598         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#validators">Validators</a><ul>
599               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#weak.and.strong.validators">Weak versus Strong</a></li>
600               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.last-modified">Last-Modified</a><ul>
601                     <li><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#lastmod.generation">Generation</a></li>
602                     <li><a href="#rfc.section.2.2.2">2.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#lastmod.comparison">Comparison</a></li>
603                  </ul>
604               </li>
605               <li><a href="#rfc.section.2.3">2.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.etag">ETag</a><ul>
606                     <li><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;&nbsp;&nbsp;<a href="#entity.tag.generation">Generation</a></li>
607                     <li><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;&nbsp;&nbsp;<a href="#entity.tag.comparison">Comparison</a></li>
608                     <li><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;&nbsp;&nbsp;<a href="#example.entity.tag.vs.conneg">Example: Entity-tags varying on Content-Negotiated Resources</a></li>
609                  </ul>
610               </li>
611               <li><a href="#rfc.section.2.4">2.4</a>&nbsp;&nbsp;&nbsp;<a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates">Rules for When to Use Entity-tags and Last-Modified Dates</a></li>
612            </ul>
613         </li>
614         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Precondition Header Fields</a><ul>
615               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-match">If-Match</a></li>
616               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-none-match">If-None-Match</a></li>
617               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></li>
618               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></li>
619               <li><a href="#rfc.section.3.5">3.5</a>&nbsp;&nbsp;&nbsp;<a href="#header.if-range">If-Range</a></li>
620            </ul>
621         </li>
622         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
623               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
624               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
625            </ul>
626         </li>
627         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
628               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
629               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
630            </ul>
631         </li>
632         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
633         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
634         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
635               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
636               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
637            </ul>
638         </li>
639         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
640         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
641         <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>
642               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
643               <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>
644               <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>
645               <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>
646               <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>
647               <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>
648               <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>
649               <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>
650               <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>
651               <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>
652               <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>
653               <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>
654               <li><a href="#rfc.section.C.13">C.13</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p4-conditional-11</a></li>
655               <li><a href="#rfc.section.C.14">C.14</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p4-conditional-12</a></li>
656               <li><a href="#rfc.section.C.15">C.15</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p4-conditional-13</a></li>
657               <li><a href="#rfc.section.C.16">C.16</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p4-conditional-14</a></li>
658               <li><a href="#rfc.section.C.17">C.17</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p4-conditional-15</a></li>
659               <li><a href="#rfc.section.C.18">C.18</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p4-conditional-16</a></li>
660               <li><a href="#rfc.section.C.19">C.19</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p4-conditional-17</a></li>
661               <li><a href="#rfc.section.C.20">C.20</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p4-conditional-18</a></li>
662            </ul>
663         </li>
664         <li><a href="#rfc.index">Index</a></li>
665         <li><a href="#rfc.authors">Authors' Addresses</a></li>
666      </ul>
667      <div id="introduction">
668         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
669         <p id="rfc.section.1.p.1">This document defines the HTTP/1.1 conditional request mechanisms, including both metadata for indicating/observing changes
670            in resource representations and request header fields that specify preconditions on that metadata be checked before performing
671            the request method. Conditional GET requests are the most efficient mechanism for HTTP cache updates <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>. Conditionals can also be applied to state-changing methods, such as PUT and DELETE, to prevent the "lost update" problem:
672            one client accidentally overwriting the work of another client that has been acting in parallel.
673         </p>
674         <p id="rfc.section.1.p.2">Conditional request preconditions are based on the state of the target resource as a whole (its current value set) or the
675            state as observed in a previously obtained representation (one value in that set). A resource might have multiple current
676            representations, each with its own observable state. The conditional request mechanisms assume that the mapping of requests
677            to corresponding representations will be consistent over time if the server intends to take advantage of conditionals. Regardless,
678            if the mapping is inconsistent and the server is unable to select the appropriate representation, then no harm will result
679            when the precondition evaluates to false.
680         </p>
681         <p id="rfc.section.1.p.3"><span id="rfc.iref.s.1"></span> We use the term "<dfn>selected representation</dfn>" to refer to the current representation of the target resource that would have been selected in a successful response if
682            the same request had used the method GET and had excluded all of the conditional request header fields. The conditional request
683            preconditions are evaluated by comparing the values provided in the request header fields to the current metadata for the
684            selected representation.
685         </p>
686         <div id="intro.conformance.and.error.handling">
687            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
688            <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"
689               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>.
690            </p>
691            <p id="rfc.section.1.1.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
692               Servers, User-Agents, Origin Servers, Intermediaries, Proxies and Gateways. See <a href="p1-messaging.html#architecture" title="Architecture">Section 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> for definitions of these terms.
693            </p>
694            <p id="rfc.section.1.1.p.3">An implementation is considered conformant if it complies with all of the requirements associated with its role(s). Note that
695               SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
696            </p>
697            <p id="rfc.section.1.1.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section&nbsp;1.2</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid.
698            </p>
699            <p id="rfc.section.1.1.p.5">Unless noted otherwise, Recipients <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
700               mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
701               different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
702               Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of
703               error recovery could lead to dangerous consequences.
704            </p>
705         </div>
706         <div id="notation">
707            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
708            <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.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>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
709            </p>
710            <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="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
711               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
712               character).
713            </p>
714            <p id="rfc.section.1.2.p.3">The ABNF rules below are 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> and <a href="#Part2" id="rfc.xref.Part2.1"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>:
715            </p>
716            <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#notation" 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#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
717  <a href="#notation" class="smpl">obs-text</a>      = &lt;obs-text, 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="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
718  <a href="#notation" class="smpl">HTTP-date</a>     = &lt;HTTP-date, defined in <a href="#Part2" id="rfc.xref.Part2.2"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>, <a href="p2-semantics.html#http.date" title="Date/Time Formats">Section 8</a>&gt;
719</pre></div>
720      </div>
721      <div id="validators">
722         <div id="rfc.iref.m.1"></div>
723         <div id="rfc.iref.v.1"></div>
724         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#validators">Validators</a></h1>
725         <p id="rfc.section.2.p.1">This specification defines two forms of metadata that are commonly used to observe resource state and test for preconditions:
726            modification dates and opaque entity tags. Additional metadata that reflects resource state has been defined by various extensions
727            of HTTP, such as WebDAV <a href="#RFC4918" id="rfc.xref.RFC4918.1"><cite title="HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)">[RFC4918]</cite></a>, that are beyond the scope of this specification. A resource metadata value is referred to as a "<dfn>validator</dfn>" when it is used within a precondition.
728         </p>
729         <div id="weak.and.strong.validators">
730            <div id="rfc.iref.v.2"></div>
731            <div id="rfc.iref.v.3"></div>
732            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#weak.and.strong.validators">Weak versus Strong</a></h2>
733            <p id="rfc.section.2.1.p.1">Validators come in two flavors: strong or weak. Weak validators are easy to generate but are far less useful for comparisons.
734               Strong validators are ideal for comparisons but can be very difficult (and occasionally impossible) to generate efficiently.
735               Rather than impose that all forms of resource adhere to the same strength of validator, HTTP exposes the type of validator
736               in use and imposes restrictions on when weak validators can be used as preconditions.
737            </p>
738            <p id="rfc.section.2.1.p.2">A "strong validator" is a representation metadata value that <em class="bcp14">MUST</em> be changed to a new, previously unused or guaranteed unique, value whenever a change occurs to the representation data such
739               that a change would be observable in the payload body of a 200 response to GET. A strong validator <em class="bcp14">MAY</em> be changed for other reasons, such as when a semantically significant part of the representation metadata is changed (e.g.,
740               Content-Type), but it is in the best interests of the origin server to only change the value when it is necessary to invalidate
741               the stored responses held by remote caches and authoring tools. A strong validator <em class="bcp14">MUST</em> be unique across all representations of a given resource, such that no two representations of that resource share the same
742               validator unless their payload body would be identical.
743            </p>
744            <p id="rfc.section.2.1.p.3">Cache entries might persist for arbitrarily long periods, regardless of expiration times. Thus, a cache might attempt to validate
745               an entry using a validator that it obtained in the distant past. A strong validator <em class="bcp14">MUST</em> be unique across all versions of all representations associated with a particular resource over time. However, there is no
746               implication of uniqueness across representations of different resources (i.e., the same strong validator might be in use for
747               representations of multiple resources at the same time and does not imply that those representations are equivalent).
748            </p>
749            <p id="rfc.section.2.1.p.4">There are a variety of strong validators used in practice. The best are based on strict revision control, wherein each change
750               to a representation always results in a unique node name and revision identifier being assigned before the representation
751               is made accessible to GET. A cryptographic hash function applied to the representation data is also sufficient if the data
752               is available prior to the response header fields being sent and the digest does not need to be recalculated every time a validation
753               request is received. However, if a resource has distinct representations that differ only in their metadata, such as might
754               occur with content negotiation over media types that happen to share the same data format, then a server <em class="bcp14">SHOULD</em> incorporate additional information in the validator to distinguish those representations and avoid confusing cache behavior.
755            </p>
756            <p id="rfc.section.2.1.p.5">In contrast, a "weak validator" is a representation metadata value that might not be changed for every change to the representation
757               data. This weakness might be due to limitations in how the value is calculated, such as clock resolution or an inability to
758               ensure uniqueness for all possible representations of the resource, or due to a desire by the resource owner to group representations
759               by some self-determined set of equivalency rather than unique sequences of data. A weak entity-tag <em class="bcp14">SHOULD</em> change whenever the origin server considers prior representations to be unacceptable as a substitute for the current representation.
760               In other words, a weak entity-tag <em class="bcp14">SHOULD</em> change whenever the origin server wants caches to invalidate old responses.
761            </p>
762            <p id="rfc.section.2.1.p.6">For example, the representation of a weather report that changes in content every second, based on dynamic measurements, might
763               be grouped into sets of equivalent representations (from the origin server's perspective) with the same weak validator in
764               order to allow cached representations to be valid for a reasonable period of time (perhaps adjusted dynamically based on server
765               load or weather quality). Likewise, a representation's modification time, if defined with only one-second resolution, might
766               be a weak validator if it is possible for the representation to be modified twice during a single second and retrieved between
767               those modifications.
768            </p>
769            <p id="rfc.section.2.1.p.7">A "use" of a validator occurs when either a client generates a request and includes the validator in a precondition or when
770               a server compares two validators. Weak validators are only usable in contexts that do not depend on exact equality of a representation's
771               payload body. Strong validators are usable and preferred for all conditional requests, including cache validation, partial
772               content ranges, and "lost update" avoidance.
773            </p>
774         </div>
775         <div id="header.last-modified">
776            <div id="rfc.iref.l.1"></div>
777            <div id="rfc.iref.h.1"></div>
778            <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#header.last-modified">Last-Modified</a></h2>
779            <p id="rfc.section.2.2.p.1">The "Last-Modified" header field indicates the date and time at which the origin server believes the selected representation
780               was last modified.
781            </p>
782            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  <a href="#header.last-modified" class="smpl">Last-Modified</a> = <a href="#notation" class="smpl">HTTP-date</a>
783</pre><p id="rfc.section.2.2.p.3">An example of its use is</p>
784            <div id="rfc.figure.u.3"></div><pre class="text">  Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
785</pre><div id="lastmod.generation">
786               <h3 id="rfc.section.2.2.1"><a href="#rfc.section.2.2.1">2.2.1</a>&nbsp;<a href="#lastmod.generation">Generation</a></h3>
787               <p id="rfc.section.2.2.1.p.1">Origin servers <em class="bcp14">SHOULD</em> send Last-Modified for any selected representation for which a last modification date can be reasonably and consistently determined,
788                  since its use in conditional requests and evaluating cache freshness (<a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) results in a substantial reduction of HTTP traffic on the Internet and can be a significant factor in improving service
789                  scalability and reliability.
790               </p>
791               <p id="rfc.section.2.2.1.p.2">A representation is typically the sum of many parts behind the resource interface. The last-modified time would usually be
792                  the most recent time that any of those parts were changed. How that value is determined for any given resource is an implementation
793                  detail beyond the scope of this specification. What matters to HTTP is how recipients of the Last-Modified header field can
794                  use its value to make conditional requests and test the validity of locally cached responses.
795               </p>
796               <p id="rfc.section.2.2.1.p.3">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 field-value
797                  for its response. This allows a recipient to make an accurate assessment of the representation's modification time, especially
798                  if the representation changes near the time that the response is generated.
799               </p>
800               <p id="rfc.section.2.2.1.p.4">An origin server with a clock <em class="bcp14">MUST NOT</em> send a Last-Modified date that is later than the server's time of message origination (Date). If the last modification time
801                  is derived from implementation-specific metadata that evaluates to some time in the future, according to the origin server's
802                  clock, then the origin server <em class="bcp14">MUST</em> replace that value with the message origination date. This prevents a future modification date from having an adverse impact
803                  on cache validation.
804               </p>
805               <p id="rfc.section.2.2.1.p.5">An origin server without a clock <em class="bcp14">MUST NOT</em> assign Last-Modified values to a response unless these values were associated with the resource by some other system or user
806                  with a reliable clock.
807               </p>
808            </div>
809            <div id="lastmod.comparison">
810               <h3 id="rfc.section.2.2.2"><a href="#rfc.section.2.2.2">2.2.2</a>&nbsp;<a href="#lastmod.comparison">Comparison</a></h3>
811               <p id="rfc.section.2.2.2.p.1">A Last-Modified time, when used as a validator in a request, is implicitly weak unless it is possible to deduce that it is
812                  strong, using the following rules:
813               </p>
814               <ul>
815                  <li>The validator is being compared by an origin server to the actual current validator for the representation and,</li>
816                  <li>That origin server reliably knows that the associated representation did not change twice during the second covered by the
817                     presented validator.
818                  </li>
819               </ul>
820               <p id="rfc.section.2.2.2.p.2">or </p>
821               <ul>
822                  <li>The validator is about to be used by a client in an If-Modified-Since, If-Unmodified-Since header field, because the client
823                     has a cache entry, or If-Range for the associated representation, and
824                  </li>
825                  <li>That cache entry includes a Date value, which gives the time when the origin server sent the original response, and</li>
826                  <li>The presented Last-Modified time is at least 60 seconds before the Date value.</li>
827               </ul>
828               <p id="rfc.section.2.2.2.p.3">or </p>
829               <ul>
830                  <li>The validator is being compared by an intermediate cache to the validator stored in its cache entry for the representation,
831                     and
832                  </li>
833                  <li>That cache entry includes a Date value, which gives the time when the origin server sent the original response, and</li>
834                  <li>The presented Last-Modified time is at least 60 seconds before the Date value.</li>
835               </ul>
836               <p id="rfc.section.2.2.2.p.4">This method relies on the fact that if two different responses were sent by the origin server during the same second, but
837                  both had the same Last-Modified time, then at least one of those responses would have a Date value equal to its Last-Modified
838                  time. The arbitrary 60-second limit guards against the possibility that the Date and Last-Modified values are generated from
839                  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.
840               </p>
841            </div>
842         </div>
843         <div id="header.etag">
844            <div id="rfc.iref.e.1"></div>
845            <div id="rfc.iref.h.2"></div>
846            <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a href="#header.etag">ETag</a></h2>
847            <p id="rfc.section.2.3.p.1">The ETag header field provides the current entity-tag for the selected representation. An entity-tag is an opaque validator
848               for differentiating between multiple representations of the same resource, regardless of whether those multiple representations
849               are due to resource state changes over time, content negotiation resulting in multiple representations being valid at the
850               same time, or both. An entity-tag consists of an opaque quoted string, possibly prefixed by a weakness indicator.
851            </p>
852            <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.etag" class="smpl">ETag</a>       = <a href="#header.etag" class="smpl">entity-tag</a>
853
854  <a href="#header.etag" class="smpl">entity-tag</a> = [ <a href="#header.etag" class="smpl">weak</a> ] <a href="#header.etag" class="smpl">opaque-tag</a>
855  <a href="#header.etag" class="smpl">weak</a>       = %x57.2F ; "W/", case-sensitive
856  <a href="#header.etag" class="smpl">opaque-tag</a> = <a href="#notation" class="smpl">DQUOTE</a> *<a href="#header.etag" class="smpl">etagc</a> <a href="#notation" class="smpl">DQUOTE</a>
857  <a href="#header.etag" class="smpl">etagc</a>      = %x21 / %x23-7E / <a href="#notation" class="smpl">obs-text</a>
858             ; <a href="#notation" class="smpl">VCHAR</a> except double quotes, plus obs-text
859</pre><div class="note" id="rfc.section.2.3.p.3">
860               <p><b>Note:</b> Previously, opaque-tag was defined to be a quoted-string (<a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>, <a href="https://tools.ietf.org/html/rfc2616#section-3.11">Section 3.11</a>), thus some recipients might perform backslash unescaping. Servers therefore ought to avoid backslash characters in entity
861                  tags.
862               </p>
863            </div>
864            <p id="rfc.section.2.3.p.4">An entity-tag can be more reliable for validation than a modification date in situations where it is inconvenient to store
865               modification dates, where the one-second resolution of HTTP date values is not sufficient, or where modification dates are
866               not consistently maintained.
867            </p>
868            <div id="rfc.figure.u.5"></div>
869            <p>Examples:</p><pre class="text">  ETag: "xyzzy"
870  ETag: W/"xyzzy"
871  ETag: ""
872</pre><p id="rfc.section.2.3.p.6">An entity-tag can be either a weak or strong validator, with strong being the default. If an origin server provides an entity-tag
873               for a representation and the generation of that entity-tag does not satisfy the requirements for a strong validator (<a href="#weak.and.strong.validators" title="Weak versus Strong">Section&nbsp;2.1</a>), then that entity-tag <em class="bcp14">MUST</em> be marked as weak by prefixing its opaque value with "W/" (case-sensitive).
874            </p>
875            <div id="entity.tag.generation">
876               <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a href="#entity.tag.generation">Generation</a></h3>
877               <p id="rfc.section.2.3.1.p.1">The principle behind entity-tags is that only the service author knows the implementation of a resource well enough to select
878                  the most accurate and efficient validation mechanism for that resource, and that any such mechanism can be mapped to a simple
879                  sequence of octets for easy comparison. Since the value is opaque, there is no need for the client to be aware of how each
880                  entity-tag is constructed.
881               </p>
882               <p id="rfc.section.2.3.1.p.2">For example, a resource that has implementation-specific versioning applied to all changes might use an internal revision
883                  number, perhaps combined with a variance identifier for content negotiation, to accurately differentiate between representations.
884                  Other implementations might use a stored hash of representation content, a combination of various filesystem attributes, or
885                  a modification timestamp that has sub-second resolution.
886               </p>
887               <p id="rfc.section.2.3.1.p.3">Origin servers <em class="bcp14">SHOULD</em> send ETag for any selected representation for which detection of changes can be reasonably and consistently determined, since
888                  the entity-tag's use in conditional requests and evaluating cache freshness (<a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) can result in a substantial reduction of HTTP network traffic and can be a significant factor in improving service scalability
889                  and reliability.
890               </p>
891            </div>
892            <div id="entity.tag.comparison">
893               <h3 id="rfc.section.2.3.2"><a href="#rfc.section.2.3.2">2.3.2</a>&nbsp;<a href="#entity.tag.comparison">Comparison</a></h3>
894               <p id="rfc.section.2.3.2.p.1">There are two entity-tag comparison functions, depending on whether the comparison context allows the use of weak validators
895                  or not:
896               </p>
897               <ul>
898                  <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.
899                  </li>
900                  <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.
901                  </li>
902               </ul>
903               <p id="rfc.section.2.3.2.p.2">The example below shows the results for a set of entity-tag pairs, and both the weak and strong comparison function results:</p>
904               <div id="rfc.table.u.1">
905                  <table class="tt full left" cellpadding="3" cellspacing="0">
906                     <thead>
907                        <tr>
908                           <th>ETag 1</th>
909                           <th>ETag 2</th>
910                           <th>Strong Comparison</th>
911                           <th>Weak Comparison</th>
912                        </tr>
913                     </thead>
914                     <tbody>
915                        <tr>
916                           <td class="left">W/"1"</td>
917                           <td class="left">W/"1"</td>
918                           <td class="left">no match</td>
919                           <td class="left">match</td>
920                        </tr>
921                        <tr>
922                           <td class="left">W/"1"</td>
923                           <td class="left">W/"2"</td>
924                           <td class="left">no match</td>
925                           <td class="left">no match</td>
926                        </tr>
927                        <tr>
928                           <td class="left">W/"1"</td>
929                           <td class="left">"1"</td>
930                           <td class="left">no match</td>
931                           <td class="left">match</td>
932                        </tr>
933                        <tr>
934                           <td class="left">"1"</td>
935                           <td class="left">"1"</td>
936                           <td class="left">match</td>
937                           <td class="left">match</td>
938                        </tr>
939                     </tbody>
940                  </table>
941               </div>
942            </div>
943            <div id="example.entity.tag.vs.conneg">
944               <h3 id="rfc.section.2.3.3"><a href="#rfc.section.2.3.3">2.3.3</a>&nbsp;<a href="#example.entity.tag.vs.conneg">Example: Entity-tags varying on Content-Negotiated Resources</a></h3>
945               <p id="rfc.section.2.3.3.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>):
946               </p>
947               <div id="rfc.figure.u.6"></div>
948               <p>&gt;&gt; Request:</p><pre class="text2">GET /index HTTP/1.1
949Host: www.example.com
950Accept-Encoding: gzip
951
952</pre><p id="rfc.section.2.3.3.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>
953               <div id="rfc.figure.u.7"></div>
954               <p>&gt;&gt; Response:</p><pre class="text">HTTP/1.1 200 OK
955Date: Thu, 26 Mar 2010 00:05:00 GMT
956ETag: "123-a"
957Content-Length: 70
958Vary: Accept-Encoding
959Content-Type: text/plain
960
961<span id="exbody">Hello World!
962Hello World!
963Hello World!
964Hello World!
965Hello World!
966</span></pre><p id="rfc.section.2.3.3.p.5">An alternative representation that does use gzip content coding would be:</p>
967               <div id="rfc.figure.u.8"></div>
968               <p>&gt;&gt; Response:</p><pre class="text">HTTP/1.1 200 OK
969Date: Thu, 26 Mar 2010 00:05:00 GMT
970ETag: "123-b"
971Content-Length: 43
972Vary: Accept-Encoding
973Content-Type: text/plain
974Content-Encoding: gzip
975
976<em>...binary data...</em></pre><div class="note" id="rfc.section.2.3.3.p.7">
977                  <p><b>Note:</b> Content codings are a property of the representation, so therefore an entity-tag of an encoded representation must be distinct
978                     from an unencoded representation to prevent conflicts during cache updates and range requests. In contrast, transfer codings
979                     (<a href="p1-messaging.html#transfer.codings" title="Transfer Codings">Section 4</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.
980                  </p>
981               </div>
982            </div>
983         </div>
984         <div id="rules.for.when.to.use.entity.tags.and.last-modified.dates">
985            <h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a>&nbsp;<a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates">Rules for When to Use Entity-tags and Last-Modified Dates</a></h2>
986            <p id="rfc.section.2.4.p.1">We adopt a set of rules and recommendations for origin servers, clients, and caches regarding when various validator types
987               ought to be used, and for what purposes.
988            </p>
989            <p id="rfc.section.2.4.p.2">HTTP/1.1 origin servers: </p>
990            <ul>
991               <li><em class="bcp14">SHOULD</em> send an entity-tag validator unless it is not feasible to generate one.
992               </li>
993               <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,
994                  or if it is unfeasible to send a strong entity-tag.
995               </li>
996               <li><em class="bcp14">SHOULD</em> send a Last-Modified value if it is feasible to send one.
997               </li>
998            </ul>
999            <p id="rfc.section.2.4.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
1000               value.
1001            </p>
1002            <p id="rfc.section.2.4.p.4">HTTP/1.1 clients: </p>
1003            <ul>
1004               <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
1005                  by the origin server.
1006               </li>
1007               <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
1008                  has been provided by the origin server.
1009               </li>
1010               <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
1011                  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.
1012               </li>
1013               <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
1014                  origin server. This allows both HTTP/1.0 and HTTP/1.1 caches to respond appropriately.
1015               </li>
1016            </ul>
1017            <p id="rfc.section.2.4.p.5">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
1018               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
1019               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
1020               in the request.
1021            </p>
1022            <p id="rfc.section.2.4.p.6">An HTTP/1.1 caching proxy, upon receiving a conditional request that includes both a Last-Modified date and one or more entity-tags
1023               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
1024               fields in the request.
1025            </p>
1026            <ul class="empty">
1027               <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
1028                  as is available in their responses and requests. HTTP/1.1 systems receiving this information will make the most conservative
1029                  assumptions about the validators they receive.
1030               </li>
1031               <li>HTTP/1.0 clients and caches might ignore entity-tags. Generally, last-modified values received or used by these systems will
1032                  support transparent and efficient caching, and so HTTP/1.1 origin servers should provide Last-Modified values. In those rare
1033                  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
1034                  HTTP/1.1 origin servers should not provide one.
1035               </li>
1036            </ul>
1037         </div>
1038      </div>
1039      <div id="header.field.definitions">
1040         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#header.field.definitions">Precondition Header Fields</a></h1>
1041         <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields for applying preconditions on requests.</p>
1042         <div id="header.if-match">
1043            <div id="rfc.iref.i.1"></div>
1044            <div id="rfc.iref.h.3"></div>
1045            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.if-match">If-Match</a></h2>
1046            <p id="rfc.section.3.1.p.1">The "If-Match" header field <em class="bcp14">MAY</em> be used to make a request method conditional on the current existence or value of an entity-tag for one or more representations
1047               of the target resource. If-Match is generally useful for resource update requests, such as PUT requests, as a means for protecting
1048               against accidental overwrites when multiple clients are acting in parallel on the same resource (i.e., the "lost update" problem).
1049               An If-Match field-value of "*" places the precondition on the existence of any current representation for the target resource.
1050            </p>
1051            <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.if-match" class="smpl">If-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
1052</pre><p id="rfc.section.3.1.p.3">If any of the entity-tags listed in the If-Match field value match (as per <a href="#entity.tag.comparison" title="Comparison">Section&nbsp;2.3.2</a>) the entity-tag of the selected representation for the target resource, or if "*" is given and any current representation
1053               exists for the target resource, then the server <em class="bcp14">MAY</em> perform the request method as if the If-Match header field was not present.
1054            </p>
1055            <p id="rfc.section.3.1.p.4">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. Instead, the server <em class="bcp14">MUST</em> respond with the 412 (Precondition Failed) status code.
1056            </p>
1057            <p id="rfc.section.3.1.p.5">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status code, then the
1058               If-Match header field <em class="bcp14">MUST</em> be ignored.
1059            </p>
1060            <p id="rfc.section.3.1.p.6">Examples:</p>
1061            <div id="rfc.figure.u.10"></div><pre class="text">  If-Match: "xyzzy"
1062  If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
1063  If-Match: *
1064</pre><p id="rfc.section.3.1.p.8">The result of a request having both an If-Match header field and either an If-None-Match or an If-Modified-Since header field
1065               is undefined by this specification.
1066            </p>
1067         </div>
1068         <div id="header.if-none-match">
1069            <div id="rfc.iref.i.2"></div>
1070            <div id="rfc.iref.h.4"></div>
1071            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.if-none-match">If-None-Match</a></h2>
1072            <p id="rfc.section.3.2.p.1">The "If-None-Match" header field <em class="bcp14">MAY</em> be used to make a request method conditional on not matching any of the current entity-tag values for representations of the
1073               target resource. If-None-Match is primarily used in conditional GET requests to enable efficient updates of cached information
1074               with a minimum amount of transaction overhead. A client that has one or more representations previously obtained from the
1075               target resource can send If-None-Match with a list of the associated entity-tags in the hope of receiving a 304 response if
1076               at least one of those representations matches the selected representation.
1077            </p>
1078            <p id="rfc.section.3.2.p.2">If-None-Match <em class="bcp14">MAY</em> also be used with a value of "*" to prevent an unsafe request method (e.g., PUT) from inadvertently modifying an existing
1079               representation of the target resource when the client believes that the resource does not have a current representation. This
1080               is a variation on the "lost update" problem that might arise if more than one client attempts to create an initial representation
1081               for the target resource.
1082            </p>
1083            <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.if-none-match" class="smpl">If-None-Match</a> = "*" / 1#<a href="#header.etag" class="smpl">entity-tag</a>
1084</pre><p id="rfc.section.3.2.p.4">If any of the entity-tags listed in the If-None-Match field-value match (as per <a href="#entity.tag.comparison" title="Comparison">Section&nbsp;2.3.2</a>) the entity-tag of the selected representation, or if "*" is given and any current representation exists for that resource,
1085               then the server <em class="bcp14">MUST NOT</em> perform the requested method. Instead, if the request method was GET or HEAD, the server <em class="bcp14">SHOULD</em> respond with a 304 (Not Modified) status code, including the cache-related header fields (particularly ETag) of the selected
1086               representation that has a matching entity-tag. For all other request methods, the server <em class="bcp14">MUST</em> respond with a 412 (Precondition Failed) status code.
1087            </p>
1088            <p id="rfc.section.3.2.p.5">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.
1089            </p>
1090            <p id="rfc.section.3.2.p.6">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status code, then
1091               the If-None-Match header field <em class="bcp14">MUST</em> be ignored. (See <a href="#rules.for.when.to.use.entity.tags.and.last-modified.dates" title="Rules for When to Use Entity-tags and Last-Modified Dates">Section&nbsp;2.4</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
1092            </p>
1093            <p id="rfc.section.3.2.p.7">Examples:</p>
1094            <div id="rfc.figure.u.12"></div><pre class="text">  If-None-Match: "xyzzy"
1095  If-None-Match: W/"xyzzy"
1096  If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
1097  If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
1098  If-None-Match: *
1099</pre><p id="rfc.section.3.2.p.9">The result of a request having both an If-None-Match header field and either an If-Match or an If-Unmodified-Since header
1100               field is undefined by this specification.
1101            </p>
1102         </div>
1103         <div id="header.if-modified-since">
1104            <div id="rfc.iref.i.3"></div>
1105            <div id="rfc.iref.h.5"></div>
1106            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></h2>
1107            <p id="rfc.section.3.3.p.1">The "If-Modified-Since" header field <em class="bcp14">MAY</em> be used to make a request method conditional by modification date: if the selected representation has not been modified since
1108               the time specified in this field, then do not perform the request method; instead, respond as detailed below.
1109            </p>
1110            <div id="rfc.figure.u.13"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> = <a href="#notation" class="smpl">HTTP-date</a>
1111</pre><p id="rfc.section.3.3.p.3">An example of the field is:</p>
1112            <div id="rfc.figure.u.14"></div><pre class="text">  If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
1113</pre><p id="rfc.section.3.3.p.5">A GET method with an If-Modified-Since header field and no Range header field requests that the selected representation be
1114               transferred only if it has been modified since the date given by the If-Modified-Since header field. The algorithm for determining
1115               this includes the following cases:
1116            </p>
1117            <ol>
1118               <li>If the request would normally result in anything other than a 200 (OK) status code, or if the passed If-Modified-Since date
1119                  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
1120                  invalid.
1121               </li>
1122               <li>If the selected representation has been modified since the If-Modified-Since date, the response is exactly the same as for
1123                  a normal GET.
1124               </li>
1125               <li>If the selected 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.
1126               </li>
1127            </ol>
1128            <p id="rfc.section.3.3.p.6">The purpose of this feature is to allow efficient updates of cached information with a minimum amount of transaction overhead. </p>
1129            <ul class="empty">
1130               <li><b>Note:</b> The Range 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.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> for full details.
1131               </li>
1132               <li><b>Note:</b> If-Modified-Since times are interpreted by the server, whose clock might not be synchronized with the client.
1133               </li>
1134               <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
1135                  function, for deciding whether to send a 304 (Not Modified) response. To get best results when sending an If-Modified-Since
1136                  header field for cache validation, clients are advised to use the exact date string received in a previous Last-Modified header
1137                  field whenever possible.
1138               </li>
1139               <li><b>Note:</b> If a client uses an arbitrary date in the If-Modified-Since header field instead of a date taken from the Last-Modified header
1140                  field for the same request, the client needs to be aware that this date is interpreted in the server's understanding of time.
1141                  Unsynchronized clocks and rounding problems, due to the different encodings of time between the client and server, are concerns.
1142                  This includes the possibility of race conditions if the document has changed between the time it was first requested and the
1143                  If-Modified-Since date of a subsequent request, and the possibility of clock-skew-related problems if the If-Modified-Since
1144                  date is derived from the client's clock without correction to the server's clock. Corrections for different time bases between
1145                  client and server are at best approximate due to network latency.
1146               </li>
1147            </ul>
1148            <p id="rfc.section.3.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
1149               field is undefined by this specification.
1150            </p>
1151         </div>
1152         <div id="header.if-unmodified-since">
1153            <div id="rfc.iref.i.4"></div>
1154            <div id="rfc.iref.h.6"></div>
1155            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></h2>
1156            <p id="rfc.section.3.4.p.1">The "If-Unmodified-Since" header field <em class="bcp14">MAY</em> be used to make a request method conditional by modification date: if the selected representation has been modified since
1157               the time specified in this field, then the server <em class="bcp14">MUST NOT</em> perform the requested operation and <em class="bcp14">MUST</em> instead respond with the 412 (Precondition Failed) status code. If the selected representation has not been modified since
1158               the time specified in this field, the server <em class="bcp14">SHOULD</em> perform the request method as if the If-Unmodified-Since header field were not present.
1159            </p>
1160            <div id="rfc.figure.u.15"></div><pre class="inline"><span id="rfc.iref.g.10"></span>  <a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> = <a href="#notation" class="smpl">HTTP-date</a>
1161</pre><p id="rfc.section.3.4.p.3">An example of the field is:</p>
1162            <div id="rfc.figure.u.16"></div><pre class="text">  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
1163</pre><p id="rfc.section.3.4.p.5">If the request normally (i.e., without the If-Unmodified-Since header field) would result in anything other than a 2xx or
1164               412 status code, the If-Unmodified-Since header field <em class="bcp14">SHOULD</em> be ignored.
1165            </p>
1166            <p id="rfc.section.3.4.p.6">If the specified date is invalid, the header field <em class="bcp14">MUST</em> be ignored.
1167            </p>
1168            <p id="rfc.section.3.4.p.7">The result of a request having both an If-Unmodified-Since header field and either an If-None-Match or an If-Modified-Since
1169               header field is undefined by this specification.
1170            </p>
1171         </div>
1172         <div id="header.if-range">
1173            <h2 id="rfc.section.3.5"><a href="#rfc.section.3.5">3.5</a>&nbsp;<a href="#header.if-range">If-Range</a></h2>
1174            <p id="rfc.section.3.5.p.1">The If-Range header field provides a special conditional request mechanism that is similar to If-Match and If-Unmodified-Since
1175               but specific to HTTP range requests. If-Range is defined in <a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.2"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>.
1176            </p>
1177         </div>
1178      </div>
1179      <div id="status.code.definitions">
1180         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
1181         <div id="status.304">
1182            <div id="rfc.iref.3.1"></div>
1183            <div id="rfc.iref.s.2"></div>
1184            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#status.304">304 Not Modified</a></h2>
1185            <p id="rfc.section.4.1.p.1">The 304 status code indicates that a conditional GET request has been received and would have resulted in a 200 (OK) response
1186               if it were not for the fact that the condition has evaluated to false. In other words, there is no need for the server to
1187               transfer a representation of the target resource because the client's request indicates that it already has a valid representation,
1188               as indicated by the 304 response header fields, and is therefore redirecting the client to make use of that stored representation
1189               as if it were the payload of a 200 response. 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.
1190            </p>
1191            <p id="rfc.section.4.1.p.2">A 304 response <em class="bcp14">MUST</em> include a Date header field (<a href="p2-semantics.html#header.date" title="Date">Section 10.2</a> of <a href="#Part2" id="rfc.xref.Part2.3"><cite title="HTTP/1.1, part 2: Message Semantics">[Part2]</cite></a>) unless the origin server does not have a clock that can provide a reasonable approximation of the current time. If a 200
1192               response to the same request would have included any of the header fields Cache-Control, Content-Location, ETag, Expires,
1193               or Vary, then those same header fields <em class="bcp14">MUST</em> be sent in a 304 response.
1194            </p>
1195            <p id="rfc.section.4.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,
1196               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
1197               cache updates (e.g., future HTTP extensions).
1198            </p>
1199            <p id="rfc.section.4.1.p.4">If the recipient of a 304 response does not have a cached representation corresponding to the entity-tag indicated by the
1200               304 response, then the recipient <em class="bcp14">MUST NOT</em> use the 304 to update its own cache. If this conditional request originated with an outbound client, such as a user agent
1201               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, the recipient <em class="bcp14">MUST</em> disregard the 304 response and repeat the request without any preconditions.
1202            </p>
1203            <p id="rfc.section.4.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.
1204            </p>
1205         </div>
1206         <div id="status.412">
1207            <div id="rfc.iref.4.1"></div>
1208            <div id="rfc.iref.s.3"></div>
1209            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#status.412">412 Precondition Failed</a></h2>
1210            <p id="rfc.section.4.2.p.1">The 412 status code indicates that one or more preconditions given in the request header fields evaluated to false when tested
1211               on the server. This response code allows the client to place preconditions on the current resource state (its current representations
1212               and metadata) and thus prevent the request method from being applied if the target resource is in an unexpected state.
1213            </p>
1214         </div>
1215      </div>
1216      <div id="IANA.considerations">
1217         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
1218         <div id="status.code.registration">
1219            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
1220            <p id="rfc.section.5.1.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below:
1221            </p>
1222            <div id="rfc.table.1">
1223               <div id="iana.status.code.registration.table"></div>
1224               <table class="tt full left" cellpadding="3" cellspacing="0">
1225                  <thead>
1226                     <tr>
1227                        <th>Value</th>
1228                        <th>Description</th>
1229                        <th>Reference</th>
1230                     </tr>
1231                  </thead>
1232                  <tbody>
1233                     <tr>
1234                        <td class="left">304</td>
1235                        <td class="left">Not Modified</td>
1236                        <td class="left"><a href="#status.304" id="rfc.xref.status.304.1" title="304 Not Modified">Section&nbsp;4.1</a>
1237                        </td>
1238                     </tr>
1239                     <tr>
1240                        <td class="left">412</td>
1241                        <td class="left">Precondition Failed</td>
1242                        <td class="left"><a href="#status.412" id="rfc.xref.status.412.1" title="412 Precondition Failed">Section&nbsp;4.2</a>
1243                        </td>
1244                     </tr>
1245                  </tbody>
1246               </table>
1247            </div>
1248         </div>
1249         <div id="header.field.registration">
1250            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
1251            <p id="rfc.section.5.2.p.1">The Message Header Field Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&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>):
1252            </p>
1253            <div id="rfc.table.2">
1254               <div id="iana.header.registration.table"></div>
1255               <table class="tt full left" cellpadding="3" cellspacing="0">
1256                  <thead>
1257                     <tr>
1258                        <th>Header Field Name</th>
1259                        <th>Protocol</th>
1260                        <th>Status</th>
1261                        <th>Reference</th>
1262                     </tr>
1263                  </thead>
1264                  <tbody>
1265                     <tr>
1266                        <td class="left">ETag</td>
1267                        <td class="left">http</td>
1268                        <td class="left">standard</td>
1269                        <td class="left"><a href="#header.etag" id="rfc.xref.header.etag.1" title="ETag">Section&nbsp;2.3</a>
1270                        </td>
1271                     </tr>
1272                     <tr>
1273                        <td class="left">If-Match</td>
1274                        <td class="left">http</td>
1275                        <td class="left">standard</td>
1276                        <td class="left"><a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;3.1</a>
1277                        </td>
1278                     </tr>
1279                     <tr>
1280                        <td class="left">If-Modified-Since</td>
1281                        <td class="left">http</td>
1282                        <td class="left">standard</td>
1283                        <td class="left"><a href="#header.if-modified-since" id="rfc.xref.header.if-modified-since.1" title="If-Modified-Since">Section&nbsp;3.3</a>
1284                        </td>
1285                     </tr>
1286                     <tr>
1287                        <td class="left">If-None-Match</td>
1288                        <td class="left">http</td>
1289                        <td class="left">standard</td>
1290                        <td class="left"><a href="#header.if-none-match" id="rfc.xref.header.if-none-match.1" title="If-None-Match">Section&nbsp;3.2</a>
1291                        </td>
1292                     </tr>
1293                     <tr>
1294                        <td class="left">If-Unmodified-Since</td>
1295                        <td class="left">http</td>
1296                        <td class="left">standard</td>
1297                        <td class="left"><a href="#header.if-unmodified-since" id="rfc.xref.header.if-unmodified-since.1" title="If-Unmodified-Since">Section&nbsp;3.4</a>
1298                        </td>
1299                     </tr>
1300                     <tr>
1301                        <td class="left">Last-Modified</td>
1302                        <td class="left">http</td>
1303                        <td class="left">standard</td>
1304                        <td class="left"><a href="#header.last-modified" id="rfc.xref.header.last-modified.1" title="Last-Modified">Section&nbsp;2.2</a>
1305                        </td>
1306                     </tr>
1307                  </tbody>
1308               </table>
1309            </div>
1310            <p id="rfc.section.5.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1311         </div>
1312      </div>
1313      <div id="security.considerations">
1314         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
1315         <p id="rfc.section.6.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
1316         </p>
1317      </div>
1318      <div id="acks">
1319         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#acks">Acknowledgments</a></h1>
1320         <p id="rfc.section.7.p.1">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
1321         </p>
1322      </div>
1323      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
1324      </h1>
1325      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
1326      </h2>
1327      <table>
1328         <tr>
1329            <td class="reference"><b id="Part1">[Part1]</b></td>
1330            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-19">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-19 (work in progress), March&nbsp;2012.
1331            </td>
1332         </tr>
1333         <tr>
1334            <td class="reference"><b id="Part2">[Part2]</b></td>
1335            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-19">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-19 (work in progress), March&nbsp;2012.
1336            </td>
1337         </tr>
1338         <tr>
1339            <td class="reference"><b id="Part3">[Part3]</b></td>
1340            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-19">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-19 (work in progress), March&nbsp;2012.
1341            </td>
1342         </tr>
1343         <tr>
1344            <td class="reference"><b id="Part5">[Part5]</b></td>
1345            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p5-range-19">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-19 (work in progress), March&nbsp;2012.
1346            </td>
1347         </tr>
1348         <tr>
1349            <td class="reference"><b id="Part6">[Part6]</b></td>
1350            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Rackspace">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-19">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-19 (work in progress), March&nbsp;2012.
1351            </td>
1352         </tr>
1353         <tr>
1354            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1355            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
1356            </td>
1357         </tr>
1358         <tr>
1359            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1360            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
1361            </td>
1362         </tr>
1363      </table>
1364      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
1365      </h2>
1366      <table>
1367         <tr>
1368            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1369            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
1370            </td>
1371         </tr>
1372         <tr>
1373            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1374            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
1375            </td>
1376         </tr>
1377         <tr>
1378            <td class="reference"><b id="RFC4918">[RFC4918]</b></td>
1379            <td class="top"><a href="mailto:ldusseault@commerce.net" title="CommerceNet">Dusseault, L., Ed.</a>, “<a href="https://tools.ietf.org/html/rfc4918">HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)</a>”, RFC&nbsp;4918, June&nbsp;2007.
1380            </td>
1381         </tr>
1382      </table>
1383      <div id="changes.from.rfc.2616">
1384         <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>
1385         <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 versus Strong">2.1</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">3.2</a>).
1386         </p>
1387         <p id="rfc.section.A.p.2">Change ETag header field ABNF not to use quoted-string, thus avoiding escaping issues. (<a href="#header.etag" id="rfc.xref.header.etag.2" title="ETag">Section&nbsp;2.3</a>)
1388         </p>
1389         <p id="rfc.section.A.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Precondition Header Fields">Section&nbsp;3</a>)
1390         </p>
1391      </div>
1392      <div id="collected.abnf">
1393         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
1394         <div id="rfc.figure.u.17"></div><pre class="inline"><a href="#header.etag" class="smpl">ETag</a> = entity-tag
1395
1396<a href="#notation" class="smpl">HTTP-date</a> = &lt;HTTP-date, defined in [Part2], Section 8&gt;
1397
1398<a href="#header.if-match" class="smpl">If-Match</a> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1399 entity-tag ] ) )
1400<a href="#header.if-modified-since" class="smpl">If-Modified-Since</a> = HTTP-date
1401<a href="#header.if-none-match" class="smpl">If-None-Match</a> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1402 entity-tag ] ) )
1403<a href="#header.if-unmodified-since" class="smpl">If-Unmodified-Since</a> = HTTP-date
1404
1405<a href="#header.last-modified" class="smpl">Last-Modified</a> = HTTP-date
1406
1407<a href="#notation" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
1408
1409<a href="#header.etag" class="smpl">entity-tag</a> = [ weak ] opaque-tag
1410<a href="#header.etag" class="smpl">etagc</a> = "!" / %x23-7E ; '#'-'~'
1411 / obs-text
1412
1413<a href="#notation" class="smpl">obs-text</a> = &lt;obs-text, defined in [Part1], Section 3.2.4&gt;
1414<a href="#header.etag" class="smpl">opaque-tag</a> = DQUOTE *etagc DQUOTE
1415
1416<a href="#header.etag" class="smpl">weak</a> = %x57.2F ; W/
1417</pre><div id="rfc.figure.u.18"></div>
1418         <p>ABNF diagnostics:</p><pre class="inline">; ETag defined but not used
1419; If-Match defined but not used
1420; If-Modified-Since defined but not used
1421; If-None-Match defined but not used
1422; If-Unmodified-Since defined but not used
1423; Last-Modified defined but not used
1424</pre></div>
1425      <div id="change.log">
1426         <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>
1427         <div>
1428            <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
1429            </h2>
1430            <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>.
1431            </p>
1432         </div>
1433         <div>
1434            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p4-conditional-00
1435            </h2>
1436            <p id="rfc.section.C.2.p.1">Closed issues: </p>
1437            <ul>
1438               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
1439               </li>
1440            </ul>
1441            <p id="rfc.section.C.2.p.2">Other changes: </p>
1442            <ul>
1443               <li>Move definitions of 304 and 412 condition codes from Part2.</li>
1444            </ul>
1445         </div>
1446         <div>
1447            <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p4-conditional-01
1448            </h2>
1449            <p id="rfc.section.C.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1450            </p>
1451            <ul>
1452               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1453            </ul>
1454         </div>
1455         <div id="changes.since.02">
1456            <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>
1457            <p id="rfc.section.C.4.p.1">Closed issues: </p>
1458            <ul>
1459               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/116">http://tools.ietf.org/wg/httpbis/trac/ticket/116</a>&gt;: "Weak ETags on non-GET requests"
1460               </li>
1461            </ul>
1462            <p id="rfc.section.C.4.p.2">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
1463            </p>
1464            <ul>
1465               <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
1466            </ul>
1467         </div>
1468         <div id="changes.since.03">
1469            <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>
1470            <p id="rfc.section.C.5.p.1">Closed issues: </p>
1471            <ul>
1472               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/71">http://tools.ietf.org/wg/httpbis/trac/ticket/71</a>&gt;: "Examples for ETag matching"
1473               </li>
1474               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/124">http://tools.ietf.org/wg/httpbis/trac/ticket/124</a>&gt;: "'entity value' undefined"
1475               </li>
1476               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/126">http://tools.ietf.org/wg/httpbis/trac/ticket/126</a>&gt;: "bogus 2068 Date header reference"
1477               </li>
1478            </ul>
1479         </div>
1480         <div id="changes.since.04">
1481            <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>
1482            <p id="rfc.section.C.6.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1483            </p>
1484            <ul>
1485               <li>Use "/" instead of "|" for alternatives.</li>
1486               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1487               <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
1488            </ul>
1489         </div>
1490         <div id="changes.since.05">
1491            <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>
1492            <p id="rfc.section.C.7.p.1">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
1493            </p>
1494            <ul>
1495               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1496            </ul>
1497         </div>
1498         <div id="changes.since.06">
1499            <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>
1500            <p id="rfc.section.C.8.p.1">Closed issues: </p>
1501            <ul>
1502               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/153">http://tools.ietf.org/wg/httpbis/trac/ticket/153</a>&gt;: "case-sensitivity of etag weakness indicator"
1503               </li>
1504            </ul>
1505         </div>
1506         <div id="changes.since.07">
1507            <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>
1508            <p id="rfc.section.C.9.p.1">Closed issues: </p>
1509            <ul>
1510               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/116">http://tools.ietf.org/wg/httpbis/trac/ticket/116</a>&gt;: "Weak ETags on non-GET requests" (If-Match still was defined to require strong matching)
1511               </li>
1512               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>&gt;: "move IANA registrations for optional status codes"
1513               </li>
1514            </ul>
1515         </div>
1516         <div id="changes.since.08">
1517            <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>
1518            <p id="rfc.section.C.10.p.1">No significant changes.</p>
1519         </div>
1520         <div id="changes.since.09">
1521            <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>
1522            <p id="rfc.section.C.11.p.1">No significant changes.</p>
1523         </div>
1524         <div id="changes.since.10">
1525            <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>
1526            <p id="rfc.section.C.12.p.1">Closed issues: </p>
1527            <ul>
1528               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/69">http://tools.ietf.org/wg/httpbis/trac/ticket/69</a>&gt;: "Clarify 'Requested Variant'"
1529               </li>
1530               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/109">http://tools.ietf.org/wg/httpbis/trac/ticket/109</a>&gt;: "Clarify entity / representation / variant terminology"
1531               </li>
1532               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/220">http://tools.ietf.org/wg/httpbis/trac/ticket/220</a>&gt;: "consider removing the 'changes from 2068' sections"
1533               </li>
1534            </ul>
1535         </div>
1536         <div id="changes.since.11">
1537            <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p4-conditional-11</a></h2>
1538            <p id="rfc.section.C.13.p.1">None.</p>
1539         </div>
1540         <div id="changes.since.12">
1541            <h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p4-conditional-12</a></h2>
1542            <p id="rfc.section.C.14.p.1">Closed issues: </p>
1543            <ul>
1544               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
1545               </li>
1546            </ul>
1547         </div>
1548         <div id="changes.since.13">
1549            <h2 id="rfc.section.C.15"><a href="#rfc.section.C.15">C.15</a>&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p4-conditional-13</a></h2>
1550            <p id="rfc.section.C.15.p.1">Closed issues: </p>
1551            <ul>
1552               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/89">http://tools.ietf.org/wg/httpbis/trac/ticket/89</a>&gt;: "If-* and entities"
1553               </li>
1554               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/101">http://tools.ietf.org/wg/httpbis/trac/ticket/101</a>&gt;: "Definition of validator weakness"
1555               </li>
1556               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
1557               </li>
1558               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/269">http://tools.ietf.org/wg/httpbis/trac/ticket/269</a>&gt;: "ETags and Quotes"
1559               </li>
1560            </ul>
1561         </div>
1562         <div id="changes.since.14">
1563            <h2 id="rfc.section.C.16"><a href="#rfc.section.C.16">C.16</a>&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p4-conditional-14</a></h2>
1564            <p id="rfc.section.C.16.p.1">None.</p>
1565         </div>
1566         <div id="changes.since.15">
1567            <h2 id="rfc.section.C.17"><a href="#rfc.section.C.17">C.17</a>&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p4-conditional-15</a></h2>
1568            <p id="rfc.section.C.17.p.1">Closed issues: </p>
1569            <ul>
1570               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/304">http://tools.ietf.org/wg/httpbis/trac/ticket/304</a>&gt;: "If-Range should be listed when dicussing contexts where L-M can be considered strong"
1571               </li>
1572            </ul>
1573         </div>
1574         <div id="changes.since.16">
1575            <h2 id="rfc.section.C.18"><a href="#rfc.section.C.18">C.18</a>&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p4-conditional-16</a></h2>
1576            <p id="rfc.section.C.18.p.1">Closed issues: </p>
1577            <ul>
1578               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>&gt;: "Document HTTP's error-handling philosophy"
1579               </li>
1580            </ul>
1581         </div>
1582         <div id="changes.since.17">
1583            <h2 id="rfc.section.C.19"><a href="#rfc.section.C.19">C.19</a>&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p4-conditional-17</a></h2>
1584            <p id="rfc.section.C.19.p.1">Closed issues: </p>
1585            <ul>
1586               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/306">http://tools.ietf.org/wg/httpbis/trac/ticket/306</a>&gt;: "does etag value really use quoted-string"
1587               </li>
1588            </ul>
1589         </div>
1590         <div id="changes.since.18">
1591            <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p4-conditional-18</a></h2>
1592            <p id="rfc.section.C.20.p.1">Closed issues: </p>
1593            <ul>
1594               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/345">http://tools.ietf.org/wg/httpbis/trac/ticket/345</a>&gt;: "Required headers on 304 and 206"
1595               </li>
1596            </ul>
1597         </div>
1598      </div>
1599      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1600      <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.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a>
1601      </p>
1602      <div class="print2col">
1603         <ul class="ind">
1604            <li><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul>
1605                  <li>304 Not Modified (status code)&nbsp;&nbsp;<a href="#rfc.iref.3.1"><b>4.1</b></a>, <a href="#rfc.xref.status.304.1">5.1</a></li>
1606               </ul>
1607            </li>
1608            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1609                  <li>412 Precondition Failed (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>4.2</b></a>, <a href="#rfc.xref.status.412.1">5.1</a></li>
1610               </ul>
1611            </li>
1612            <li><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul>
1613                  <li>ETag header field&nbsp;&nbsp;<a href="#rfc.iref.e.1"><b>2.3</b></a>, <a href="#rfc.xref.header.etag.1">5.2</a>, <a href="#rfc.xref.header.etag.2">A</a></li>
1614               </ul>
1615            </li>
1616            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1617                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1618                     <ul>
1619                        <li><tt>entity-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2.3</b></a></li>
1620                        <li><tt>ETag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.3</b></a></li>
1621                        <li><tt>etagc</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>2.3</b></a></li>
1622                        <li><tt>If-Match</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.1</b></a></li>
1623                        <li><tt>If-Modified-Since</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.3</b></a></li>
1624                        <li><tt>If-None-Match</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.2</b></a></li>
1625                        <li><tt>If-Unmodified-Since</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.4</b></a></li>
1626                        <li><tt>Last-Modified</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2.2</b></a></li>
1627                        <li><tt>opaque-tag</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>2.3</b></a></li>
1628                        <li><tt>weak</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>2.3</b></a></li>
1629                     </ul>
1630                  </li>
1631               </ul>
1632            </li>
1633            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1634                  <li>Header Fields&nbsp;&nbsp;
1635                     <ul>
1636                        <li>ETag&nbsp;&nbsp;<a href="#rfc.iref.h.2"><b>2.3</b></a>, <a href="#rfc.xref.header.etag.1">5.2</a>, <a href="#rfc.xref.header.etag.2">A</a></li>
1637                        <li>If-Match&nbsp;&nbsp;<a href="#rfc.iref.h.3"><b>3.1</b></a>, <a href="#rfc.xref.header.if-match.1">5.2</a></li>
1638                        <li>If-Modified-Since&nbsp;&nbsp;<a href="#rfc.iref.h.5"><b>3.3</b></a>, <a href="#rfc.xref.header.if-modified-since.1">5.2</a></li>
1639                        <li>If-None-Match&nbsp;&nbsp;<a href="#rfc.iref.h.4"><b>3.2</b></a>, <a href="#rfc.xref.header.if-none-match.1">5.2</a>, <a href="#rfc.xref.header.if-none-match.2">A</a></li>
1640                        <li>If-Unmodified-Since&nbsp;&nbsp;<a href="#rfc.iref.h.6"><b>3.4</b></a>, <a href="#rfc.xref.header.if-unmodified-since.1">5.2</a></li>
1641                        <li>Last-Modified&nbsp;&nbsp;<a href="#rfc.iref.h.1"><b>2.2</b></a>, <a href="#rfc.xref.header.last-modified.1">5.2</a></li>
1642                     </ul>
1643                  </li>
1644               </ul>
1645            </li>
1646            <li><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul>
1647                  <li>If-Match header field&nbsp;&nbsp;<a href="#rfc.iref.i.1"><b>3.1</b></a>, <a href="#rfc.xref.header.if-match.1">5.2</a></li>
1648                  <li>If-Modified-Since header field&nbsp;&nbsp;<a href="#rfc.iref.i.3"><b>3.3</b></a>, <a href="#rfc.xref.header.if-modified-since.1">5.2</a></li>
1649                  <li>If-None-Match header field&nbsp;&nbsp;<a href="#rfc.iref.i.2"><b>3.2</b></a>, <a href="#rfc.xref.header.if-none-match.1">5.2</a>, <a href="#rfc.xref.header.if-none-match.2">A</a></li>
1650                  <li>If-Unmodified-Since header field&nbsp;&nbsp;<a href="#rfc.iref.i.4"><b>3.4</b></a>, <a href="#rfc.xref.header.if-unmodified-since.1">5.2</a></li>
1651               </ul>
1652            </li>
1653            <li><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul>
1654                  <li>Last-Modified header field&nbsp;&nbsp;<a href="#rfc.iref.l.1"><b>2.2</b></a>, <a href="#rfc.xref.header.last-modified.1">5.2</a></li>
1655               </ul>
1656            </li>
1657            <li><a id="rfc.index.M" href="#rfc.index.M"><b>M</b></a><ul>
1658                  <li>metadata&nbsp;&nbsp;<a href="#rfc.iref.m.1"><b>2</b></a></li>
1659               </ul>
1660            </li>
1661            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1662                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2</a>, <a href="#rfc.xref.Part1.4">1.2</a>, <a href="#rfc.xref.Part1.5">1.2</a>, <a href="#rfc.xref.Part1.6">2.3.3</a>, <a href="#rfc.xref.Part1.7">6</a>, <a href="#rfc.xref.Part1.8">7</a>, <a href="#Part1"><b>8.1</b></a><ul>
1663                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
1664                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
1665                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.2</a></li>
1666                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.5">1.2</a></li>
1667                        <li><em>Section 4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2.3.3</a></li>
1668                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">7</a></li>
1669                     </ul>
1670                  </li>
1671                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1.2</a>, <a href="#rfc.xref.Part2.2">1.2</a>, <a href="#rfc.xref.Part2.3">4.1</a>, <a href="#Part2"><b>8.1</b></a><ul>
1672                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.2">1.2</a></li>
1673                        <li><em>Section 10.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.3">4.1</a></li>
1674                     </ul>
1675                  </li>
1676                  <li><em>Part3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">2.3.3</a>, <a href="#rfc.xref.Part3.2">2.3.3</a>, <a href="#Part3"><b>8.1</b></a><ul>
1677                        <li><em>Section 5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.1">2.3.3</a></li>
1678                        <li><em>Section 6.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part3.2">2.3.3</a></li>
1679                     </ul>
1680                  </li>
1681                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.3</a>, <a href="#rfc.xref.Part5.2">3.5</a>, <a href="#Part5"><b>8.1</b></a><ul>
1682                        <li><em>Section 5.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.2">3.5</a></li>
1683                        <li><em>Section 5.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">3.3</a></li>
1684                     </ul>
1685                  </li>
1686                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#rfc.xref.Part6.2">2.2.1</a>, <a href="#rfc.xref.Part6.3">2.3.1</a>, <a href="#Part6"><b>8.1</b></a></li>
1687               </ul>
1688            </li>
1689            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1690                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li>
1691                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">2.3</a>, <a href="#RFC2616"><b>8.2</b></a>, <a href="#rfc.xref.RFC2616.2">C.1</a><ul>
1692                        <li><em>Section 3.11</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">2.3</a></li>
1693                     </ul>
1694                  </li>
1695                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">5.2</a>, <a href="#RFC3864"><b>8.2</b></a></li>
1696                  <li><em>RFC4918</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4918.1">2</a>, <a href="#RFC4918"><b>8.2</b></a></li>
1697                  <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>8.1</b></a><ul>
1698                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
1699                     </ul>
1700                  </li>
1701               </ul>
1702            </li>
1703            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1704                  <li>selected representation&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>1</b></a></li>
1705                  <li>Status Codes&nbsp;&nbsp;
1706                     <ul>
1707                        <li>304 Not Modified&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>4.1</b></a>, <a href="#rfc.xref.status.304.1">5.1</a></li>
1708                        <li>412 Precondition Failed&nbsp;&nbsp;<a href="#rfc.iref.s.3"><b>4.2</b></a>, <a href="#rfc.xref.status.412.1">5.1</a></li>
1709                     </ul>
1710                  </li>
1711               </ul>
1712            </li>
1713            <li><a id="rfc.index.V" href="#rfc.index.V"><b>V</b></a><ul>
1714                  <li>validator&nbsp;&nbsp;<a href="#rfc.iref.v.1"><b>2</b></a><ul>
1715                        <li>strong&nbsp;&nbsp;<a href="#rfc.iref.v.3"><b>2.1</b></a></li>
1716                        <li>weak&nbsp;&nbsp;<a href="#rfc.iref.v.2"><b>2.1</b></a></li>
1717                     </ul>
1718                  </li>
1719               </ul>
1720            </li>
1721         </ul>
1722      </div>
1723      <div class="avoidbreak">
1724         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1725         <p><b>Roy T. Fielding</b>
1726            (editor)
1727            <br>Adobe Systems Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
1728         <p><b>Yves Lafon</b>
1729            (editor)
1730            <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="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
1731         <p><b>Julian F. Reschke</b>
1732            (editor)
1733            <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="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
1734      </div>
1735   </body>
1736</html>
Note: See TracBrowser for help on using the repository browser.