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

Last change on this file since 1796 was 1796, checked in by julian.reschke@…, 8 years ago

Undo the part of [1783] that removed/moved the conformance/syntax sections.

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