Context Navigation

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

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

Note: See TracBrowser for help on using the repository browser.

Download in other formats: