source: draft-ietf-httpbis/latest/p4-conditional.xml @ 2354

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

Allow an origin server to respond with a success status if the precondition is on a state change that already succeeded; also, make the description of If-Unmodified-Since have the same conditions as If-Match; addresses #455

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 70.7 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "August">
16  <!ENTITY ID-YEAR "2013">
17  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
18  <!ENTITY architecture               "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
19  <!ENTITY conformance                "<xref target='Part1' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY notation                   "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY abnf-extension             "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY acks                       "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY whitespace                 "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY field-components           "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY header-date                "<xref target='Part2' x:rel='#header.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY safe-methods               "<xref target='Part2' x:rel='#safe.methods' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY representation             "<xref target='Part2' x:rel='#representations' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY semantics                  "<xref target='Part2' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31  <!ENTITY freshening-responses       "<xref target='Part6' x:rel='#freshening.responses' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
32  <!ENTITY header-accept-encoding     "<xref target='Part2' x:rel='#header.accept-encoding' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
33  <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
34  <!ENTITY header-range               "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
35  <!ENTITY header-vary                "<xref target='Part2' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
36  <!ENTITY http-date                  "<xref target='Part2' x:rel='#http.date' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
37  <!ENTITY transfer-codings           "<xref target='Part1' x:rel='#transfer.codings' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
38  <!ENTITY content-negotiation        "<xref target='Part2' x:rel='#content.negotiation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
39]>
40<?rfc toc="yes" ?>
41<?rfc symrefs="yes" ?>
42<?rfc sortrefs="yes" ?>
43<?rfc compact="yes"?>
44<?rfc subcompact="no" ?>
45<?rfc linkmailto="no" ?>
46<?rfc editing="no" ?>
47<?rfc comments="yes"?>
48<?rfc inline="yes"?>
49<?rfc rfcedstyle="yes"?>
50<?rfc-ext allow-markup-in-artwork="yes" ?>
51<?rfc-ext include-references-in-index="yes" ?>
52<rfc obsoletes="2616" category="std" x:maturity-level="proposed"
53     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"
54     xmlns:x='http://purl.org/net/xml2rfc/ext'>
55<x:link rel="prev" basename="p2-semantics"/>
56<x:link rel="next" basename="p5-range"/>
57<x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
58<front>
59
60  <title abbrev="HTTP/1.1 Conditional Requests">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title>
61
62  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
63    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
64    <address>
65      <postal>
66        <street>345 Park Ave</street>
67        <city>San Jose</city>
68        <region>CA</region>
69        <code>95110</code>
70        <country>USA</country>
71      </postal>
72      <email>fielding@gbiv.com</email>
73      <uri>http://roy.gbiv.com/</uri>
74    </address>
75  </author>
76
77  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
78    <organization abbrev="greenbytes">greenbytes GmbH</organization>
79    <address>
80      <postal>
81        <street>Hafenweg 16</street>
82        <city>Muenster</city><region>NW</region><code>48155</code>
83        <country>Germany</country>
84      </postal>
85      <email>julian.reschke@greenbytes.de</email>
86      <uri>http://greenbytes.de/tech/webdav/</uri>
87    </address>
88  </author>
89
90  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
91  <workgroup>HTTPbis Working Group</workgroup>
92
93<abstract>
94<t>
95   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
96   distributed, collaborative, hypertext information systems. This document
97   defines HTTP/1.1 conditional requests, including metadata header fields
98   for indicating state changes, request header fields for making
99   preconditions on such state, and rules for constructing the responses to a
100   conditional request when one or more preconditions evaluate to false.
101</t>
102</abstract>
103
104<note title="Editorial Note (To be removed by RFC Editor)">
105  <t>
106    Discussion of this draft takes place on the HTTPBIS working group
107    mailing list (ietf-http-wg@w3.org), which is archived at
108    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
109  </t>
110  <t>
111    The current issues list is at
112    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
113    documents (including fancy diffs) can be found at
114    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
115  </t>
116  <t>
117    The changes in this draft are summarized in <xref target="changes.since.23"/>.
118  </t>
119</note>
120</front>
121
122<middle>
123<section title="Introduction" anchor="introduction">
124<t>
125   Conditional requests are HTTP requests <xref target="Part2"/> that include
126   one or more header fields indicating a precondition to be tested before
127   applying the method semantics to the target resource.
128   This document defines the HTTP/1.1 conditional request mechanisms in terms
129   of the architecture, syntax notation, and conformance criteria defined in
130   <xref target="Part1"/>.
131</t>
132<t>
133   Conditional GET requests are the most efficient mechanism for HTTP
134   cache updates &caching;.  Conditionals can also be
135   applied to state-changing methods, such as PUT and DELETE, to prevent
136   the "lost update" problem: one client accidentally overwriting
137   the work of another client that has been acting in parallel.
138</t>
139<t><iref primary="true" item="selected representation"/>
140   Conditional request preconditions are based on the state of the target
141   resource as a whole (its current value set) or the state as observed
142   in a previously obtained representation (one value in that set).
143   A resource might have multiple current representations, each with its
144   own observable state.  The conditional request mechanisms assume that
145   the mapping of requests to a "selected representation" (&representation;)
146   will be consistent over time if the server intends to take advantage of
147   conditionals. Regardless, if the mapping is inconsistent and the server is
148   unable to select the appropriate representation, then no harm will result
149   when the precondition evaluates to false.
150</t>
151<t>
152   The conditional request preconditions defined by this specification are
153   evaluated by comparing the validators provided in the conditional request
154   header fields to the current validators for the selected representation
155   in the order defined by <xref target="precedence"/>.
156</t>
157
158<section title="Conformance and Error Handling" anchor="conformance">
159<t>
160   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
161   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
162   document are to be interpreted as described in <xref target="RFC2119"/>.
163</t>
164<t>
165   Conformance criteria and considerations regarding error handling
166   are defined in &conformance;.
167</t>
168</section>
169
170<section title="Syntax Notation" anchor="notation">
171<t>
172   This specification uses the Augmented Backus-Naur Form (ABNF) notation
173   of <xref target="RFC5234"/> with the list rule extension defined in
174   &notation;. <xref target="imported.abnf"/> describes rules imported from
175   other documents. <xref target="collected.abnf"/> shows the collected ABNF
176   with the list rule expanded.
177</t>
178</section>
179</section>
180
181<section title="Validators" anchor="validators">
182   <iref primary="true" item="metadata"/>
183   <iref primary="true" item="validator"/>
184<t>
185   This specification defines two forms of metadata that are commonly used
186   to observe resource state and test for preconditions: modification dates
187   (<xref target="header.last-modified"/>) and opaque entity tags
188   (<xref target="header.etag"/>).  Additional metadata that reflects resource state
189   has been defined by various extensions of HTTP, such as WebDAV
190   <xref target="RFC4918"/>, that are beyond the scope of this specification.
191   A resource metadata value is referred to as a "<x:dfn>validator</x:dfn>"
192   when it is used within a precondition.
193</t>
194
195<section title="Weak versus Strong" anchor="weak.and.strong.validators">
196   <iref primary="true" item="validator" subitem="weak"/>
197   <iref primary="true" item="validator" subitem="strong"/>
198<t>
199   Validators come in two flavors: strong or weak.  Weak validators are easy
200   to generate but are far less useful for comparisons.  Strong validators
201   are ideal for comparisons but can be very difficult (and occasionally
202   impossible) to generate efficiently.  Rather than impose that all forms
203   of resource adhere to the same strength of validator, HTTP exposes the
204   type of validator in use and imposes restrictions on when weak validators
205   can be used as preconditions.
206</t>
207<t>
208   A "strong validator" is representation metadata that changes value whenever
209   a change occurs to the representation data that would be observable in the
210   payload body of a <x:ref>200 (OK)</x:ref> response to GET.
211</t>
212<t>  
213   A strong validator might change for other reasons, such as when a
214   semantically significant part of the representation metadata is changed
215   (e.g., <x:ref>Content-Type</x:ref>), but it is in the best interests of the
216   origin server to only change the value when it is necessary to invalidate
217   the stored responses held by remote caches and authoring tools. A strong
218   validator is unique across all representations of a given resource, such
219   that no two representations of that resource can share the same validator
220   unless their representation data is identical.
221</t>
222<t>
223   Cache entries might persist for arbitrarily long periods, regardless
224   of expiration times.  Thus, a cache might attempt to validate an
225   entry using a validator that it obtained in the distant past.
226   A strong validator is unique across all versions of all
227   representations associated with a particular resource over time.
228   However, there is no implication of uniqueness across representations
229   of different resources (i.e., the same strong validator might be
230   in use for representations of multiple resources at the same time
231   and does not imply that those representations are equivalent).
232</t>
233<t>
234   There are a variety of strong validators used in practice.  The best are
235   based on strict revision control, wherein each change to a representation
236   always results in a unique node name and revision identifier being assigned
237   before the representation is made accessible to GET.  A collision-resistant hash
238   function applied to the representation data is also sufficient if the data
239   is available prior to the response header fields being sent and the digest
240   does not need to be recalculated every time a validation request is
241   received.  However, if a resource has distinct representations that differ
242   only in their metadata, such as might occur with content negotiation over
243   media types that happen to share the same data format, then the origin
244   server &SHOULD; incorporate additional information in the validator to
245   distinguish those representations.
246</t>
247<t>
248   In contrast, a "weak validator" is representation metadata that
249   might not change for every change to the representation data.  This
250   weakness might be due to limitations in how the value is calculated, such
251   as clock resolution or an inability to ensure uniqueness for all possible
252   representations of the resource, or due to a desire by the resource owner
253   to group representations by some self-determined set of equivalency
254   rather than unique sequences of data.  An origin server &SHOULD; change a
255   weak entity-tag whenever it considers prior representations to be
256   unacceptable as a substitute for the current representation. In other words,
257   a weak entity-tag ought to change whenever the origin server wants caches to
258   invalidate old responses.
259</t>
260<t>
261   For example, the representation of a weather report that changes in
262   content every second, based on dynamic measurements, might be grouped
263   into sets of equivalent representations (from the origin server's
264   perspective) with the same weak validator in order to allow cached
265   representations to be valid for a reasonable period of time (perhaps
266   adjusted dynamically based on server load or weather quality).
267   Likewise, a representation's modification time, if defined with only
268   one-second resolution, might be a weak validator if it is possible
269   for the representation to be modified twice during a single second and
270   retrieved between those modifications.
271</t>
272<t>
273   Likewise, a validator is weak if it is shared by two or more
274   representations of a given resource at the same time, unless those
275   representations have identical representation data. For example, if the
276   origin server sends the same validator for a representation with a gzip
277   content coding applied as it does for a representation with no content
278   coding, then that validator is weak. However, two simultaneous
279   representations might share the same strong validator if they differ only
280   in the representation metadata, such as when two different media types are
281   available for the same representation data.
282</t>
283<t>
284   A "use" of a validator occurs when either a client generates a request
285   and includes the validator in a precondition or when a server
286   compares two validators.
287   Weak validators are only usable in contexts that do not depend on exact
288   equality of the representation data.
289   Strong validators are usable and preferred for all conditional requests,
290   including cache validation, partial content ranges, and "lost update"
291   avoidance.
292</t>
293</section>
294
295<section title="Last-Modified" anchor="header.last-modified">
296  <iref primary="true" item="Last-Modified header field" x:for-anchor=""/>
297  <x:anchor-alias value="Last-Modified"/>
298<t>
299   The "Last-Modified" header field in a response provides a timestamp
300   indicating the date and time at which the origin server believes the
301   selected representation was last modified, as determined at the conclusion
302   of handling the request.
303</t>
304<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Last-Modified"/>
305  <x:ref>Last-Modified</x:ref> = <x:ref>HTTP-date</x:ref>
306</artwork></figure>
307<t>
308   An example of its use is
309</t>
310<figure><artwork type="example">
311  Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
312</artwork></figure>
313
314<section title="Generation" anchor="lastmod.generation">
315<t>
316   Origin servers &SHOULD; send Last-Modified for any selected
317   representation for which a last modification date can be reasonably
318   and consistently determined, since its use in conditional requests
319   and evaluating cache freshness (&caching;) results in a substantial
320   reduction of HTTP traffic on the Internet and can be a significant
321   factor in improving service scalability and reliability.
322</t>
323<t>
324   A representation is typically the sum of many parts behind the
325   resource interface.  The last-modified time would usually be
326   the most recent time that any of those parts were changed.
327   How that value is determined for any given resource is an
328   implementation detail beyond the scope of this specification.
329   What matters to HTTP is how recipients of the Last-Modified
330   header field can use its value to make conditional requests
331   and test the validity of locally cached responses.
332</t>
333<t>
334   An origin server &SHOULD; obtain the Last-Modified value of the
335   representation as close as possible to the time that it generates the
336   <x:ref>Date</x:ref> field value for its response. This allows a recipient to
337   make an accurate assessment of the representation's modification time,
338   especially if the representation changes near the time that the
339   response is generated.
340</t>
341<t>
342   An origin server with a clock &MUST-NOT; send a Last-Modified date
343   that is later than the server's time of message origination (<x:ref>Date</x:ref>).
344   If the last modification time is derived from implementation-specific
345   metadata that evaluates to some time in the future, according to the
346   origin server's clock, then the origin server &MUST; replace that
347   value with the message origination date. This prevents a future
348   modification date from having an adverse impact on cache validation.
349</t>
350<t>
351   An origin server without a clock &MUST-NOT; assign Last-Modified
352   values to a response unless these values were associated
353   with the resource by some other system or user with a reliable clock.
354</t>
355</section>
356
357<section title="Comparison" anchor="lastmod.comparison">
358<t>
359   A Last-Modified time, when used as a validator in a request, is
360   implicitly weak unless it is possible to deduce that it is strong,
361   using the following rules:
362  <list style="symbols">
363     <t>The validator is being compared by an origin server to the
364        actual current validator for the representation and,</t>
365     <t>That origin server reliably knows that the associated representation did
366        not change twice during the second covered by the presented
367        validator.</t>
368  </list>
369</t>
370<t>
371   or
372  <list style="symbols">
373     <t>The validator is about to be used by a client in an <x:ref>If-Modified-Since</x:ref>,
374        <x:ref>If-Unmodified-Since</x:ref> header field, because the client has
375        a cache entry, or <x:ref>If-Range</x:ref> for the associated
376        representation, and</t>
377     <t>That cache entry includes a <x:ref>Date</x:ref> value, which gives the
378        time when the origin server sent the original response, and</t>
379     <t>The presented Last-Modified time is at least 60 seconds before
380        the Date value.</t>
381  </list>
382</t>
383<t>
384   or
385  <list style="symbols">
386     <t>The validator is being compared by an intermediate cache to the
387        validator stored in its cache entry for the representation, and</t>
388     <t>That cache entry includes a <x:ref>Date</x:ref> value, which gives the
389        time when the origin server sent the original response, and</t>
390     <t>The presented Last-Modified time is at least 60 seconds before
391        the Date value.</t>
392  </list>
393</t>
394<t>
395   This method relies on the fact that if two different responses were
396   sent by the origin server during the same second, but both had the
397   same Last-Modified time, then at least one of those responses would
398   have a <x:ref>Date</x:ref> value equal to its Last-Modified time. The
399   arbitrary 60-second limit guards against the possibility that the Date and
400   Last-Modified values are generated from different clocks, or at somewhat
401   different times during the preparation of the response. An
402   implementation &MAY; use a value larger than 60 seconds, if it is
403   believed that 60 seconds is too short.
404</t>
405</section>
406</section>
407
408<section title="ETag" anchor="header.etag">
409  <iref primary="true" item="ETag header field" x:for-anchor=""/>
410  <x:anchor-alias value="ETag"/>
411  <x:anchor-alias value="entity-tag"/>
412  <x:anchor-alias value="opaque-tag"/>
413  <x:anchor-alias value="weak"/>
414  <x:anchor-alias value="etagc"/>
415<t>
416   The "ETag" header field in a response provides the current entity-tag for
417   the selected representation, as determined at the conclusion of handling
418   the request.
419   An entity-tag is an opaque validator for differentiating between
420   multiple representations of the same resource, regardless of whether
421   those multiple representations are due to resource state changes over
422   time, content negotiation resulting in multiple representations being
423   valid at the same time, or both. An entity-tag consists of an opaque
424   quoted string, possibly prefixed by a weakness indicator.
425</t>
426<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="ETag"/><iref primary="true" item="Grammar" subitem="entity-tag"/><iref primary="true" item="Grammar" subitem="weak"/><iref primary="true" item="Grammar" subitem="opaque-tag"/><iref primary="true" item="Grammar" subitem="etagc"/>
427  <x:ref>ETag</x:ref>       = <x:ref>entity-tag</x:ref>
428
429  <x:ref>entity-tag</x:ref> = [ <x:ref>weak</x:ref> ] <x:ref>opaque-tag</x:ref>
430  <x:ref>weak</x:ref>       = <x:abnf-char-sequence>"W/"</x:abnf-char-sequence> ; "W/", case-sensitive
431  <x:ref>opaque-tag</x:ref> = <x:ref>DQUOTE</x:ref> *<x:ref>etagc</x:ref> <x:ref>DQUOTE</x:ref>
432  <x:ref>etagc</x:ref>      = %x21 / %x23-7E / <x:ref>obs-text</x:ref>
433             ; <x:ref>VCHAR</x:ref> except double quotes, plus obs-text
434</artwork></figure>
435<x:note>
436  <t>
437    &Note; Previously, opaque-tag was defined to be a quoted-string
438    (<xref target="RFC2616" x:fmt="," x:sec="3.11"/>), thus some recipients
439    might perform backslash unescaping. Servers therefore ought to avoid
440    backslash characters in entity tags.
441  </t>
442</x:note>
443<t>
444   An entity-tag can be more reliable for validation than a modification
445   date in situations where it is inconvenient to store modification
446   dates, where the one-second resolution of HTTP date values is not
447   sufficient, or where modification dates are not consistently maintained.
448</t>
449<figure><preamble>
450  Examples:
451</preamble>
452<artwork type="example">
453  ETag: "xyzzy"
454  ETag: W/"xyzzy"
455  ETag: ""
456</artwork></figure>
457<t>
458   An entity-tag can be either a weak or strong validator, with
459   strong being the default.  If an origin server provides an entity-tag
460   for a representation and the generation of that entity-tag does not satisfy
461   all of the characteristics of a strong validator
462   (<xref target="weak.and.strong.validators"/>), then the origin server
463   &MUST; mark the entity-tag as weak by prefixing its opaque value
464   with "W/" (case-sensitive).
465</t>
466
467<section title="Generation" anchor="entity.tag.generation">
468<t>
469   The principle behind entity-tags is that only the service author
470   knows the implementation of a resource well enough to select the
471   most accurate and efficient validation mechanism for that resource,
472   and that any such mechanism can be mapped to a simple sequence of
473   octets for easy comparison.  Since the value is opaque, there is no
474   need for the client to be aware of how each entity-tag is constructed.
475</t>
476<t>
477   For example, a resource that has implementation-specific versioning
478   applied to all changes might use an internal revision number, perhaps
479   combined with a variance identifier for content negotiation, to
480   accurately differentiate between representations.
481   Other implementations might use a collision-resistant hash of
482   representation content,
483   a combination of various filesystem attributes, or a modification
484   timestamp that has sub-second resolution.
485</t>
486<t>
487   Origin servers &SHOULD; send ETag for any selected representation
488   for which detection of changes can be reasonably and consistently
489   determined, since the entity-tag's use in conditional requests and
490   evaluating cache freshness (&caching;) can result in a substantial
491   reduction of HTTP network traffic and can be a significant factor in
492   improving service scalability and reliability.
493</t>
494</section>
495
496<section title="Comparison" anchor="entity.tag.comparison">
497  <x:anchor-alias value="validator.comparison"/>
498  <x:anchor-alias value="strong comparison"/>
499  <x:anchor-alias value="weak comparison"/>
500<t>
501   There are two entity-tag comparison functions, depending
502   on whether the comparison context allows the use of weak validators
503   or not:
504  <list style="symbols">
505     <t><x:dfn>Strong comparison</x:dfn>: two entity-tags are equivalent if both
506        are not weak and their opaque-tags match character-by-character.</t>
507     <t><x:dfn>Weak comparison</x:dfn>: two entity-tags are equivalent if their opaque-tags
508        match character-by-character, regardless of either or both
509        being tagged as "weak".</t>
510  </list>
511</t>
512<t>
513   The example below shows the results for a set of entity-tag pairs,
514   and both the weak and strong comparison function results:
515</t>
516<texttable align="left">
517  <ttcol>ETag 1</ttcol>
518  <ttcol>ETag 2</ttcol>
519  <ttcol>Strong Comparison</ttcol>
520  <ttcol>Weak Comparison</ttcol>
521
522  <c>W/"1"</c>
523  <c>W/"1"</c>
524  <c>no match</c>
525  <c>match</c>
526 
527  <c>W/"1"</c>
528  <c>W/"2"</c>
529  <c>no match</c>
530  <c>no match</c>
531
532  <c>W/"1"</c>
533  <c>"1"</c>
534  <c>no match</c>
535  <c>match</c>
536
537  <c>"1"</c>
538  <c>"1"</c>
539  <c>match</c>
540  <c>match</c>
541</texttable>
542</section>
543
544<section title="Example: Entity-tags Varying on Content-Negotiated Resources" anchor="example.entity.tag.vs.conneg">
545<t>
546   Consider a resource that is subject to content negotiation
547   (&content-negotiation;), and where the representations sent in response to
548   a GET request vary based on the <x:ref>Accept-Encoding</x:ref> request
549   header field (&header-accept-encoding;):
550</t>
551<figure><preamble>>> Request:</preamble><artwork type="message/http; msgtype=&#34;request&#34;"  x:indent-with="  ">
552GET /index HTTP/1.1
553Host: www.example.com
554Accept-Encoding: gzip
555
556</artwork></figure>
557<t>
558   In this case, the response might or might not use the gzip content coding.
559   If it does not, the response might look like:
560</t>
561<figure><preamble>>> Response:</preamble><artwork type="message/http; msgtype=&#34;response&#34;"  x:indent-with="  ">
562HTTP/1.1 200 OK
563Date: Fri, 26 Mar 2010 00:05:00 GMT
564ETag: "123-a"
565Content-Length: <x:length-of target="exbody"/>
566Vary: Accept-Encoding
567Content-Type: text/plain
568
569<x:span anchor="exbody">Hello World!
570Hello World!
571Hello World!
572Hello World!
573Hello World!
574</x:span></artwork></figure>
575<t>
576   An alternative representation that does use gzip content coding would be:
577</t>
578<figure><preamble>>> Response:</preamble><artwork type="message/http; msgtype=&#34;response&#34;"  x:indent-with="  ">
579HTTP/1.1 200 OK
580Date: Fri, 26 Mar 2010 00:05:00 GMT
581ETag: "123-b"
582Content-Length: 43
583Vary: Accept-Encoding
584Content-Type: text/plain
585Content-Encoding: gzip
586
587<spanx>...binary data...</spanx></artwork></figure>
588<x:note>
589  <t>
590    &Note; Content codings are a property of the representation,
591    so therefore an entity-tag of an encoded representation has to be distinct
592    from an unencoded representation to prevent conflicts during cache updates
593    and range requests.  In contrast, transfer codings (&transfer-codings;)
594    apply only during message transfer and do not require distinct entity-tags.
595  </t>
596</x:note>
597</section>
598</section>
599
600<section title="When to Use Entity-tags and Last-Modified Dates" anchor="when.to.use.entity.tags.and.last-modified.dates">
601<t>
602   We adopt a set of rules and recommendations for origin servers,
603   clients, and caches regarding when various validator types ought to
604   be used, and for what purposes.
605</t>
606<t>
607   In <x:ref>200 (OK)</x:ref> responses to GET or HEAD, an origin server:
608  <list style="symbols">
609     <t>&SHOULD; send an entity-tag validator unless it is not feasible to
610        generate one.</t>
611
612     <t>&MAY; send a weak entity-tag instead of a strong entity-tag, if
613        performance considerations support the use of weak entity-tags,
614        or if it is unfeasible to send a strong entity-tag.</t>
615
616     <t>&SHOULD; send a <x:ref>Last-Modified</x:ref> value if it is feasible to
617        send one.</t>
618  </list>
619</t>
620<t>
621   In other words, the preferred behavior for an origin server
622   is to send both a strong entity-tag and a <x:ref>Last-Modified</x:ref>
623   value in successful responses to a retrieval request.
624</t>
625<t>
626   A client:
627  <list style="symbols">
628     <t>&MUST; use that entity-tag in any cache-conditional request (using
629        <x:ref>If-Match</x:ref> or <x:ref>If-None-Match</x:ref>) if an
630        entity-tag has been provided by the origin server.</t>
631
632     <t>&SHOULD; use the <x:ref>Last-Modified</x:ref> value in non-subrange
633        cache-conditional requests (using <x:ref>If-Modified-Since</x:ref>)
634        if only a Last-Modified value has been provided by the origin server.</t>
635
636     <t>&MAY; use the <x:ref>Last-Modified</x:ref> value in subrange
637        cache-conditional requests (using <x:ref>If-Unmodified-Since</x:ref>)
638        if only a Last-Modified value has been provided by an HTTP/1.0 origin
639        server. The user agent &SHOULD; provide a way to disable this, in case
640        of difficulty.</t>
641
642     <t>&SHOULD; use both validators in cache-conditional requests if both an
643        entity-tag and a <x:ref>Last-Modified</x:ref> value have been provided
644        by the origin server. This allows both HTTP/1.0 and HTTP/1.1 caches to
645        respond appropriately.</t>
646  </list>
647</t>
648</section>
649</section>
650
651<section title="Precondition Header Fields" anchor="header.field.definitions">
652<t>
653   This section defines the syntax and semantics of HTTP/1.1 header fields
654   for applying preconditions on requests.
655   <xref target="precedence"/> defines when the preconditions are applied and
656   the order of evaluation when more than one precondition is present.
657</t>
658
659<section title="If-Match" anchor="header.if-match">
660  <iref primary="true" item="If-Match header field" x:for-anchor=""/>
661  <x:anchor-alias value="If-Match"/>
662<t>
663   The "If-Match" header field can be used to make a request method conditional
664   on the current existence or value of an entity-tag for one or more
665   representations of the target resource.
666</t>
667<t>
668   If-Match is generally useful for resource update requests, such as PUT
669   requests, as a means for protecting against accidental overwrites when
670   multiple clients are acting in parallel on the same resource (i.e., the
671   "lost update" problem).  An If-Match field-value of "*" places the
672   precondition on the existence of any current representation for the
673   target resource.
674</t>
675<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Match"/>
676  <x:ref>If-Match</x:ref> = "*" / 1#<x:ref>entity-tag</x:ref>
677</artwork></figure>
678<t>
679   The If-Match condition is met if and only if any of the entity-tags listed
680   in the If-Match field value match the entity-tag of the selected
681   representation using the weak comparison function (as per <xref
682   target="entity.tag.comparison"/>), or if "*" is given and any current
683   representation exists for the target resource.
684</t>
685<t>
686   If the condition is met, the server &MAY; perform the request method.
687</t>
688<t>
689   An origin server &MUST-NOT; perform the requested method if the condition
690   is not met; instead the origin server &MUST; respond with either:
691   a) the <x:ref>412 (Precondition Failed)</x:ref> status code; or,
692   b) one of the <x:ref>2xx (Successful)</x:ref> status codes if the origin
693   server has verified that a state change is being requested and the final
694   state is already reflected in the current state of the target resource
695   (i.e., the change requested by the user agent has already succeeded, but
696   the user agent might not be aware of that due to the prior response message
697   being lost or because a compatible change was made by some other user
698   agent). In the latter case, the origin server &MUST-NOT; send a
699   <x:ref>204 (No Content)</x:ref> status code unless it can verify that the
700   request is a duplicate of an immediately prior change made by the same user
701   agent.
702</t>
703<t>
704   A proxy using a cached response as the selected representation
705   &MUST-NOT; perform the requested method if the condition is not met;
706   instead, the proxy &MUST; forward the request towards the origin server.
707</t>
708<t>
709   Examples:
710</t>
711<figure><artwork type="example">
712  If-Match: "xyzzy"
713  If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
714  If-Match: *
715</artwork></figure>
716</section>
717
718<section title="If-None-Match" anchor="header.if-none-match">
719  <iref primary="true" item="If-None-Match header field" x:for-anchor=""/>
720  <x:anchor-alias value="If-None-Match"/>
721<t>
722   The "If-None-Match" header field can be used to make a request method
723   conditional on not matching any of the current entity-tag values for
724   representations of the target resource.
725</t>
726<t>
727   If-None-Match is primarily used in conditional GET requests to enable
728   efficient updates of cached information with a minimum amount of transaction
729   overhead. A client that has one or more representations previously obtained
730   from the target resource can send If-None-Match with a list of the
731   associated entity-tags in the hope of receiving a <x:ref>304 (Not
732   Modified)</x:ref> response if at least one of those representations matches
733   the selected representation.
734</t>
735<t>
736   If-None-Match can also be used with a value of "*" to prevent an unsafe
737   request method (e.g., PUT) from inadvertently modifying an existing
738   representation of the target resource when the client believes that
739   the resource does not have a current representation (&safe-methods;).
740   This is a variation on the "lost update" problem that might arise if more
741   than one client attempts to create an initial representation for the target
742   resource.
743</t>
744<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-None-Match"/>
745  <x:ref>If-None-Match</x:ref> = "*" / 1#<x:ref>entity-tag</x:ref>
746</artwork></figure>
747<t>
748   The If-None-Match condition is met if and only if none of the entity-tags
749   listed in the If-None-Match field value match the entity-tag of the selected
750   representation using the weak comparison function (as per <xref
751   target="entity.tag.comparison"/>), or if "*" is given and no current
752   representation exists for that resource.
753</t>
754<t>
755   If the condition is not met, the server &MUST-NOT; perform the requested
756   method. Instead, if the request method was GET or HEAD, the server &SHOULD;
757   respond with a <x:ref>304 (Not Modified)</x:ref> status code, including the
758   cache-related header fields (particularly <x:ref>ETag</x:ref>) of the
759   selected representation that has a matching entity-tag. For all other
760   request methods, the server &MUST; respond with a <x:ref>412 (Precondition
761   Failed)</x:ref> status code when the condition is not met.
762</t>
763<t>
764   If the condition is met, the server &MAY; perform the requested method and
765   &MUST; ignore any <x:ref>If-Modified-Since</x:ref> header field(s) in the
766   request. That is, if no entity-tags match, then the server &MUST-NOT; send
767   a <x:ref>304 (Not Modified)</x:ref> response.
768</t>
769<t>
770   Examples:
771</t>
772<figure><artwork type="example">
773  If-None-Match: "xyzzy"
774  If-None-Match: W/"xyzzy"
775  If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
776  If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
777  If-None-Match: *
778</artwork></figure>
779</section>
780
781<section title="If-Modified-Since" anchor="header.if-modified-since">
782  <iref primary="true" item="If-Modified-Since header field" x:for-anchor=""/>
783  <x:anchor-alias value="If-Modified-Since"/>
784<t>
785   The "If-Modified-Since" header field can be used with GET or HEAD to make
786   the method conditional by modification date: if the selected representation
787   has not been modified since the time specified in this field, then
788   do not perform the request method; instead, respond as detailed below.
789</t>
790<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Modified-Since"/>
791  <x:ref>If-Modified-Since</x:ref> = <x:ref>HTTP-date</x:ref>
792</artwork></figure>
793<t>
794   An example of the field is:
795</t>
796<figure><artwork type="example">
797  If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
798</artwork></figure>
799<t>
800   A GET method with an If-Modified-Since header field and no <x:ref>Range</x:ref>
801   header field requests that the selected representation be transferred only if
802   it has been modified since the date given by the If-Modified-Since
803   header field.
804   The algorithm for determining this includes the following cases:
805  <list style="numbers">
806      <t>If the request would normally result in anything other than a
807         <x:ref>200 (OK)</x:ref> status code, or if the passed If-Modified-Since date is
808         invalid, the response is exactly the same as for a normal GET.
809         A date that is later than the server's current time is
810         invalid.</t>
811
812      <t>If the selected representation has been modified since the
813         If-Modified-Since date, the response is exactly the same as for
814         a normal GET.</t>
815
816      <t>If the selected representation has not been modified since a valid
817         If-Modified-Since date, the server &SHOULD; send a
818         <x:ref>304 (Not Modified)</x:ref> response.</t>
819  </list>
820</t>
821<t>
822   The two purposes of this feature are to allow efficient updates of cached
823   information, with a minimum amount of transaction overhead, and to limit
824   the scope of a web traversal to resources that have recently changed.
825</t>
826<t>
827   When used for cache updates, a cache will typically use the value of the
828   cached message's <x:ref>Last-Modified</x:ref> field to generate the field
829   value of If-Modified-Since. This behavior is most interoperable for cases
830   where clocks are poorly synchronized or when the server has chosen to only
831   honor exact timestamp matches (due to a problem with Last-Modified dates
832   that appear to go "back in time" when the origin server's clock is
833   corrected or a representation is restored from an archived backup).
834   However, caches occasionally generate the field value based on other data,
835   such as the <x:ref>Date</x:ref> header field of the cached message or the
836   local clock time that the message was received, particularly when the
837   cached message does not contain a <x:ref>Last-Modified</x:ref> field.
838</t>
839<t>
840   When used for limiting the scope of retrieval to a recent time window, a
841   user agent will generate an If-Modified-Since field value based on either
842   its own local clock or a <x:ref>Date</x:ref> header field received from the
843   server during a past run. Origin servers that choose an exact timestamp
844   match based on the selected representation's <x:ref>Last-Modified</x:ref>
845   field will not be able to help the user agent limit its data transfers to
846   only those changed during the specified window.
847</t>
848<x:note>
849  <t>
850     &Note; If a client uses an arbitrary date in the If-Modified-Since
851     header field instead of a date taken from a <x:ref>Last-Modified</x:ref>
852     or <x:ref>Date</x:ref> header field from the origin server, the client
853     ought to be aware that its date will be interpreted according to the
854     server's understanding of time.
855  </t>
856</x:note>
857</section>
858
859<section title="If-Unmodified-Since" anchor="header.if-unmodified-since">
860  <iref primary="true" item="If-Unmodified-Since header field" x:for-anchor=""/>
861  <x:anchor-alias value="If-Unmodified-Since"/>
862<t>
863   The "If-Unmodified-Since" header field can be used to make a request
864   method conditional by modification date: if the selected representation
865   has not been modified since the time specified in this field, then the
866   condition is met.  If-Unmodified-Since is useful for resource update
867   requests, when the resource does not provide entity-tag values, as a means
868   for protecting against accidental overwrites when multiple clients are
869   acting in parallel on the same resource (i.e., the "lost update" problem).
870</t>
871<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Unmodified-Since"/>
872  <x:ref>If-Unmodified-Since</x:ref> = <x:ref>HTTP-date</x:ref>
873</artwork></figure>
874<t>
875   An example of the field is:
876</t>
877<figure><artwork type="example">
878  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
879</artwork></figure>
880<t>
881   If the condition is met, the server &MAY; perform the request method.
882</t>
883<t>
884   An origin server &MUST-NOT; perform the requested method if the condition
885   is not met; instead the origin server &MUST; respond with either:
886   a) the <x:ref>412 (Precondition Failed)</x:ref> status code; or,
887   b) one of the <x:ref>2xx (Successful)</x:ref> status codes if the origin
888   server has verified that a state change is being requested and the final
889   state is already reflected in the current state of the target resource
890   (i.e., the change requested by the user agent has already succeeded, but
891   the user agent might not be aware of that due to the prior response message
892   being lost or because a compatible change was made by some other user
893   agent). In the latter case, the origin server &MUST-NOT; send a
894   <x:ref>204 (No Content)</x:ref> status code unless it can verify that the
895   request is a duplicate of an immediately prior change made by the same user
896   agent.
897</t>
898<t>
899   A proxy using a cached response as the selected representation
900   &MUST-NOT; perform the requested method if the condition is not met;
901   instead, the proxy &MUST; forward the request towards the origin server.
902</t>
903<t>
904   A server &MUST; ignore the If-Unmodified-Since header field if the
905   received value is not a valid HTTP-date.
906</t>
907</section>
908
909<section title="If-Range" anchor="header.if-range">
910<t>
911   The "If-Range" header field provides a special conditional request
912   mechanism that is similar to <x:ref>If-Match</x:ref> and
913   <x:ref>If-Unmodified-Since</x:ref> but specific to range requests.
914   If-Range is defined in &header-if-range;.
915</t>
916</section>
917
918</section>
919
920<section title="Status Code Definitions" anchor="status.code.definitions">
921<section title="304 Not Modified" anchor="status.304">
922  <iref primary="true" item="304 Not Modified (status code)" x:for-anchor=""/>
923  <x:anchor-alias value="304"/>
924  <x:anchor-alias value="304 (Not Modified)"/>
925<t>
926   The <x:dfn>304 (Not Modified)</x:dfn> status code indicates that a
927   conditional GET or HEAD request has been
928   received and would have resulted in a <x:ref>200 (OK)</x:ref> response
929   if it were not for the fact that the condition has evaluated to false.
930   In other words, there is no need for the server to transfer a
931   representation of the target resource because the request indicates that
932   the client, which made the request conditional, already has a valid
933   representation; the server is therefore redirecting the client to make
934   use of that stored representation as if it were the payload of a
935   <x:ref>200 (OK)</x:ref> response.
936</t>
937<t>
938   The server generating a 304 response &MUST; generate any of the following
939   header fields that would have been sent in a <x:ref>200 (OK)</x:ref>
940   response to the same request:
941   <x:ref>Cache-Control</x:ref>,
942   <x:ref>Content-Location</x:ref>,
943   <x:ref>ETag</x:ref>,
944   <x:ref>Expires</x:ref>, and
945   <x:ref>Vary</x:ref>.
946</t>
947<t>
948   Since the goal of a 304 response is to minimize information transfer
949   when the recipient already has one or more cached representations,
950   a sender &SHOULD-NOT; generate representation metadata other
951   than the above listed fields unless said metadata exists for the
952   purpose of guiding cache updates (e.g., <x:ref>Last-Modified</x:ref> might
953   be useful if the response does not have an <x:ref>ETag</x:ref> field).
954</t>
955<t>
956   Requirements on a cache that receives a 304 response are defined in
957   &freshening-responses;. If the conditional request originated with an
958   outbound client, such as a user agent with its own cache sending a
959   conditional GET to a shared proxy, then the proxy &SHOULD; forward the
960   304 response to that client.
961</t>
962<t>
963   A 304 response cannot contain a message-body; it is always
964   terminated by the first empty line after the header fields.
965</t>
966</section>
967
968<section title="412 Precondition Failed" anchor="status.412">
969  <iref primary="true" item="412 Precondition Failed (status code)" x:for-anchor=""/>
970  <x:anchor-alias value="412 (Precondition Failed)"/>
971<t>
972   The <x:dfn>412 (Precondition Failed)</x:dfn> status code indicates that one
973   or more preconditions given in the request header fields evaluated to false
974   when tested on the server. This response code allows the client to place
975   preconditions on the current resource state (its current representations
976   and metadata) and thus prevent the request method from being applied if the
977   target resource is in an unexpected state.
978</t>
979</section>
980</section>
981
982<section title="Evaluation and Precedence" anchor="precedence">
983<t>
984   For each conditional request, a server &MUST; evaluate the request
985   preconditions after it has successfully performed its normal request checks
986   (i.e., just before it would perform the action associated with the request
987   method). Preconditions are ignored if the server determines that an error
988   or redirect response applies before they are evaluated. Otherwise, the
989   evaluation depends on both the method semantics and the choice of
990   conditional.
991</t>
992<t>
993   A conditional request header field that is designed specifically for cache
994   validation, which includes <x:ref>If-None-Match</x:ref> and
995   <x:ref>If-Modified-Since</x:ref> when used in a GET or HEAD request,
996   allows cached representations to be refreshed without repeatedly
997   transferring data already held by the client. Evaluating to false is thus
998   an indication that the client can continue to use its local copy of the
999   selected representation, as indicated by the server generating a
1000   <x:ref>304 (Not Modified)</x:ref> response that includes only those header
1001   fields useful for refreshing the cached representation.
1002</t>
1003<t>
1004   All other conditionals are intended to signal failure when the
1005   precondition evaluates to false. For example, an <x:ref>If-Match</x:ref>
1006   conditional sent with a state-changing method (e.g., POST, PUT, DELETE) is
1007   intended to prevent the request from taking effect on the target resource
1008   if the resource state does not match the expected state. In other words,
1009   evaluating the condition to false means that the resource has been changed
1010   by some other client, perhaps by another user attempting to edit the same
1011   resource, and thus preventing the request from being applied saves the
1012   client from overwriting some other client's work. This result is indicated
1013   by the server generating a <x:ref>412 (Precondition Failed)</x:ref>
1014   response.
1015</t>
1016<t>
1017   The conditional request header fields defined by this specification are
1018   ignored for request methods that never involve the selection or
1019   modification of a <x:ref>selected representation</x:ref> (e.g., CONNECT,
1020   OPTIONS, and TRACE). Other conditional request header fields, defined by
1021   extensions to HTTP, might place conditions on the state of the target
1022   resource in general, or on a group of resources. For instance, the If header
1023   field in WebDAV can make a request conditional on various aspects (such
1024   as locks) of multiple resources
1025   (<xref target="RFC4918" x:fmt="," x:sec="10.4"/>).
1026</t>
1027<t>
1028   When more than one conditional request header field is present in a request,
1029   the order in which the fields are evaluated becomes important. In practice,
1030   the fields defined in this document are consistently implemented in a
1031   single, logical order, due to the fact that entity tags are presumed to be
1032   more accurate than date validators. For example, the only reason to send
1033   both <x:ref>If-Modified-Since</x:ref> and <x:ref>If-None-Match</x:ref> in
1034   the same GET request is to support intermediary caches that might not have
1035   implemented <x:ref>If-None-Match</x:ref>, so it makes sense to ignore the
1036   <x:ref>If-Modified-Since</x:ref> when entity tags are understood and
1037   available for the selected representation.
1038</t>
1039<t>
1040   The general rule of conditional precedence is that exact match conditions
1041   are evaluated before cache-validating conditions and, within that order,
1042   last-modified conditions are only evaluated if the corresponding
1043   entity tag condition is not present (or not applicable because the
1044   selected representation does not have an entity tag).
1045</t>
1046<t>
1047   Specifically, the fields defined by this specification are evaluated
1048   as follows:
1049   <list style="numbers">
1050     <t anchor="precedence1">When <x:ref>If-Match</x:ref> is present, evaluate it:
1051       <list style="symbols">
1052         <t>if true, continue to step <xref target="precedence3" format="counter"/></t>
1053         <t>if false, respond <x:ref>412 (Precondition Failed)</x:ref> unless
1054            it can be determined that the state-changing request has already
1055            succeeded (see <xref target="header.if-match"/>)</t>
1056       </list>
1057     </t>
1058     <t anchor="precedence2">When <x:ref>If-Match</x:ref> is not present and
1059        <x:ref>If-Unmodified-Since</x:ref> is present, evaluate it:
1060       <list style="symbols">
1061         <t>if true, continue to step <xref target="precedence3" format="counter"/></t>
1062         <t>if false, respond <x:ref>412 (Precondition Failed)</x:ref> unless
1063            it can be determined that the state-changing request has already
1064            succeeded (see <xref target="header.if-unmodified-since"/>)</t>
1065       </list>
1066     </t>
1067     <t anchor="precedence3">When <x:ref>If-None-Match</x:ref> is present, evaluate it:
1068       <list style="symbols">
1069         <t>if true, continue to step <xref target="precedence5" format="counter"/></t>
1070         <t>if false for GET/HEAD, respond <x:ref>304 (Not Modified)</x:ref></t>
1071         <t>if false for other methods, respond <x:ref>412 (Precondition Failed)</x:ref></t>
1072       </list>
1073     </t>
1074     <t anchor="precedence4">When the method is GET or HEAD,
1075        <x:ref>If-None-Match</x:ref> is not present, and
1076        <x:ref>If-Modified-Since</x:ref> is present, evaluate it:
1077       <list style="symbols">
1078         <t>if true, continue to step <xref target="precedence5" format="counter"/></t>
1079         <t>if false, respond <x:ref>304 (Not Modified)</x:ref></t>
1080       </list>
1081     </t>
1082     <t anchor="precedence5">When the method is GET and both <x:ref>Range</x:ref> and
1083        <x:ref>If-Range</x:ref> are present, evaluate If-Range:
1084       <list style="symbols">
1085         <t>if the validator matches and the Range specification is
1086            applicable to the selected representation, respond
1087            <x:ref>206 (Partial Content)</x:ref> <xref target="Part5"/></t>
1088       </list>
1089     </t>
1090     <t anchor="precedencelast">Otherwise,
1091       <list style="symbols">
1092         <t>all conditions are met, so perform the requested action and
1093            respond according to its success or failure.</t>
1094       </list>
1095     </t>
1096   </list>
1097</t>
1098<t>
1099   Any extension to HTTP/1.1 that defines additional conditional request
1100   header fields ought to define its own expectations regarding the order
1101   for evaluating such fields in relation to those defined in this document
1102   and other conditionals that might be found in practice.
1103</t>
1104</section>
1105
1106<section title="IANA Considerations" anchor="IANA.considerations">
1107
1108<section title="Status Code Registration" anchor="status.code.registration">
1109<t>
1110   The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
1111   shall be updated with the registrations below:
1112</t>
1113<?BEGININC p4-conditional.iana-status-codes ?>
1114<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
1115<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
1116   <ttcol>Value</ttcol>
1117   <ttcol>Description</ttcol>
1118   <ttcol>Reference</ttcol>
1119   <c>304</c>
1120   <c>Not Modified</c>
1121   <c>
1122      <xref target="status.304"/>
1123   </c>
1124   <c>412</c>
1125   <c>Precondition Failed</c>
1126   <c>
1127      <xref target="status.412"/>
1128   </c>
1129</texttable>
1130<!--(END)-->
1131<?ENDINC p4-conditional.iana-status-codes ?>
1132</section>
1133
1134<section title="Header Field Registration" anchor="header.field.registration">
1135<t>
1136   HTTP header fields are registered within the Message Header Field Registry
1137   maintained at
1138   <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/>.
1139</t>
1140<t>
1141   This document defines the following HTTP header fields, so their
1142   associated registry entries shall be updated according to the permanent
1143   registrations below (see <xref target="BCP90"/>):
1144</t>
1145<?BEGININC p4-conditional.iana-headers ?>
1146<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
1147<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
1148   <ttcol>Header Field Name</ttcol>
1149   <ttcol>Protocol</ttcol>
1150   <ttcol>Status</ttcol>
1151   <ttcol>Reference</ttcol>
1152
1153   <c>ETag</c>
1154   <c>http</c>
1155   <c>standard</c>
1156   <c>
1157      <xref target="header.etag"/>
1158   </c>
1159   <c>If-Match</c>
1160   <c>http</c>
1161   <c>standard</c>
1162   <c>
1163      <xref target="header.if-match"/>
1164   </c>
1165   <c>If-Modified-Since</c>
1166   <c>http</c>
1167   <c>standard</c>
1168   <c>
1169      <xref target="header.if-modified-since"/>
1170   </c>
1171   <c>If-None-Match</c>
1172   <c>http</c>
1173   <c>standard</c>
1174   <c>
1175      <xref target="header.if-none-match"/>
1176   </c>
1177   <c>If-Unmodified-Since</c>
1178   <c>http</c>
1179   <c>standard</c>
1180   <c>
1181      <xref target="header.if-unmodified-since"/>
1182   </c>
1183   <c>Last-Modified</c>
1184   <c>http</c>
1185   <c>standard</c>
1186   <c>
1187      <xref target="header.last-modified"/>
1188   </c>
1189</texttable>
1190<!--(END)-->
1191<?ENDINC p4-conditional.iana-headers ?>
1192<t>
1193   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
1194</t>
1195</section>
1196</section>
1197
1198<section title="Security Considerations" anchor="security.considerations">
1199<t>
1200   This section is meant to inform developers, information providers, and
1201   users of known security concerns specific to the HTTP/1.1 conditional
1202   request mechanisms. More general security considerations are addressed
1203   in HTTP messaging &messaging; and semantics &semantics;.
1204</t>
1205<t>
1206   The validators defined by this specification are not intended to ensure
1207   the validity of a representation, guard against malicious changes, or
1208   detect man-in-the-middle attacks. At best, they enable more efficient cache
1209   updates and optimistic concurrent writes when all participants are behaving
1210   nicely. At worst, the conditions will fail and the client will receive a
1211   response that is no more harmful than an HTTP exchange without conditional
1212   requests.
1213</t>
1214<t>
1215   An entity-tag can be abused in ways that create privacy risks. For example,
1216   a site might deliberately construct a semantically invalid entity-tag that
1217   is unique to the user or user agent, send it in a cacheable response with a
1218   long freshness time, and then read that entity-tag in later conditional
1219   requests as a means of re-identifying that user or user agent. Such an
1220   identifying tag would become a persistent identifier for as long as the
1221   user agent retained the original cache entry. User agents that cache
1222   representations ought to ensure that the cache is cleared or replaced
1223   whenever the user performs privacy-maintaining actions, such as clearing
1224   stored cookies or changing to a private browsing mode.
1225</t>
1226</section>
1227
1228<section title="Acknowledgments" anchor="acks">
1229<t>
1230  See &acks;.
1231</t>
1232</section>
1233</middle>
1234<back>
1235
1236<references title="Normative References">
1237
1238<reference anchor="Part1">
1239  <front>
1240    <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
1241    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1242      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1243      <address><email>fielding@gbiv.com</email></address>
1244    </author>
1245    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1246      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1247      <address><email>julian.reschke@greenbytes.de</email></address>
1248    </author>
1249    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1250  </front>
1251  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
1252  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
1253</reference>
1254
1255<reference anchor="Part2">
1256  <front>
1257    <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
1258    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1259      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1260      <address><email>fielding@gbiv.com</email></address>
1261    </author>
1262    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1263      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1264      <address><email>julian.reschke@greenbytes.de</email></address>
1265    </author>
1266    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1267  </front>
1268  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
1269  <x:source href="p2-semantics.xml" basename="p2-semantics">
1270    <x:defines>2xx</x:defines>
1271    <x:defines>2xx (Successful)</x:defines>
1272    <x:defines>200 (OK)</x:defines>
1273    <x:defines>204 (No Content)</x:defines>
1274    <x:defines>Accept-Encoding</x:defines>
1275    <x:defines>Content-Location</x:defines>
1276    <x:defines>Content-Type</x:defines>
1277    <x:defines>Date</x:defines>
1278    <x:defines>Location</x:defines>
1279    <x:defines>Vary</x:defines>
1280    <x:defines>selected representation</x:defines>
1281  </x:source>
1282</reference>
1283
1284<reference anchor="Part5">
1285  <front>
1286    <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title>
1287    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1288      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1289      <address><email>fielding@gbiv.com</email></address>
1290    </author>
1291    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1292      <organization abbrev="W3C">World Wide Web Consortium</organization>
1293      <address><email>ylafon@w3.org</email></address>
1294    </author>
1295    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1296      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1297      <address><email>julian.reschke@greenbytes.de</email></address>
1298    </author>
1299    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1300  </front>
1301  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
1302  <x:source href="p5-range.xml" basename="p5-range">
1303    <x:defines>If-Range</x:defines>
1304    <x:defines>Range</x:defines>
1305    <x:defines>206 (Partial Content)</x:defines>
1306  </x:source>
1307</reference>
1308
1309<reference anchor="Part6">
1310  <front>
1311    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
1312    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1313      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1314      <address><email>fielding@gbiv.com</email></address>
1315    </author>
1316    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
1317      <organization>Akamai</organization>
1318      <address><email>mnot@mnot.net</email></address>
1319    </author>
1320    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1321      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1322      <address><email>julian.reschke@greenbytes.de</email></address>
1323    </author>
1324    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1325  </front>
1326  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
1327  <x:source href="p6-cache.xml" basename="p6-cache">
1328    <x:defines>Cache-Control</x:defines>
1329    <x:defines>Expires</x:defines>
1330  </x:source>
1331</reference>
1332
1333<reference anchor="RFC2119">
1334  <front>
1335    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
1336    <author initials="S." surname="Bradner" fullname="Scott Bradner">
1337      <organization>Harvard University</organization>
1338      <address><email>sob@harvard.edu</email></address>
1339    </author>
1340    <date month="March" year="1997"/>
1341  </front>
1342  <seriesInfo name="BCP" value="14"/>
1343  <seriesInfo name="RFC" value="2119"/>
1344</reference>
1345
1346<reference anchor="RFC5234">
1347  <front>
1348    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
1349    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
1350      <organization>Brandenburg InternetWorking</organization>
1351      <address>
1352        <email>dcrocker@bbiw.net</email>
1353      </address> 
1354    </author>
1355    <author initials="P." surname="Overell" fullname="Paul Overell">
1356      <organization>THUS plc.</organization>
1357      <address>
1358        <email>paul.overell@thus.net</email>
1359      </address>
1360    </author>
1361    <date month="January" year="2008"/>
1362  </front>
1363  <seriesInfo name="STD" value="68"/>
1364  <seriesInfo name="RFC" value="5234"/>
1365</reference>
1366
1367</references>
1368
1369<references title="Informative References">
1370
1371<reference anchor="RFC2616">
1372  <front>
1373    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
1374    <author initials="R." surname="Fielding" fullname="R. Fielding">
1375      <organization>University of California, Irvine</organization>
1376      <address><email>fielding@ics.uci.edu</email></address>
1377    </author>
1378    <author initials="J." surname="Gettys" fullname="J. Gettys">
1379      <organization>W3C</organization>
1380      <address><email>jg@w3.org</email></address>
1381    </author>
1382    <author initials="J." surname="Mogul" fullname="J. Mogul">
1383      <organization>Compaq Computer Corporation</organization>
1384      <address><email>mogul@wrl.dec.com</email></address>
1385    </author>
1386    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
1387      <organization>MIT Laboratory for Computer Science</organization>
1388      <address><email>frystyk@w3.org</email></address>
1389    </author>
1390    <author initials="L." surname="Masinter" fullname="L. Masinter">
1391      <organization>Xerox Corporation</organization>
1392      <address><email>masinter@parc.xerox.com</email></address>
1393    </author>
1394    <author initials="P." surname="Leach" fullname="P. Leach">
1395      <organization>Microsoft Corporation</organization>
1396      <address><email>paulle@microsoft.com</email></address>
1397    </author>
1398    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
1399      <organization>W3C</organization>
1400      <address><email>timbl@w3.org</email></address>
1401    </author>
1402    <date month="June" year="1999"/>
1403  </front>
1404  <seriesInfo name="RFC" value="2616"/>
1405</reference>
1406
1407<reference anchor='BCP90'>
1408  <front>
1409    <title>Registration Procedures for Message Header Fields</title>
1410    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
1411      <organization>Nine by Nine</organization>
1412      <address><email>GK-IETF@ninebynine.org</email></address>
1413    </author>
1414    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
1415      <organization>BEA Systems</organization>
1416      <address><email>mnot@pobox.com</email></address>
1417    </author>
1418    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
1419      <organization>HP Labs</organization>
1420      <address><email>JeffMogul@acm.org</email></address>
1421    </author>
1422    <date year='2004' month='September' />
1423  </front>
1424  <seriesInfo name='BCP' value='90' />
1425  <seriesInfo name='RFC' value='3864' />
1426</reference>
1427
1428<reference anchor='RFC4918'>
1429  <front>
1430    <title>HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)</title>
1431    <author initials="L.M." surname="Dusseault" fullname="Lisa Dusseault" role="editor" >
1432      <organization abbrev="CommerceNet">CommerceNet</organization>
1433      <address><email>ldusseault@commerce.net</email></address>
1434    </author>
1435    <date month="June" year="2007" />
1436  </front>
1437  <seriesInfo name='RFC' value='4918' />
1438</reference>
1439</references>
1440
1441<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
1442<t>
1443  The definition of validator weakness has been expanded and clarified.
1444  (<xref target="weak.and.strong.validators" />)
1445</t>
1446<t>
1447  Weak entity-tags are now allowed in all requests except range requests
1448  (Sections <xref target="weak.and.strong.validators" format="counter"/> and
1449  <xref target="header.if-none-match" format="counter"/>).
1450</t>
1451<t>
1452  The <x:ref>ETag</x:ref> header field ABNF has been changed to not use
1453  quoted-string, thus avoiding escaping issues.
1454  (<xref target="header.etag" />)
1455</t>
1456<t>
1457  ETag is defined to provide an entity tag for the selected representation,
1458  thereby clarifying what it applies to in various situations (such as a
1459  PUT response).
1460  (<xref target="header.etag" />)
1461</t>
1462<t>
1463  The precedence for evaluation of conditional requests has been defined.
1464  (<xref target="precedence" />)
1465</t>
1466</section>
1467
1468<section title="Imported ABNF" anchor="imported.abnf">
1469  <x:anchor-alias value="ALPHA"/>
1470  <x:anchor-alias value="CR"/>
1471  <x:anchor-alias value="DIGIT"/>
1472  <x:anchor-alias value="DQUOTE"/>
1473  <x:anchor-alias value="LF"/>
1474  <x:anchor-alias value="OCTET"/>
1475  <x:anchor-alias value="VCHAR"/>
1476  <x:anchor-alias value="core.rules"/>
1477  <x:anchor-alias value="obs-text"/>
1478  <x:anchor-alias value="OWS"/>
1479  <x:anchor-alias value="HTTP-date"/>
1480<t>
1481  The following core rules are included by
1482  reference, as defined in <xref target="RFC5234" x:fmt="of" x:sec="B.1"/>:
1483  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
1484  DIGIT (decimal 0-9), DQUOTE (double quote),
1485  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
1486  OCTET (any 8-bit sequence of data), SP (space), and
1487  VCHAR (any visible US-ASCII character).
1488</t>
1489<t>
1490  The rules below are defined in <xref target="Part1"/>:
1491</t>
1492<figure><artwork type="abnf2616">
1493  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
1494  <x:ref>obs-text</x:ref>      = &lt;obs-text, defined in &field-components;&gt;
1495</artwork></figure>
1496<t>
1497  The rules below are defined in other parts:
1498</t>
1499<figure><artwork type="abnf2616">
1500  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, defined in &http-date;&gt;
1501</artwork></figure>
1502</section>
1503
1504<?BEGININC p4-conditional.abnf-appendix ?>
1505<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
1506<t>
1507  In the collected ABNF below, list rules are expanded as per <xref target="Part1" x:rel="#notation"/>.
1508</t><figure>
1509<artwork type="abnf" name="p4-conditional.parsed-abnf">
1510<x:ref>ETag</x:ref> = entity-tag
1511
1512<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, defined in [Part2], Section 7.1.1.1&gt;
1513
1514<x:ref>If-Match</x:ref> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1515 entity-tag ] ) )
1516<x:ref>If-Modified-Since</x:ref> = HTTP-date
1517<x:ref>If-None-Match</x:ref> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1518 entity-tag ] ) )
1519<x:ref>If-Unmodified-Since</x:ref> = HTTP-date
1520
1521<x:ref>Last-Modified</x:ref> = HTTP-date
1522
1523<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.3&gt;
1524
1525<x:ref>entity-tag</x:ref> = [ weak ] opaque-tag
1526<x:ref>etagc</x:ref> = "!" / %x23-7E ; '#'-'~'
1527 / obs-text
1528
1529<x:ref>obs-text</x:ref> = &lt;obs-text, defined in [Part1], Section 3.2.6&gt;
1530<x:ref>opaque-tag</x:ref> = DQUOTE *etagc DQUOTE
1531
1532<x:ref>weak</x:ref> = %x57.2F ; W/
1533</artwork>
1534</figure>
1535</section>
1536<?ENDINC p4-conditional.abnf-appendix ?>
1537
1538<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
1539<t>
1540  Changes up to the first Working Group Last Call draft are summarized
1541  in <eref target="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-19#appendix-C"/>.
1542</t>
1543
1544<section title="Since draft-ietf-httpbis-p4-conditional-19" anchor="changes.since.19">
1545<t>
1546  Closed issues:
1547  <list style="symbols">
1548    <t>
1549      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/241"/>:
1550      "Need to clarify eval order/interaction of conditional headers"
1551    </t>
1552    <t>
1553      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/345"/>:
1554      "Required headers on 304 and 206"
1555    </t>
1556    <t>
1557      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/350"/>:
1558      "Optionality of Conditional Request Support"
1559    </t>
1560    <t>
1561      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/354"/>:
1562      "ETags and Conditional Requests"
1563    </t>
1564    <t>
1565      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
1566      "ABNF requirements for recipients"
1567    </t>
1568    <t>
1569      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/363"/>:
1570      "Rare cases"
1571    </t>
1572    <t>
1573      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/365"/>:
1574      "Conditional Request Security Considerations"
1575    </t>
1576    <t>
1577      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/371"/>:
1578      "If-Modified-Since lacks definition for method != GET"
1579    </t>
1580    <t>
1581      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/372"/>:
1582      "refactor conditional header field descriptions"
1583    </t>
1584  </list>
1585</t>
1586</section>
1587
1588<section title="Since draft-ietf-httpbis-p4-conditional-20" anchor="changes.since.20">
1589<t>
1590  <list style="symbols">
1591    <t>
1592      Conformance criteria and considerations regarding error handling are
1593      now defined in Part 1.
1594    </t>
1595  </list>
1596</t>
1597</section>
1598
1599<section title="Since draft-ietf-httpbis-p4-conditional-21" anchor="changes.since.21">
1600<t>
1601  Closed issues:
1602  <list style="symbols">
1603    <t>
1604      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/96"/>:
1605      "Conditional GET text"
1606    </t>
1607    <t>
1608      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/350"/>:
1609      "Optionality of Conditional Request Support"
1610    </t>
1611    <t>
1612      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/384"/>:
1613      "unclear prose in definition of 304"
1614    </t>
1615    <t>
1616      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/401"/>:
1617      "ETags and Conneg"
1618    </t>
1619    <t>
1620      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/402"/>:
1621      "Comparison function for If-Match and If-None-Match"
1622    </t>
1623    <t>
1624      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/406"/>:
1625      "304 without validator"
1626    </t>
1627    <t>
1628      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/427"/>:
1629      "If-Match and 428"
1630    </t>
1631  </list>
1632</t>
1633</section>
1634
1635<section title="Since draft-ietf-httpbis-p4-conditional-22" anchor="changes.since.22">
1636<t>
1637  Closed issues:
1638  <list style="symbols">
1639    <t>
1640      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/436"/>:
1641      "explain list expansion in ABNF appendices"
1642    </t>
1643    <t>
1644      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/437"/>:
1645      "incorrect example dates"
1646    </t>
1647  </list>
1648</t>
1649<t>
1650  Partly resolved issues:
1651  <list style="symbols">
1652    <t>
1653      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/461"/>:
1654      "Editorial suggestions"
1655    </t>
1656  </list>
1657</t>
1658</section>
1659
1660<section title="Since draft-ietf-httpbis-p4-conditional-23" anchor="changes.since.23">
1661<t>
1662  None yet.
1663</t>
1664</section>
1665</section>
1666
1667</back>
1668</rfc>
Note: See TracBrowser for help on using the repository browser.