source: draft-ietf-httpbis/latest/p4-conditional.html @ 183

Last change on this file since 183 was 183, checked in by fielding@…, 12 years ago

Reduce the description of cache validation to just those bits that
summarize what a cache SHOULD do, thus avoiding the need to respecify
what is defined in part 4. Move cache validator descriptions
to the associated header field definitions in part 4 (to be merged
at a later time).

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 80.8 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://www.w3.org/2006/03/hcard">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 4: Conditional Requests</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
9}
10a.smpl {
11  color: black;
12}
13a:hover {
14  text-decoration: underline;
15}
16a:active {
17  text-decoration: underline;
18}
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
23}
24body {
25  color: black;
26  font-family: verdana, helvetica, arial, sans-serif;
27  font-size: 10pt;
28}
29cite {
30  font-style: normal;
31}
32dd {
33  margin-right: 2em;
34}
35dl {
36  margin-left: 2em;
37}
38
39dl.empty dd {
40  margin-top: .5em;
41}
42dl p {
43  margin-left: 0em;
44}
45dt {
46  margin-top: .5em;
47}
48h1 {
49  font-size: 14pt;
50  line-height: 21pt;
51  page-break-after: avoid;
52}
53h1.np {
54  page-break-before: always;
55}
56h1 a {
57  color: #333333;
58}
59h2 {
60  font-size: 12pt;
61  line-height: 15pt;
62  page-break-after: avoid;
63}
64h2 a {
65  color: black;
66}
67h3 {
68  font-size: 10pt;
69  page-break-after: avoid;
70}
71h3 a {
72  color: black;
73}
74h4 {
75  font-size: 10pt;
76  page-break-after: avoid;
77}
78h4 a {
79  color: black;
80}
81h5 {
82  font-size: 10pt;
83  page-break-after: avoid;
84}
85h5 a {
86  color: black;
87}
88img {
89  margin-left: 3em;
90}
91li {
92  margin-left: 2em;
93  margin-right: 2em;
94}
95ol {
96  margin-left: 2em;
97  margin-right: 2em;
98}
99ol p {
100  margin-left: 0em;
101}
102p {
103  margin-left: 2em;
104  margin-right: 2em;
105}
106pre {
107  margin-left: 3em;
108  background-color: lightyellow;
109  padding: .25em;
110}
111pre.text2 {
112  border-style: dotted;
113  border-width: 1px;
114  background-color: #f0f0f0;
115  width: 69em;
116}
117pre.inline {
118  background-color: white;
119  padding: 0em;
120}
121pre.text {
122  border-style: dotted;
123  border-width: 1px;
124  background-color: #f8f8f8;
125  width: 69em;
126}
127pre.drawing {
128  border-style: solid;
129  border-width: 1px;
130  background-color: #f8f8f8;
131  padding: 2em;
132}
133table {
134  margin-left: 2em;
135}
136table.header {
137  width: 95%;
138  font-size: 10pt;
139  color: white;
140}
141td.top {
142  vertical-align: top;
143}
144td.topnowrap {
145  vertical-align: top;
146  white-space: nowrap; 
147}
148td.header {
149  background-color: gray;
150  width: 50%;
151}
152td.reference {
153  vertical-align: top;
154  white-space: nowrap;
155  padding-right: 1em;
156}
157thead {
158  display:table-header-group;
159}
160ul.toc {
161  list-style: none;
162  margin-left: 1.5em;
163  margin-right: 0em;
164  padding-left: 0em;
165}
166li.tocline0 {
167  line-height: 150%;
168  font-weight: bold;
169  font-size: 10pt;
170  margin-left: 0em;
171  margin-right: 0em;
172}
173li.tocline1 {
174  line-height: normal;
175  font-weight: normal;
176  font-size: 9pt;
177  margin-left: 0em;
178  margin-right: 0em;
179}
180li.tocline2 {
181  font-size: 0pt;
182}
183ul p {
184  margin-left: 0em;
185}
186ul.ind {
187  list-style: none;
188  margin-left: 1.5em;
189  margin-right: 0em;
190  padding-left: 0em;
191}
192li.indline0 {
193  font-weight: bold;
194  line-height: 200%;
195  margin-left: 0em;
196  margin-right: 0em;
197}
198li.indline1 {
199  font-weight: normal;
200  line-height: 150%;
201  margin-left: 0em;
202  margin-right: 0em;
203}
204.bcp14 {
205  font-style: normal;
206  text-transform: lowercase;
207  font-variant: small-caps;
208}
209.comment {
210  background-color: yellow;
211}
212.center {
213  text-align: center;
214}
215.error {
216  color: red;
217  font-style: italic;
218  font-weight: bold;
219}
220.figure {
221  font-weight: bold;
222  text-align: center;
223  font-size: 9pt;
224}
225.filename {
226  color: #333333;
227  font-weight: bold;
228  font-size: 12pt;
229  line-height: 21pt;
230  text-align: center;
231}
232.fn {
233  font-weight: bold;
234}
235.hidden {
236  display: none;
237}
238.left {
239  text-align: left;
240}
241.right {
242  text-align: right;
243}
244.title {
245  color: #990000;
246  font-size: 18pt;
247  line-height: 18pt;
248  font-weight: bold;
249  text-align: center;
250  margin-top: 36pt;
251}
252.vcardline {
253  display: block;
254}
255.warning {
256  font-size: 14pt;
257  background-color: yellow;
258}
259
260
261@media print {
262  .noprint {
263    display: none;
264  }
265 
266  a {
267    color: black;
268    text-decoration: none;
269  }
270
271  table.header {
272    width: 90%;
273  }
274
275  td.header {
276    width: 50%;
277    color: black;
278    background-color: white;
279    vertical-align: top;
280    font-size: 12pt;
281  }
282
283  ul.toc a::after {
284    content: leader('.') target-counter(attr(href), page);
285  }
286 
287  a.iref {
288    content: target-counter(attr(href), page);
289  }
290 
291  .print2col {
292    column-count: 2;
293    -moz-column-count: 2;
294    column-fill: auto;
295  }
296}
297
298@page {
299  @top-left {
300       content: "INTERNET DRAFT"; 
301  } 
302  @top-right {
303       content: "February 2008"; 
304  } 
305  @top-center {
306       content: "HTTP/1.1, Part 4"; 
307  } 
308  @bottom-left {
309       content: "Fielding, et al."; 
310  } 
311  @bottom-center {
312       content: "Standards Track"; 
313  } 
314  @bottom-right {
315       content: "[Page " counter(page) "]"; 
316  } 
317}
318
319@page:first { 
320    @top-left {
321      content: normal;
322    }
323    @top-right {
324      content: normal;
325    }
326    @top-center {
327      content: normal;
328    }
329}
330</style><link rel="Contents" href="#rfc.toc">
331      <link rel="Author" href="#rfc.authors">
332      <link rel="Copyright" href="#rfc.copyright">
333      <link rel="Index" href="#rfc.index">
334      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
335      <link rel="Chapter" title="2 Entity Tags" href="#rfc.section.2">
336      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
337      <link rel="Chapter" title="4 Weak and Strong Validators" href="#rfc.section.4">
338      <link rel="Chapter" title="5 Rules for When to Use Entity Tags and Last-Modified Dates" href="#rfc.section.5">
339      <link rel="Chapter" title="6 Header Field Definitions" href="#rfc.section.6">
340      <link rel="Chapter" title="7 IANA Considerations" href="#rfc.section.7">
341      <link rel="Chapter" title="8 Security Considerations" href="#rfc.section.8">
342      <link rel="Chapter" title="9 Acknowledgments" href="#rfc.section.9">
343      <link rel="Chapter" href="#rfc.section.10" title="10 References">
344      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
345      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
346      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.354, 2007/12/31 13:43:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
347      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
348      <meta name="DC.Creator" content="Fielding, R.">
349      <meta name="DC.Creator" content="Gettys, J.">
350      <meta name="DC.Creator" content="Mogul, J.">
351      <meta name="DC.Creator" content="Frystyk, H.">
352      <meta name="DC.Creator" content="Masinter, L.">
353      <meta name="DC.Creator" content="Leach, P.">
354      <meta name="DC.Creator" content="Berners-Lee, T.">
355      <meta name="DC.Creator" content="Lafon, Y.">
356      <meta name="DC.Creator" content="Reschke, J. F.">
357      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
358      <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-02">
359      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
360      <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.">
361   </head>
362   <body>
363      <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
364         <tr>
365            <td class="header left">Network Working Group</td>
366            <td class="header right">R. Fielding, Editor</td>
367         </tr>
368         <tr>
369            <td class="header left">Internet Draft</td>
370            <td class="header right">Day Software</td>
371         </tr>
372         <tr>
373            <td class="header left">
374               &lt;draft-ietf-httpbis-p4-conditional-latest&gt;
375               
376            </td>
377            <td class="header right">J. Gettys</td>
378         </tr>
379         <tr>
380            <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
381            </td>
382            <td class="header right">One Laptop per Child</td>
383         </tr>
384         <tr>
385            <td class="header left">Intended status: Standards Track</td>
386            <td class="header right">J. Mogul</td>
387         </tr>
388         <tr>
389            <td class="header left">Expires: August 2008</td>
390            <td class="header right">HP</td>
391         </tr>
392         <tr>
393            <td class="header left"></td>
394            <td class="header right">H. Frystyk</td>
395         </tr>
396         <tr>
397            <td class="header left"></td>
398            <td class="header right">Microsoft</td>
399         </tr>
400         <tr>
401            <td class="header left"></td>
402            <td class="header right">L. Masinter</td>
403         </tr>
404         <tr>
405            <td class="header left"></td>
406            <td class="header right">Adobe Systems</td>
407         </tr>
408         <tr>
409            <td class="header left"></td>
410            <td class="header right">P. Leach</td>
411         </tr>
412         <tr>
413            <td class="header left"></td>
414            <td class="header right">Microsoft</td>
415         </tr>
416         <tr>
417            <td class="header left"></td>
418            <td class="header right">T. Berners-Lee</td>
419         </tr>
420         <tr>
421            <td class="header left"></td>
422            <td class="header right">W3C/MIT</td>
423         </tr>
424         <tr>
425            <td class="header left"></td>
426            <td class="header right">Y. Lafon, Editor</td>
427         </tr>
428         <tr>
429            <td class="header left"></td>
430            <td class="header right">W3C</td>
431         </tr>
432         <tr>
433            <td class="header left"></td>
434            <td class="header right">J. F. Reschke, Editor</td>
435         </tr>
436         <tr>
437            <td class="header left"></td>
438            <td class="header right">greenbytes</td>
439         </tr>
440         <tr>
441            <td class="header left"></td>
442            <td class="header right">February 2008</td>
443         </tr>
444      </table>
445      <p class="title">HTTP/1.1, part 4: Conditional Requests<br><span class="filename">draft-ietf-httpbis-p4-conditional-latest</span></p>
446      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
447      <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
448         is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
449         6 of BCP 79.
450      </p>
451      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
452         that other groups may also distribute working documents as Internet-Drafts.
453      </p>
454      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
455         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
456         in progress”.
457      </p>
458      <p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.
459      </p>
460      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
461      </p>
462      <p>This Internet-Draft will expire in August 2008.</p>
463      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
464      <p>Copyright © The IETF Trust (2008). All Rights Reserved.</p>
465      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
466      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
467         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the
468         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
469         4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests.
470      </p> 
471      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
472      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
473         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
474      </p> 
475      <p>This draft incorporates those issue resolutions that were either collected in the original RFC2616 errata list (&lt;<a href="http://purl.org/NET/http-errata">http://purl.org/NET/http-errata</a>&gt;), or which were agreed upon on the mailing list between October 2006 and November 2007 (as published in "draft-lafon-rfc2616bis-03").
476      </p> 
477      <hr class="noprint">
478      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
479      <ul class="toc">
480         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
481               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
482            </ul>
483         </li>
484         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#entity.tags">Entity Tags</a></li>
485         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul class="toc">
486               <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#status.304">304 Not Modified</a></li>
487               <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#status.412">412 Precondition Failed</a></li>
488            </ul>
489         </li>
490         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#weak.and.strong.validators">Weak and Strong Validators</a></li>
491         <li class="tocline0">5.&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>
492         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
493               <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#header.etag">ETag</a></li>
494               <li class="tocline1">6.2&nbsp;&nbsp;&nbsp;<a href="#header.if-match">If-Match</a></li>
495               <li class="tocline1">6.3&nbsp;&nbsp;&nbsp;<a href="#header.if-modified-since">If-Modified-Since</a></li>
496               <li class="tocline1">6.4&nbsp;&nbsp;&nbsp;<a href="#header.if-none-match">If-None-Match</a></li>
497               <li class="tocline1">6.5&nbsp;&nbsp;&nbsp;<a href="#header.if-unmodified-since">If-Unmodified-Since</a></li>
498               <li class="tocline1">6.6&nbsp;&nbsp;&nbsp;<a href="#header.last-modified">Last-Modified</a></li>
499            </ul>
500         </li>
501         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
502         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a></li>
503         <li class="tocline0">9.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
504         <li class="tocline0">10.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
505               <li class="tocline1">10.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
506               <li class="tocline1">10.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
507            </ul>
508         </li>
509         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
510         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
511               <li class="tocline1">A.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
512            </ul>
513         </li>
514         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
515               <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
516               <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p4-conditional-00</a></li>
517               <li class="tocline1">B.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.3">Since draft-ietf-httpbis-p4-conditional-01</a></li>
518            </ul>
519         </li>
520         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
521         <li class="tocline0"><a href="#rfc.index">Index</a></li>
522      </ul>
523      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
524      <p id="rfc.section.1.p.1">This document defines HTTP/1.1 response metadata for indicating potential changes to payload content, including modification
525         time stamps and opaque entity-tags, and the HTTP conditional request mechanisms that allow preconditions to be placed on a
526         request method. Conditional GET requests allow for efficient cache updates. Other conditional request methods are used to
527         protect against overwriting or misunderstanding the state of a resource that has been changed unbeknownst to the requesting
528         client.
529      </p>
530      <p id="rfc.section.1.p.2">This document is currently disorganized in order to minimize the changes between drafts and enable reviewers to see the smaller
531         errata changes. The next draft will reorganize the sections to better reflect the content. In particular, the sections on
532         resource metadata will be discussed first and then followed by each conditional request-header, concluding with a definition
533         of precedence and the expectation of ordering strong validator checks before weak validator checks. It is likely that more
534         content from <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a> will migrate to this part, where appropriate. The current mess reflects how widely dispersed these topics and associated requirements
535         had become in <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
536      </p>
537      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
538      <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"
539         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>.
540      </p>
541      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
542      </p>
543      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="entity.tags" href="#entity.tags">Entity Tags</a></h1>
544      <p id="rfc.section.2.p.1">Entity tags are used for comparing two or more entities from the same requested resource. HTTP/1.1 uses entity tags in the
545         ETag (<a href="#header.etag" id="rfc.xref.header.etag.1" title="ETag">Section&nbsp;6.1</a>), If-Match (<a href="#header.if-match" id="rfc.xref.header.if-match.1" title="If-Match">Section&nbsp;6.2</a>), If-None-Match (<a href="#header.if-none-match" id="rfc.xref.header.if-none-match.1" title="If-None-Match">Section&nbsp;6.4</a>), and If-Range (<a href="p5-range.html#header.if-range" title="If-Range">Section 5.3</a> of <a href="#Part5" id="rfc.xref.Part5.1"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a>) header fields. The definition of how they are used and compared as cache validators is in <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>. An entity tag consists of an opaque quoted string, possibly prefixed by a weakness indicator.
546      </p>
547      <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.g.3"></span>  entity-tag = [ weak ] opaque-tag
548  weak       = "W/"
549  opaque-tag = quoted-string
550</pre><p id="rfc.section.2.p.3">A "strong entity tag" <em class="bcp14">MAY</em> be shared by two entities of a resource only if they are equivalent by octet equality.
551      </p>
552      <p id="rfc.section.2.p.4">A "weak entity tag," indicated by the "W/" prefix, <em class="bcp14">MAY</em> be shared by two entities of a resource only if the entities are equivalent and could be substituted for each other with no
553         significant change in semantics. A weak entity tag can only be used for weak comparison.
554      </p>
555      <p id="rfc.section.2.p.5">An entity tag <em class="bcp14">MUST</em> be unique across all versions of all entities associated with a particular resource. A given entity tag value <em class="bcp14">MAY</em> be used for entities obtained by requests on different URIs. The use of the same entity tag value in conjunction with entities
556         obtained by requests on different URIs does not imply the equivalence of those entities.
557      </p>
558      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
559      </h1>
560      <div id="rfc.iref.3"></div>
561      <div id="rfc.iref.s.1"></div>
562      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="status.304" href="#status.304">304 Not Modified</a></h2>
563      <p id="rfc.section.3.1.p.1">If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server <em class="bcp14">SHOULD</em> respond with this status code. The 304 response <em class="bcp14">MUST NOT</em> contain a message-body, and thus is always terminated by the first empty line after the header fields.
564      </p>
565      <p id="rfc.section.3.1.p.2">The response <em class="bcp14">MUST</em> include the following header fields:
566      </p>
567      <ul>
568         <li>Date, unless its omission is required by <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 8.3.1</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></li>
569      </ul>
570      <p id="rfc.section.3.1.p.3">If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without
571         one (as already specified by <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-14.19">Section 14.19</a>), caches will operate correctly.
572      </p>
573      <ul>
574         <li>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</li>
575         <li>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
576            variant
577         </li>
578      </ul>
579      <p id="rfc.section.3.1.p.4">If the conditional GET used a strong cache validator (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>), the response <em class="bcp14">SHOULD NOT</em> include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response <em class="bcp14">MUST NOT</em> include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
580      </p>
581      <p id="rfc.section.3.1.p.5">If a 304 response indicates an entity not currently cached, then the cache <em class="bcp14">MUST</em> disregard the response and repeat the request without the conditional.
582      </p>
583      <p id="rfc.section.3.1.p.6">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.
584      </p>
585      <div id="rfc.iref.4"></div>
586      <div id="rfc.iref.s.2"></div>
587      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.412" href="#status.412">412 Precondition Failed</a></h2>
588      <p id="rfc.section.3.2.p.1">The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This
589         response code allows the client to place preconditions on the current resource metainformation (header field data) and thus
590         prevent the requested method from being applied to a resource other than the one intended.
591      </p>
592      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="weak.and.strong.validators" href="#weak.and.strong.validators">Weak and Strong Validators</a></h1>
593      <p id="rfc.section.4.p.1">Since both origin servers and caches will compare two validators to decide if they represent the same or different entities,
594         one normally would expect that if the entity (the entity-body or any entity-headers) changes in any way, then the associated
595         validator would change as well. If this is true, then we call this validator a "strong validator."
596      </p>
597      <p id="rfc.section.4.p.2">However, there might be cases when a server prefers to change the validator only on semantically significant changes, and
598         not when insignificant aspects of the entity change. A validator that does not always change when the resource changes is
599         a "weak validator."
600      </p>
601      <p id="rfc.section.4.p.3">Entity tags are normally "strong validators," but the protocol provides a mechanism to tag an entity tag as "weak." One can
602         think of a strong validator as one that changes whenever the bits of an entity changes, while a weak value changes whenever
603         the meaning of an entity changes. Alternatively, one can think of a strong validator as part of an identifier for a specific
604         entity, while a weak validator is part of an identifier for a set of semantically equivalent entities.
605      </p>
606      <dl class="empty">
607         <dd> <b>Note:</b> One example of a strong validator is an integer that is incremented in stable storage every time an entity is changed.
608         </dd>
609         <dd>An entity's modification time, if represented with one-second resolution, could be a weak validator, since it is possible
610            that the resource might be modified twice during a single second.
611         </dd>
612         <dd>Support for weak validators is optional. However, weak validators allow for more efficient caching of equivalent objects;
613            for example, a hit counter on a site is probably good enough if it is updated every few days or weeks, and any value during
614            that period is likely "good enough" to be equivalent.
615         </dd>
616      </dl>
617      <p id="rfc.section.4.p.4">A "use" of a validator is either when a client generates a request and includes the validator in a validating header field,
618         or when a server compares two validators.
619      </p>
620      <p id="rfc.section.4.p.5">Strong validators are usable in any context. Weak validators are only usable in contexts that do not depend on exact equality
621         of an entity. For example, either kind is usable for a conditional GET of a full entity. However, only a strong validator
622         is usable for a sub-range retrieval, since otherwise the client might end up with an internally inconsistent entity.
623      </p>
624      <p id="rfc.section.4.p.6">Clients <em class="bcp14">MAY</em> issue simple (non-subrange) GET requests with either weak validators or strong validators. Clients <em class="bcp14">MUST NOT</em> use weak validators in other forms of request.
625      </p>
626      <p id="rfc.section.4.p.7">The only function that HTTP/1.1 defines on validators is comparison. There are two validator comparison functions, depending
627         on whether the comparison context allows the use of weak validators or not:
628      </p>
629      <ul>
630         <li>The strong comparison function: in order to be considered equal, both validators <em class="bcp14">MUST</em> be identical in every way, and both <em class="bcp14">MUST NOT</em> be weak.
631         </li>
632         <li>The weak comparison function: in order to be considered equal, both validators <em class="bcp14">MUST</em> be identical in every way, but either or both of them <em class="bcp14">MAY</em> be tagged as "weak" without affecting the result.
633         </li>
634      </ul>
635      <p id="rfc.section.4.p.8">An entity tag is strong unless it is explicitly tagged as weak. <a href="#entity.tags" title="Entity Tags">Section&nbsp;2</a> gives the syntax for entity tags.
636      </p>
637      <p id="rfc.section.4.p.9">A Last-Modified time, when used as a validator in a request, is implicitly weak unless it is possible to deduce that it is
638         strong, using the following rules:
639      </p>
640      <ul>
641         <li>The validator is being compared by an origin server to the actual current validator for the entity and,</li>
642         <li>That origin server reliably knows that the associated entity did not change twice during the second covered by the presented
643            validator.
644         </li>
645      </ul>
646      <p id="rfc.section.4.p.10">or </p>
647      <ul>
648         <li>The validator is about to be used by a client in an If-Modified-Since or If-Unmodified-Since header, because the client has
649            a cache entry for the associated entity, and
650         </li>
651         <li>That cache entry includes a Date value, which gives the time when the origin server sent the original response, and</li>
652         <li>The presented Last-Modified time is at least 60 seconds before the Date value.</li>
653      </ul>
654      <p id="rfc.section.4.p.11">or </p>
655      <ul>
656         <li>The validator is being compared by an intermediate cache to the validator stored in its cache entry for the entity, and</li>
657         <li>That cache entry includes a Date value, which gives the time when the origin server sent the original response, and</li>
658         <li>The presented Last-Modified time is at least 60 seconds before the Date value.</li>
659      </ul>
660      <p id="rfc.section.4.p.12">This method relies on the fact that if two different responses were sent by the origin server during the same second, but
661         both had the same Last-Modified time, then at least one of those responses would have a Date value equal to its Last-Modified
662         time. The arbitrary 60-second limit guards against the possibility that the Date and Last-Modified values are generated from
663         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.
664      </p>
665      <p id="rfc.section.4.p.13">If a client wishes to perform a sub-range retrieval on a value for which it has only a Last-Modified time and no opaque validator,
666         it <em class="bcp14">MAY</em> do this only if the Last-Modified time is strong in the sense described here.
667      </p>
668      <p id="rfc.section.4.p.14">A cache or origin server receiving a conditional request, other than a full-body GET request, <em class="bcp14">MUST</em> use the strong comparison function to evaluate the condition.
669      </p>
670      <p id="rfc.section.4.p.15">These rules allow HTTP/1.1 caches and clients to safely perform sub-range retrievals on values that have been obtained from
671         HTTP/1.0 servers.
672      </p>
673      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="rules.for.when.to.use.entity.tags.and.last-modified.dates" href="#rules.for.when.to.use.entity.tags.and.last-modified.dates">Rules for When to Use Entity Tags and Last-Modified Dates</a></h1>
674      <p id="rfc.section.5.p.1">We adopt a set of rules and recommendations for origin servers, clients, and caches regarding when various validator types
675         ought to be used, and for what purposes.
676      </p>
677      <p id="rfc.section.5.p.2">HTTP/1.1 origin servers: </p>
678      <ul>
679         <li><em class="bcp14">SHOULD</em> send an entity tag validator unless it is not feasible to generate one.
680         </li>
681         <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,
682            or if it is unfeasible to send a strong entity tag.
683         </li>
684         <li><em class="bcp14">SHOULD</em> send a Last-Modified value if it is feasible to send one, unless the risk of a breakdown in semantic transparency that could
685            result from using this date in an If-Modified-Since header would lead to serious problems.
686         </li>
687      </ul>
688      <p id="rfc.section.5.p.3">In other words, the preferred behavior for an HTTP/1.1 origin server is to send both a strong entity tag and a Last-Modified
689         value.
690      </p>
691      <p id="rfc.section.5.p.4">In order to be legal, a strong entity tag <em class="bcp14">MUST</em> change whenever the associated entity value changes in any way. A weak entity tag <em class="bcp14">SHOULD</em> change whenever the associated entity changes in a semantically significant way.
692      </p>
693      <dl class="empty">
694         <dd> <b>Note:</b> in order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value
695            for two different entities, or reusing a specific weak entity tag value for two semantically different entities. Cache entries
696            might persist for arbitrarily long periods, regardless of expiration times, so it might be inappropriate to expect that a
697            cache will never again attempt to validate an entry using a validator that it obtained at some point in the past.
698         </dd>
699      </dl>
700      <p id="rfc.section.5.p.5">HTTP/1.1 clients: </p>
701      <ul>
702         <li>If an entity tag has been provided by the origin server, <em class="bcp14">MUST</em> use that entity tag in any cache-conditional request (using If-Match or If-None-Match).
703         </li>
704         <li>If only a Last-Modified value has been provided by the origin server, <em class="bcp14">SHOULD</em> use that value in non-subrange cache-conditional requests (using If-Modified-Since).
705         </li>
706         <li>If only a Last-Modified value has been provided by an HTTP/1.0 origin server, <em class="bcp14">MAY</em> use that value in subrange cache-conditional requests (using If-Unmodified-Since:). The user agent <em class="bcp14">SHOULD</em> provide a way to disable this, in case of difficulty.
707         </li>
708         <li>If both an entity tag and a Last-Modified value have been provided by the origin server, <em class="bcp14">SHOULD</em> use both validators in cache-conditional requests. This allows both HTTP/1.0 and HTTP/1.1 caches to respond appropriately.
709         </li>
710      </ul>
711      <p id="rfc.section.5.p.6">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
712         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
713         field) as cache validators, <em class="bcp14">MUST NOT</em> return a response status of 304 (Not Modified) unless doing so is consistent with all of the conditional header fields in
714         the request.
715      </p>
716      <p id="rfc.section.5.p.7">An HTTP/1.1 caching proxy, upon receiving a conditional request that includes both a Last-Modified date and one or more entity
717         tags 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
718         fields in the request.
719      </p>
720      <dl class="empty">
721         <dd> <b>Note:</b> The general principle behind these rules is that HTTP/1.1 servers and clients should transmit as much non-redundant information
722            as is available in their responses and requests. HTTP/1.1 systems receiving this information will make the most conservative
723            assumptions about the validators they receive.
724         </dd>
725         <dd>HTTP/1.0 clients and caches will ignore entity tags. Generally, last-modified values received or used by these systems will
726            support transparent and efficient caching, and so HTTP/1.1 origin servers should provide Last-Modified values. In those rare
727            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
728            HTTP/1.1 origin servers should not provide one.
729         </dd>
730      </dl>
731      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
732      <p id="rfc.section.6.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to conditional requests.</p>
733      <p id="rfc.section.6.p.2">For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who
734         receives the entity.
735      </p>
736      <div id="rfc.iref.e.1"></div>
737      <div id="rfc.iref.h.1"></div>
738      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="header.etag" href="#header.etag">ETag</a></h2>
739      <p id="rfc.section.6.1.p.1">The ETag response-header field provides the current value of the entity tag for the requested variant. The headers used with
740         entity tags are described in Sections <a href="#header.if-match" id="rfc.xref.header.if-match.2" title="If-Match">6.2</a> and <a href="#header.if-none-match" id="rfc.xref.header.if-none-match.2" title="If-None-Match">6.4</a> of this document, and 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>. The entity tag <em class="bcp14">MAY</em> be used for comparison with other entities from the same resource (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>).
741      </p>
742      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  ETag = "ETag" ":" entity-tag
743</pre><div id="rfc.figure.u.3"></div>
744      <p>Examples:</p>  <pre class="text">   ETag: "xyzzy"
745   ETag: W/"xyzzy"
746   ETag: ""
747</pre><p id="rfc.section.6.1.p.4">The ETag response-header field value, an entity tag, provides for an "opaque" cache validator. This might allow more reliable
748         validation in situations where it is inconvenient to store modification dates, where the one-second resolution of HTTP date
749         values is not sufficient, or where the origin server wishes to avoid certain paradoxes that might arise from the use of modification
750         dates.
751      </p>
752      <p id="rfc.section.6.1.p.5">The principle behind entity tags is that only the service author knows the semantics of a resource well enough to select an
753         appropriate cache validation mechanism, and the specification of any validator comparison function more complex than byte-equality
754         would open up a can of worms. Thus, comparisons of any other headers (except Last-Modified, for compatibility with HTTP/1.0)
755         are never used for purposes of validating a cache entry.
756      </p>
757      <div id="rfc.iref.i.1"></div>
758      <div id="rfc.iref.h.2"></div>
759      <h2 id="rfc.section.6.2"><a href="#rfc.section.6.2">6.2</a>&nbsp;<a id="header.if-match" href="#header.if-match">If-Match</a></h2>
760      <p id="rfc.section.6.2.p.1">The If-Match request-header field is used with a method to make it conditional. A client that has one or more entities previously
761         obtained from the resource can verify that one of those entities is current by including a list of their associated entity
762         tags in the If-Match header field. Entity tags are defined in <a href="#entity.tags" title="Entity Tags">Section&nbsp;2</a>. The purpose of this feature is to allow efficient updates of cached information with a minimum amount of transaction overhead.
763         It is also used, on updating requests, to prevent inadvertent modification of the wrong version of a resource. As a special
764         case, the value "*" matches any current entity of the resource.
765      </p>
766      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  If-Match = "If-Match" ":" ( "*" | 1#entity-tag )
767</pre><p id="rfc.section.6.2.p.3">If any of the entity tags match the entity tag of the entity that would have been returned in the response to a similar GET
768         request (without the If-Match header) on that resource, or if "*" is given and any current entity exists for that resource,
769         then the server <em class="bcp14">MAY</em> perform the requested method as if the If-Match header field did not exist.
770      </p>
771      <p id="rfc.section.6.2.p.4">A server <em class="bcp14">MUST</em> use the strong comparison function (see <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a>) to compare the entity tags in If-Match.
772      </p>
773      <p id="rfc.section.6.2.p.5">If none of the entity tags match, or if "*" is given and no current entity exists, the server <em class="bcp14">MUST NOT</em> perform the requested method, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed) response. This behavior is most useful when the client wants to prevent an updating method,
774         such as PUT, from modifying a resource that has changed since the client last retrieved it.
775      </p>
776      <p id="rfc.section.6.2.p.6">If the request would, without the If-Match header field, result in anything other than a 2xx or 412 status, then the If-Match
777         header <em class="bcp14">MUST</em> be ignored.
778      </p>
779      <p id="rfc.section.6.2.p.7">The meaning of "If-Match: *" is that the method <em class="bcp14">SHOULD</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 15.5</a> of <a href="#Part6" id="rfc.xref.Part6.2"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">MUST NOT</em> be performed if the representation does not exist.
780      </p>
781      <p id="rfc.section.6.2.p.8">A request intended to update a resource (e.g., a PUT) <em class="bcp14">MAY</em> include an If-Match header field to signal that the request method <em class="bcp14">MUST NOT</em> be applied if the entity corresponding to the If-Match value (a single entity tag) is no longer a representation of that resource.
782         This allows the user to indicate that they do not wish the request to be successful if the resource has been changed without
783         their knowledge. Examples:
784      </p>
785      <div id="rfc.figure.u.5"></div><pre class="text">    If-Match: "xyzzy"
786    If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
787    If-Match: *
788</pre><p id="rfc.section.6.2.p.10">The result of a request having both an If-Match header field and either an If-None-Match or an If-Modified-Since header fields
789         is undefined by this specification.
790      </p>
791      <div id="rfc.iref.i.2"></div>
792      <div id="rfc.iref.h.3"></div>
793      <h2 id="rfc.section.6.3"><a href="#rfc.section.6.3">6.3</a>&nbsp;<a id="header.if-modified-since" href="#header.if-modified-since">If-Modified-Since</a></h2>
794      <p id="rfc.section.6.3.p.1">The If-Modified-Since request-header field is used with a method to make it conditional: if the requested variant has not
795         been modified since the time specified in this field, an entity will not be returned from the server; instead, a 304 (Not
796         Modified) response will be returned without any message-body.
797      </p>
798      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  If-Modified-Since = "If-Modified-Since" ":" HTTP-date
799</pre><p id="rfc.section.6.3.p.3">An example of the field is:</p>
800      <div id="rfc.figure.u.7"></div><pre class="text">    If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
801</pre><p id="rfc.section.6.3.p.5">A GET method with an If-Modified-Since header and no Range header requests that the identified entity be transferred only
802         if it has been modified since the date given by the If-Modified-Since header. The algorithm for determining this includes
803         the following cases:
804      </p>
805      <ol>
806         <li>If the request would normally result in anything other than a 200 (OK) status, or if the passed If-Modified-Since date is
807            invalid, the response is exactly the same as for a normal GET. A date which is later than the server's current time is invalid.
808         </li>
809         <li>If the variant has been modified since the If-Modified-Since date, the response is exactly the same as for a normal GET.</li>
810         <li>If the variant has not been modified since a valid If-Modified-Since date, the server <em class="bcp14">SHOULD</em> return a 304 (Not Modified) response.
811         </li>
812      </ol>
813      <p id="rfc.section.6.3.p.6">The purpose of this feature is to allow efficient updates of cached information with a minimum amount of transaction overhead. </p>
814      <dl class="empty">
815         <dd> <b>Note:</b> The Range request-header field modifies the meaning of If-Modified-Since; see <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.3"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> for full details.
816         </dd>
817         <dd> <b>Note:</b> If-Modified-Since times are interpreted by the server, whose clock might not be synchronized with the client.
818         </dd>
819         <dd> <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
820            function, for deciding whether to send a 304 (Not Modified) response. To get best results when sending an If-Modified-Since
821            header field for cache validation, clients are advised to use the exact date string received in a previous Last-Modified header
822            field whenever possible.
823         </dd>
824         <dd> <b>Note:</b> If a client uses an arbitrary date in the If-Modified-Since header instead of a date taken from the Last-Modified header for
825            the same request, the client should be aware of the fact that this date is interpreted in the server's understanding of time.
826            The client should consider unsynchronized clocks and rounding problems due to the different encodings of time between the
827            client and server. This includes the possibility of race conditions if the document has changed between the time it was first
828            requested and the If-Modified-Since date of a subsequent request, and the possibility of clock-skew-related problems if the
829            If-Modified-Since date is derived from the client's clock without correction to the server's clock. Corrections for different
830            time bases between client and server are at best approximate due to network latency.
831         </dd>
832      </dl>
833      <p id="rfc.section.6.3.p.7">The result of a request having both an If-Modified-Since header field and either an If-Match or an If-Unmodified-Since header
834         fields is undefined by this specification.
835      </p>
836      <div id="rfc.iref.i.3"></div>
837      <div id="rfc.iref.h.4"></div>
838      <h2 id="rfc.section.6.4"><a href="#rfc.section.6.4">6.4</a>&nbsp;<a id="header.if-none-match" href="#header.if-none-match">If-None-Match</a></h2>
839      <p id="rfc.section.6.4.p.1">The If-None-Match request-header field is used with a method to make it conditional. A client that has one or more entities
840         previously obtained from the resource can verify that none of those entities is current by including a list of their associated
841         entity tags in the If-None-Match header field. The purpose of this feature is to allow efficient updates of cached information
842         with a minimum amount of transaction overhead. It is also used to prevent a method (e.g. PUT) from inadvertently modifying
843         an existing resource when the client believes that the resource does not exist.
844      </p>
845      <p id="rfc.section.6.4.p.2">As a special case, the value "*" matches any current entity of the resource.</p>
846      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  If-None-Match = "If-None-Match" ":" ( "*" | 1#entity-tag )
847</pre><p id="rfc.section.6.4.p.4">If any of the entity tags match the entity tag of the entity that would have been returned in the response to a similar GET
848         request (without the If-None-Match header) on that resource, or if "*" is given and any current entity exists for that resource,
849         then the server <em class="bcp14">MUST NOT</em> perform the requested method, unless required to do so because the resource's modification date fails to match that supplied
850         in an If-Modified-Since header field in the request. Instead, if the request method was GET or HEAD, the server <em class="bcp14">SHOULD</em> respond with a 304 (Not Modified) response, including the cache-related header fields (particularly ETag) of one of the entities
851         that matched. For all other request methods, the server <em class="bcp14">MUST</em> respond with a status of 412 (Precondition Failed).
852      </p>
853      <p id="rfc.section.6.4.p.5">See <a href="#weak.and.strong.validators" title="Weak and Strong Validators">Section&nbsp;4</a> for rules on how to determine if two entities tags match. The weak comparison function can only be used with GET or HEAD requests.
854      </p>
855      <p id="rfc.section.6.4.p.6">If none of the entity tags match, then the server <em class="bcp14">MAY</em> perform the requested method as if the If-None-Match header field did not exist, but <em class="bcp14">MUST</em> also ignore any If-Modified-Since header field(s) in the request. That is, if no entity tags match, then the server <em class="bcp14">MUST NOT</em> return a 304 (Not Modified) response.
856      </p>
857      <p id="rfc.section.6.4.p.7">If the request would, without the If-None-Match header field, result in anything other than a 2xx or 304 status, then the
858         If-None-Match header <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;5</a> for a discussion of server behavior when both If-Modified-Since and If-None-Match appear in the same request.)
859      </p>
860      <p id="rfc.section.6.4.p.8">The meaning of "If-None-Match: *" is that the method <em class="bcp14">MUST NOT</em> be performed if the representation selected by the origin server (or by a cache, possibly using the Vary mechanism, see <a href="p6-cache.html#header.vary" title="Vary">Section 15.5</a> of <a href="#Part6" id="rfc.xref.Part6.3"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) exists, and <em class="bcp14">SHOULD</em> be performed if the representation does not exist. This feature is intended to be useful in preventing races between PUT operations.
861      </p>
862      <p id="rfc.section.6.4.p.9">Examples:</p>
863      <div id="rfc.figure.u.9"></div><pre class="text">    If-None-Match: "xyzzy"
864    If-None-Match: W/"xyzzy"
865    If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
866    If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
867    If-None-Match: *
868</pre><p id="rfc.section.6.4.p.11">The result of a request having both an If-None-Match header field and either an If-Match or an If-Unmodified-Since header
869         fields is undefined by this specification.
870      </p>
871      <div id="rfc.iref.i.4"></div>
872      <div id="rfc.iref.h.5"></div>
873      <h2 id="rfc.section.6.5"><a href="#rfc.section.6.5">6.5</a>&nbsp;<a id="header.if-unmodified-since" href="#header.if-unmodified-since">If-Unmodified-Since</a></h2>
874      <p id="rfc.section.6.5.p.1">The If-Unmodified-Since request-header field is used with a method to make it conditional. If the requested resource has not
875         been modified since the time specified in this field, the server <em class="bcp14">SHOULD</em> perform the requested operation as if the If-Unmodified-Since header were not present.
876      </p>
877      <p id="rfc.section.6.5.p.2">If the requested variant has been modified since the specified time, the server <em class="bcp14">MUST NOT</em> perform the requested operation, and <em class="bcp14">MUST</em> return a 412 (Precondition Failed).
878      </p>
879      <div id="rfc.figure.u.10"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  If-Unmodified-Since = "If-Unmodified-Since" ":" HTTP-date
880</pre><p id="rfc.section.6.5.p.4">An example of the field is:</p>
881      <div id="rfc.figure.u.11"></div><pre class="text">    If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
882</pre><p id="rfc.section.6.5.p.6">If the request normally (i.e., without the If-Unmodified-Since header) would result in anything other than a 2xx or 412 status,
883         the If-Unmodified-Since header <em class="bcp14">SHOULD</em> be ignored.
884      </p>
885      <p id="rfc.section.6.5.p.7">If the specified date is invalid, the header is ignored.</p>
886      <p id="rfc.section.6.5.p.8">The result of a request having both an If-Unmodified-Since header field and either an If-None-Match or an If-Modified-Since
887         header fields is undefined by this specification.
888      </p>
889      <div id="rfc.iref.l.1"></div>
890      <div id="rfc.iref.h.6"></div>
891      <h2 id="rfc.section.6.6"><a href="#rfc.section.6.6">6.6</a>&nbsp;<a id="header.last-modified" href="#header.last-modified">Last-Modified</a></h2>
892      <p id="rfc.section.6.6.p.1">The Last-Modified entity-header field indicates the date and time at which the origin server believes the variant was last
893         modified.
894      </p>
895      <div id="rfc.figure.u.12"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  Last-Modified  = "Last-Modified" ":" HTTP-date
896</pre><p id="rfc.section.6.6.p.3">An example of its use is</p>
897      <div id="rfc.figure.u.13"></div><pre class="text">    Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
898</pre><p id="rfc.section.6.6.p.5">The exact meaning of this header field depends on the implementation of the origin server and the nature of the original resource.
899         For files, it may be just the file system last-modified time. For entities with dynamically included parts, it may be the
900         most recent of the set of last-modify times for its component parts. For database gateways, it may be the last-update time
901         stamp of the record. For virtual objects, it may be the last time the internal state changed.
902      </p>
903      <p id="rfc.section.6.6.p.6">An origin server <em class="bcp14">MUST NOT</em> send a Last-Modified date which is later than the server's time of message origination. In such cases, where the resource's
904         last modification would indicate some time in the future, the server <em class="bcp14">MUST</em> replace that date with the message origination date.
905      </p>
906      <p id="rfc.section.6.6.p.7">An origin server <em class="bcp14">SHOULD</em> obtain the Last-Modified value of the entity as close as possible to the time that it generates the Date value of its response.
907         This allows a recipient to make an accurate assessment of the entity's modification time, especially if the entity changes
908         near the time that the response is generated.
909      </p>
910      <p id="rfc.section.6.6.p.8">HTTP/1.1 servers <em class="bcp14">SHOULD</em> send Last-Modified whenever feasible.
911      </p>
912      <p id="rfc.section.6.6.p.9">The Last-Modified entity-header field value is often used as a cache validator. In simple terms, a cache entry is considered
913         to be valid if the entity has not been modified since the Last-Modified value.
914      </p>
915      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
916      <p id="rfc.section.7.p.1">TBD.</p>
917      <h1 id="rfc.section.8"><a href="#rfc.section.8">8.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
918      <p id="rfc.section.8.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
919      </p>
920      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
921      <h1 id="rfc.references"><a id="rfc.section.10" href="#rfc.section.10">10.</a> References
922      </h1>
923      <h2 id="rfc.references.1"><a href="#rfc.section.10.1" id="rfc.section.10.1">10.1</a> Normative References
924      </h2>
925      <table summary="Normative References">       
926         <tr>
927            <td class="reference"><b id="Part1">[Part1]</b></td>
928            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), February&nbsp;2008.
929            </td>
930         </tr>
931         <tr>
932            <td class="reference"><b id="Part5">[Part5]</b></td>
933            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), February&nbsp;2008.
934            </td>
935         </tr>
936         <tr>
937            <td class="reference"><b id="Part6">[Part6]</b></td>
938            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), February&nbsp;2008.
939            </td>
940         </tr>
941         <tr>
942            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
943            <td class="top"><a title="Harvard University">Bradner, S.</a>, “<a href="http://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.
944            </td>
945         </tr>
946      </table>
947      <h2 id="rfc.references.2"><a href="#rfc.section.10.2" id="rfc.section.10.2">10.2</a> Informative References
948      </h2>
949      <table summary="Informative References">   
950         <tr>
951            <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
952            <td class="top"><a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
953            </td>
954         </tr>
955         <tr>
956            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
957            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
958            </td>
959         </tr>
960      </table>
961      <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
962      <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
963            (editor)
964            <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Day Software</span><span class="adr"><span class="street-address vcardline">23 Corporate Plaza DR, Suite 280</span><span class="vcardline"><span class="locality">Newport Beach</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92660</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel">Phone: <a href="tel:+1-949-706-5300"><span class="value">+1-949-706-5300</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1-949-706-5305"><span class="value">+1-949-706-5305</span></a></span><span class="vcardline">EMail: <a><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
965      <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">One Laptop per Child</span><span class="adr"><span class="street-address vcardline">21 Oak Knoll Road</span><span class="vcardline"><span class="locality">Carlisle</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">01741</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
966      <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Hewlett-Packard Company</span><span class="adr"><span class="street-address vcardline">HP Labs, Large Scale Systems Group</span><span class="street-address vcardline">1501 Page Mill Road, MS 1177</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">94304</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">JeffMogul@acm.org</span></a></span></address>
967      <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">henrikn@microsoft.com</span></a></span></address>
968      <address class="vcard"><span class="vcardline"><span class="fn">Larry Masinter</span><span class="n hidden"><span class="family-name">Masinter</span><span class="given-name">Larry</span></span></span><span class="org vcardline">Adobe Systems, Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">LMM@acm.org</span></a></span><span class="vcardline">URI: <a href="http://larry.masinter.net/" class="url">http://larry.masinter.net/</a></span></address>
969      <address class="vcard"><span class="vcardline"><span class="fn">Paul J. Leach</span><span class="n hidden"><span class="family-name">Leach</span><span class="given-name">Paul J.</span></span></span><span class="org vcardline">Microsoft Corporation</span><span class="adr"><span class="street-address vcardline">1 Microsoft Way</span><span class="vcardline"><span class="locality">Redmond</span>, <span class="region">WA</span>&nbsp;<span class="postal-code">98052</span></span></span><span class="vcardline">EMail: <a><span class="email">paulle@microsoft.com</span></a></span></address>
970      <address class="vcard"><span class="vcardline"><span class="fn">Tim Berners-Lee</span><span class="n hidden"><span class="family-name">Berners-Lee</span><span class="given-name">Tim</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Computer Science and Artificial Intelligence Laboratory</span><span class="street-address vcardline">The Stata Center, Building 32</span><span class="street-address vcardline">32 Vassar Street</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a><span class="email">timbl@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.w3.org/People/Berners-Lee/" class="url">http://www.w3.org/People/Berners-Lee/</a></span></address>
971      <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
972            (editor)
973            <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">EMail: <a><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
974      <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
975            (editor)
976            <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">EMail: <a><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
977      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
978      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
979      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
980      </h1>
981      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
982      </h2>
983      <p id="rfc.section.B.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>.
984      </p>
985      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p4-conditional-00
986      </h2>
987      <p id="rfc.section.B.2.p.1">Closed issues: </p>
988      <ul>
989         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
990         </li>
991      </ul>
992      <p id="rfc.section.B.2.p.2">Other changes: </p>
993      <ul>
994         <li>Move definitions of 304 and 412 condition codes from Part2.</li>
995      </ul>
996      <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a>&nbsp;Since draft-ietf-httpbis-p4-conditional-01
997      </h2>
998      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
999      <p>Copyright © The IETF Trust (2008).</p>
1000      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
1001         authors retain all their rights.
1002      </p>
1003      <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
1004         HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
1005         DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
1006         WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
1007      </p>
1008      <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
1009      <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
1010         be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
1011         license under such rights might or might not be available; nor does it represent that it has made any independent effort to
1012         identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
1013         BCP 79.
1014      </p>
1015      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
1016         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
1017         of this specification can be obtained from the IETF on-line IPR repository at &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
1018      </p>
1019      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
1020         rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
1021         at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
1022      </p>
1023      <h1>Acknowledgement</h1>
1024      <p>Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).</p>
1025      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1026      <p class="noprint"><a href="#rfc.index.3">3</a> <a href="#rfc.index.4">4</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> 
1027      </p>
1028      <div class="print2col">
1029         <ul class="ind">
1030            <li class="indline0"><a id="rfc.index.3" href="#rfc.index.3"><b>3</b></a><ul class="ind">
1031                  <li class="indline1">304 Not Modified (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.3"><b>3.1</b></a></li>
1032               </ul>
1033            </li>
1034            <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
1035                  <li class="indline1">412 Precondition Failed (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.4"><b>3.2</b></a></li>
1036               </ul>
1037            </li>
1038            <li class="indline0"><a id="rfc.index.E" href="#rfc.index.E"><b>E</b></a><ul class="ind">
1039                  <li class="indline1">ETag header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.etag.1">2</a>, <a class="iref" href="#rfc.iref.e.1"><b>6.1</b></a></li>
1040               </ul>
1041            </li>
1042            <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
1043                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
1044                     <ul class="ind">
1045                        <li class="indline1"><tt>entity-tag</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li>
1046                        <li class="indline1"><tt>ETag</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>6.1</b></a></li>
1047                        <li class="indline1"><tt>If-Match</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>6.2</b></a></li>
1048                        <li class="indline1"><tt>If-Modified-Since</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>6.3</b></a></li>
1049                        <li class="indline1"><tt>If-None-Match</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.7"><b>6.4</b></a></li>
1050                        <li class="indline1"><tt>If-Unmodified-Since</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.8"><b>6.5</b></a></li>
1051                        <li class="indline1"><tt>Last-Modified</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.9"><b>6.6</b></a></li>
1052                        <li class="indline1"><tt>opaque-tag</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>2</b></a></li>
1053                        <li class="indline1"><tt>weak</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li>
1054                     </ul>
1055                  </li>
1056               </ul>
1057            </li>
1058            <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
1059                  <li class="indline1">Headers&nbsp;&nbsp;
1060                     <ul class="ind">
1061                        <li class="indline1">ETag&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.etag.1">2</a>, <a class="iref" href="#rfc.iref.h.1"><b>6.1</b></a></li>
1062                        <li class="indline1">If-Match&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-match.1">2</a>, <a class="iref" href="#rfc.xref.header.if-match.2">6.1</a>, <a class="iref" href="#rfc.iref.h.2"><b>6.2</b></a></li>
1063                        <li class="indline1">If-Modified-Since&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.3"><b>6.3</b></a></li>
1064                        <li class="indline1">If-None-Match&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc.xref.header.if-none-match.2">6.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>6.4</b></a></li>
1065                        <li class="indline1">If-Unmodified-Since&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.5"><b>6.5</b></a></li>
1066                        <li class="indline1">Last-Modified&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.6"><b>6.6</b></a></li>
1067                     </ul>
1068                  </li>
1069               </ul>
1070            </li>
1071            <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
1072                  <li class="indline1">If-Match header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-match.1">2</a>, <a class="iref" href="#rfc.xref.header.if-match.2">6.1</a>, <a class="iref" href="#rfc.iref.i.1"><b>6.2</b></a></li>
1073                  <li class="indline1">If-Modified-Since header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.2"><b>6.3</b></a></li>
1074                  <li class="indline1">If-None-Match header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.if-none-match.1">2</a>, <a class="iref" href="#rfc.xref.header.if-none-match.2">6.1</a>, <a class="iref" href="#rfc.iref.i.3"><b>6.4</b></a></li>
1075                  <li class="indline1">If-Unmodified-Since header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.i.4"><b>6.5</b></a></li>
1076               </ul>
1077            </li>
1078            <li class="indline0"><a id="rfc.index.L" href="#rfc.index.L"><b>L</b></a><ul class="ind">
1079                  <li class="indline1">Last-Modified header&nbsp;&nbsp;<a class="iref" href="#rfc.iref.l.1"><b>6.6</b></a></li>
1080               </ul>
1081            </li>
1082            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
1083                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">3.1</a>, <a class="iref" href="#rfc.xref.Part1.2">8</a>, <a class="iref" href="#Part1"><b>10.1</b></a><ul class="ind">
1084                        <li class="indline1"><em>Section 8.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">3.1</a></li>
1085                     </ul>
1086                  </li>
1087                  <li class="indline1"><em>Part5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.2">6.1</a>, <a class="iref" href="#rfc.xref.Part5.3">6.3</a>, <a class="iref" href="#Part5"><b>10.1</b></a><ul class="ind">
1088                        <li class="indline1"><em>Section 5.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.1">2</a>, <a class="iref" href="#rfc.xref.Part5.2">6.1</a></li>
1089                        <li class="indline1"><em>Section 5.4</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part5.3">6.3</a></li>
1090                     </ul>
1091                  </li>
1092                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">1</a>, <a class="iref" href="#rfc.xref.Part6.2">6.2</a>, <a class="iref" href="#rfc.xref.Part6.3">6.4</a>, <a class="iref" href="#Part6"><b>10.1</b></a><ul class="ind">
1093                        <li class="indline1"><em>Section 15.5</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.2">6.2</a>, <a class="iref" href="#rfc.xref.Part6.3">6.4</a></li>
1094                     </ul>
1095                  </li>
1096               </ul>
1097            </li>
1098            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
1099                  <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">3.1</a>, <a class="iref" href="#RFC2068"><b>10.2</b></a><ul class="ind">
1100                        <li class="indline1"><em>Section 14.19</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">3.1</a></li>
1101                     </ul>
1102                  </li>
1103                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>10.1</b></a></li>
1104                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>10.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>
1105               </ul>
1106            </li>
1107            <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
1108                  <li class="indline1">Status Codes&nbsp;&nbsp;
1109                     <ul class="ind">
1110                        <li class="indline1">304 Not Modified&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a></li>
1111                        <li class="indline1">412 Precondition Failed&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a></li>
1112                     </ul>
1113                  </li>
1114               </ul>
1115            </li>
1116         </ul>
1117      </div>
1118   </body>
1119</html>
Note: See TracBrowser for help on using the repository browser.