source: draft-ietf-httpbis/01/p4-conditional.html @ 1391

Last change on this file since 1391 was 1099, checked in by julian.reschke@…, 9 years ago

bump up document dates, update to latest version of rfc2629.xslt

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