source: draft-ietf-httpbis/07/draft-ietf-httpbis-p4-conditional-07.xml @ 653

Last change on this file since 653 was 609, checked in by julian.reschke@…, 10 years ago

HTAB cleanup (not even editorial)

File size: 58.9 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!--
3    This XML document is the output of clean-for-DTD.xslt; a tool that strips
4    extensions to RFC2629(bis) from documents for processing with xml2rfc.
5-->
6<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
7<?rfc toc="yes" ?>
8<?rfc symrefs="yes" ?>
9<?rfc sortrefs="yes" ?>
10<?rfc compact="yes"?>
11<?rfc subcompact="no" ?>
12<?rfc linkmailto="no" ?>
13<?rfc editing="no" ?>
14<?rfc comments="yes"?>
15<?rfc inline="yes"?>
16<!DOCTYPE rfc
17  PUBLIC "" "rfc2629.dtd">
18<rfc obsoletes="2616" category="std" ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p4-conditional-07">
19<front>
20
21  <title abbrev="HTTP/1.1, Part 4">HTTP/1.1, part 4: Conditional Requests</title>
22
23  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
24    <organization abbrev="Day Software">Day Software</organization>
25    <address>
26      <postal>
27        <street>23 Corporate Plaza DR, Suite 280</street>
28        <city>Newport Beach</city>
29        <region>CA</region>
30        <code>92660</code>
31        <country>USA</country>
32      </postal>
33      <phone>+1-949-706-5300</phone>
34      <facsimile>+1-949-706-5305</facsimile>
35      <email>fielding@gbiv.com</email>
36      <uri>http://roy.gbiv.com/</uri>
37    </address>
38  </author>
39
40  <author initials="J." surname="Gettys" fullname="Jim Gettys">
41    <organization>One Laptop per Child</organization>
42    <address>
43      <postal>
44        <street>21 Oak Knoll Road</street>
45        <city>Carlisle</city>
46        <region>MA</region>
47        <code>01741</code>
48        <country>USA</country>
49      </postal>
50      <email>jg@laptop.org</email>
51      <uri>http://www.laptop.org/</uri>
52    </address>
53  </author>
54 
55  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
56    <organization abbrev="HP">Hewlett-Packard Company</organization>
57    <address>
58      <postal>
59        <street>HP Labs, Large Scale Systems Group</street>
60        <street>1501 Page Mill Road, MS 1177</street>
61        <city>Palo Alto</city>
62        <region>CA</region>
63        <code>94304</code>
64        <country>USA</country>
65      </postal>
66      <email>JeffMogul@acm.org</email>
67    </address>
68  </author>
69
70  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
71    <organization abbrev="Microsoft">Microsoft Corporation</organization>
72    <address>
73      <postal>
74        <street>1 Microsoft Way</street>
75        <city>Redmond</city>
76        <region>WA</region>
77        <code>98052</code>
78        <country>USA</country>
79      </postal>
80      <email>henrikn@microsoft.com</email>
81    </address>
82  </author>
83
84  <author initials="L." surname="Masinter" fullname="Larry Masinter">
85    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
86    <address>
87      <postal>
88        <street>345 Park Ave</street>
89        <city>San Jose</city>
90        <region>CA</region>
91        <code>95110</code>
92        <country>USA</country>
93      </postal>
94      <email>LMM@acm.org</email>
95      <uri>http://larry.masinter.net/</uri>
96    </address>
97  </author>
98 
99  <author initials="P." surname="Leach" fullname="Paul J. Leach">
100    <organization abbrev="Microsoft">Microsoft Corporation</organization>
101    <address>
102      <postal>
103        <street>1 Microsoft Way</street>
104        <city>Redmond</city>
105        <region>WA</region>
106        <code>98052</code>
107      </postal>
108      <email>paulle@microsoft.com</email>
109    </address>
110  </author>
111   
112  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
113    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
114    <address>
115      <postal>
116        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
117        <street>The Stata Center, Building 32</street>
118        <street>32 Vassar Street</street>
119        <city>Cambridge</city>
120        <region>MA</region>
121        <code>02139</code>
122        <country>USA</country>
123      </postal>
124      <email>timbl@w3.org</email>
125      <uri>http://www.w3.org/People/Berners-Lee/</uri>
126    </address>
127  </author>
128
129  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
130    <organization abbrev="W3C">World Wide Web Consortium</organization>
131    <address>
132      <postal>
133        <street>W3C / ERCIM</street>
134        <street>2004, rte des Lucioles</street>
135        <city>Sophia-Antipolis</city>
136        <region>AM</region>
137        <code>06902</code>
138        <country>France</country>
139      </postal>
140      <email>ylafon@w3.org</email>
141      <uri>http://www.raubacapeu.net/people/yves/</uri>
142    </address>
143  </author>
144
145  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
146    <organization abbrev="greenbytes">greenbytes GmbH</organization>
147    <address>
148      <postal>
149        <street>Hafenweg 16</street>
150        <city>Muenster</city><region>NW</region><code>48155</code>
151        <country>Germany</country>
152      </postal>
153      <phone>+49 251 2807760</phone>
154      <facsimile>+49 251 2807761</facsimile>
155      <email>julian.reschke@greenbytes.de</email>
156      <uri>http://greenbytes.de/tech/webdav/</uri>
157    </address>
158  </author>
159
160  <date day="13" month="July" year="2009"/>
161  <workgroup>HTTPbis Working Group</workgroup>
162
163<abstract>
164<t>
165   The Hypertext Transfer Protocol (HTTP) is an application-level
166   protocol for distributed, collaborative, hypermedia information
167   systems. HTTP has been in use by the World Wide Web global information
168   initiative since 1990. This document is Part 4 of the seven-part specification
169   that defines the protocol referred to as "HTTP/1.1" and, taken together,
170   obsoletes RFC 2616.  Part 4 defines request header fields for
171   indicating conditional requests and the rules for constructing responses
172   to those requests.
173</t>
174</abstract>
175
176<note title="Editorial Note (To be removed by RFC Editor)">
177  <t>
178    Discussion of this draft should take place on the HTTPBIS working group
179    mailing list (ietf-http-wg@w3.org). The current issues list is
180    at <eref target="http://tools.ietf.org/wg/httpbis/trac/report/11"/>
181    and related documents (including fancy diffs) can be found at
182    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
183  </t>
184  <t>
185    The changes in this draft are summarized in <xref target="changes.since.06"/>.
186  </t>
187</note>
188</front>
189<middle>
190<section title="Introduction" anchor="introduction">
191<t>
192   This document defines HTTP/1.1 response metadata for indicating potential
193   changes to payload content, including modification time stamps and opaque
194   entity-tags, and the HTTP conditional request mechanisms that allow
195   preconditions to be placed on a request method.  Conditional GET requests
196   allow for efficient cache updates.  Other conditional request methods are
197   used to protect against overwriting or misunderstanding the state of a
198   resource that has been changed unbeknownst to the requesting client.
199</t>
200<t>
201   This document is currently disorganized in order to minimize the changes
202   between drafts and enable reviewers to see the smaller errata changes.
203   The next draft will reorganize the sections to better reflect the content.
204   In particular, the sections on resource metadata will be discussed first
205   and then followed by each conditional request-header, concluding with a
206   definition of precedence and the expectation of ordering strong validator
207   checks before weak validator checks.  It is likely that more content from
208   <xref target="Part6"/> will migrate to this part, where appropriate.
209   The current mess reflects how widely dispersed these topics and associated
210   requirements had become in <xref target="RFC2616"/>.
211</t>
212
213<section title="Requirements" anchor="intro.requirements">
214<t>
215   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
216   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
217   document are to be interpreted as described in <xref target="RFC2119"/>.
218</t>
219<t>
220   An implementation is not compliant if it fails to satisfy one or more
221   of the MUST or REQUIRED level requirements for the protocols it
222   implements. An implementation that satisfies all the MUST or REQUIRED
223   level and all the SHOULD level requirements for its protocols is said
224   to be "unconditionally compliant"; one that satisfies all the MUST
225   level requirements but not all the SHOULD level requirements for its
226   protocols is said to be "conditionally compliant."
227</t>
228</section>
229
230<section title="Syntax Notation" anchor="notation">
231 
232 
233 
234 
235 
236 
237 
238<t>
239  This specification uses the ABNF syntax defined in Section 1.2 of <xref target="Part1"/> (which
240  extends the syntax defined in <xref target="RFC5234"/> with a list rule).
241  <xref target="collected.abnf"/> shows the collected ABNF, with the list
242  rule expanded.
243</t>
244<t>
245  The following core rules are included by
246  reference, as defined in <xref target="RFC5234"/>, Appendix B.1:
247  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
248  DIGIT (decimal 0-9), DQUOTE (double quote),
249  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
250  OCTET (any 8-bit sequence of data), SP (space),
251  VCHAR (any visible USASCII character),
252  and WSP (whitespace).
253</t>
254
255<section title="Core Rules" anchor="core.rules">
256 
257 
258<t>
259  The core rules below are defined in Section 1.2.2 of <xref target="Part1"/>:
260</t>
261<figure><artwork type="abnf2616"><![CDATA[
262  quoted-string = <quoted-string, defined in [Part1], Section 1.2.2>
263  OWS           = <OWS, defined in [Part1], Section 1.2.2>
264]]></artwork></figure>
265</section>
266
267<section title="ABNF Rules defined in other Parts of the Specification" anchor="abnf.dependencies">
268 
269<t>
270  The ABNF rules below are defined in other parts:
271</t>
272<figure><artwork type="abnf2616"><![CDATA[
273  HTTP-date     = <HTTP-date, defined in [Part1], Section 3.2>
274]]></artwork></figure>
275</section>
276
277</section>
278
279</section>
280
281<section title="Entity Tags" anchor="entity.tags">
282 
283 
284 
285<t>
286   Entity tags are used for comparing two or more entities from the same
287   requested resource. HTTP/1.1 uses entity tags in the ETag (<xref target="header.etag"/>),
288   If-Match (<xref target="header.if-match"/>), If-None-Match (<xref target="header.if-none-match"/>), and
289   If-Range (Section 5.3 of <xref target="Part5"/>) header fields. The definition of how they
290   are used and compared as cache validators is in <xref target="weak.and.strong.validators"/>. An
291   entity tag consists of an opaque quoted string, possibly prefixed by
292   a weakness indicator.
293</t>
294<figure><iref primary="true" item="Grammar" subitem="entity-tag"/><iref primary="true" item="Grammar" subitem="weak"/><iref primary="true" item="Grammar" subitem="opaque-tag"/><artwork type="abnf2616"><![CDATA[
295  entity-tag = [ weak ] opaque-tag
296  weak       = %x57.2F ; "W/", case-sensitive
297  opaque-tag = quoted-string
298]]></artwork></figure>
299<t>
300   A "strong entity tag" MAY be shared by two entities of a resource
301   only if they are equivalent by octet equality.
302</t>
303<t>
304   A "weak entity tag," indicated by the "W/" prefix, MAY be shared by
305   two entities of a resource only if the entities are equivalent and
306   could be substituted for each other with no significant change in
307   semantics. A weak entity tag can only be used for weak comparison.
308</t>
309<t>
310   An entity tag MUST be unique across all versions of all entities
311   associated with a particular resource. A given entity tag value MAY
312   be used for entities obtained by requests on different URIs. The use
313   of the same entity tag value in conjunction with entities obtained by
314   requests on different URIs does not imply the equivalence of those
315   entities.
316</t>
317</section>
318
319<section title="Status Code Definitions">
320<section title="304 Not Modified" anchor="status.304">
321  <iref primary="true" item="304 Not Modified (status code)"/>
322  <iref primary="true" item="Status Codes" subitem="304 Not Modified"/>
323<t>
324   If the client has performed a conditional GET request and access is
325   allowed, but the document has not been modified, the server SHOULD
326   respond with this status code. The 304 response MUST NOT contain a
327   message-body, and thus is always terminated by the first empty line
328   after the header fields.
329</t>
330<t>
331   The response MUST include the following header fields:
332  <list style="symbols">
333    <t>Date, unless its omission is required by Section 8.3.1 of <xref target="Part1"/>.<vspace blankLines="1"/>
334         If a clockless origin server obeys these rules, and proxies and
335         clients add their own Date to any response received without one (as
336         already specified by Section 8.3 of <xref target="Part1"/>, caches will operate
337         correctly.</t>
338    <t>ETag and/or Content-Location, if the header would have been sent
339         in a 200 response to the same request.</t>
340    <t>Expires, Cache-Control, and/or Vary, if the field-value might
341         differ from that sent in any previous response for the same
342         variant.</t>
343  </list>
344</t>
345<t>
346   If the conditional GET used a strong cache validator (see <xref target="weak.and.strong.validators"/>),
347   the response SHOULD NOT  include other entity-headers.
348   Otherwise (i.e., the conditional GET used a weak validator), the
349   response MUST NOT include other entity-headers; this prevents
350   inconsistencies between cached entity-bodies and updated headers.
351</t>
352<t>
353   If a 304 response indicates an entity not currently cached, then the
354   cache MUST disregard the response and repeat the request without the
355   conditional.
356</t>
357<t>
358   If a cache uses a received 304 response to update a cache entry, the
359   cache MUST update the entry to reflect any new field values given in
360   the response.
361</t>
362</section>
363
364<section title="412 Precondition Failed" anchor="status.412">
365  <iref primary="true" item="412 Precondition Failed (status code)"/>
366  <iref primary="true" item="Status Codes" subitem="412 Precondition Failed"/>
367<t>
368   The precondition given in one or more of the request-header fields
369   evaluated to false when it was tested on the server. This response
370   code allows the client to place preconditions on the current resource
371   metainformation (header field data) and thus prevent the requested
372   method from being applied to a resource other than the one intended.
373</t>
374</section>
375</section>
376
377<section title="Weak and Strong Validators" anchor="weak.and.strong.validators">
378<t>
379   Since both origin servers and caches will compare two validators to
380   decide if they represent the same or different entities, one normally
381   would expect that if the entity (the entity-body or any entity-headers)
382   changes in any way, then the associated validator would
383   change as well. If this is true, then we call this validator a
384   "strong validator."
385</t>
386<t>
387   However, there might be cases when a server prefers to change the
388   validator only on semantically significant changes, and not when
389   insignificant aspects of the entity change. A validator that does not
390   always change when the resource changes is a "weak validator."
391</t>
392<t>
393   Entity tags are normally "strong validators," but the protocol
394   provides a mechanism to tag an entity tag as "weak." One can think of
395   a strong validator as one that changes whenever the bits of an entity
396   changes, while a weak value changes whenever the meaning of an entity
397   changes. Alternatively, one can think of a strong validator as part
398   of an identifier for a specific entity, while a weak validator is
399   part of an identifier for a set of semantically equivalent entities.
400  <list><t>
401      Note: One example of a strong validator is an integer that is
402      incremented in stable storage every time an entity is changed.
403    </t><t>
404      An entity's modification time, if represented with one-second
405      resolution, could be a weak validator, since it is possible that
406      the resource might be modified twice during a single second.
407    </t><t>
408      Support for weak validators is optional. However, weak validators
409      allow for more efficient caching of equivalent objects; for
410      example, a hit counter on a site is probably good enough if it is
411      updated every few days or weeks, and any value during that period
412      is likely "good enough" to be equivalent.
413    </t></list>
414</t>
415<t>
416   A "use" of a validator is either when a client generates a request
417   and includes the validator in a validating header field, or when a
418   server compares two validators.
419</t>
420<t>
421   Strong validators are usable in any context. Weak validators are only
422   usable in contexts that do not depend on exact equality of an entity.
423   For example, either kind is usable for a conditional GET of a full
424   entity. However, only a strong validator is usable for a sub-range
425   retrieval, since otherwise the client might end up with an internally
426   inconsistent entity.
427</t>
428<t>
429   Clients MUST NOT use weak validators in range requests (<xref target="Part5"/>).
430</t>
431<t>
432   The only function that HTTP/1.1 defines on validators is
433   comparison. There are two validator comparison functions, depending
434   on whether the comparison context allows the use of weak validators
435   or not:
436  <list style="symbols">
437     <t>The strong comparison function: in order to be considered equal,
438        both opaque-tags MUST be identical character-by-character, and both
439        MUST NOT be weak.</t>
440     <t>The weak comparison function: in order to be considered equal, both
441        opaque-tags MUST be identical character-by-character.</t>
442  </list>
443</t>
444<t>
445   The example below shows the results for a set of entity tag pairs,
446   and both the weak and strong comparison function results:
447</t>
448<texttable align="left">
449  <ttcol>ETag 1</ttcol>
450  <ttcol>ETag 2</ttcol>
451  <ttcol>Strong Comparison</ttcol>
452  <ttcol>Weak Comparison</ttcol>
453
454  <c>W/"1"</c>
455  <c>W/"1"</c>
456  <c>no match</c>
457  <c>match</c>
458 
459  <c>W/"1"</c>
460  <c>W/"2"</c>
461  <c>no match</c>
462  <c>no match</c>
463
464  <c>W/"1"</c>
465  <c>"1"</c>
466  <c>no match</c>
467  <c>match</c>
468
469  <c>"1"</c>
470  <c>"1"</c>
471  <c>match</c>
472  <c>match</c>
473</texttable>
474<t>
475   An entity tag is strong unless it is explicitly tagged as weak.
476   <xref target="entity.tags"/> gives the syntax for entity tags.
477</t>
478<t>
479   A Last-Modified time, when used as a validator in a request, is
480   implicitly weak unless it is possible to deduce that it is strong,
481   using the following rules:
482  <list style="symbols">
483     <t>The validator is being compared by an origin server to the
484        actual current validator for the entity and,</t>
485     <t>That origin server reliably knows that the associated entity did
486        not change twice during the second covered by the presented
487        validator.</t>
488  </list>
489</t>
490<t>
491   or
492  <list style="symbols">
493     <t>The validator is about to be used by a client in an If-Modified-Since
494        or If-Unmodified-Since header, because the client
495        has a cache entry for the associated entity, and</t>
496     <t>That cache entry includes a Date value, which gives the time
497        when the origin server sent the original response, and</t>
498     <t>The presented Last-Modified time is at least 60 seconds before
499        the Date value.</t>
500  </list>
501</t>
502<t>
503   or
504  <list style="symbols">
505     <t>The validator is being compared by an intermediate cache to the
506        validator stored in its cache entry for the entity, and</t>
507     <t>That cache entry includes a Date value, which gives the time
508        when the origin server sent the original response, and</t>
509     <t>The presented Last-Modified time is at least 60 seconds before
510        the Date value.</t>
511  </list>
512</t>
513<t>
514   This method relies on the fact that if two different responses were
515   sent by the origin server during the same second, but both had the
516   same Last-Modified time, then at least one of those responses would
517   have a Date value equal to its Last-Modified time. The arbitrary 60-second
518   limit guards against the possibility that the Date and Last-Modified
519   values are generated from different clocks, or at somewhat
520   different times during the preparation of the response. An
521   implementation MAY use a value larger than 60 seconds, if it is
522   believed that 60 seconds is too short.
523</t>
524<t>
525   If a client wishes to perform a sub-range retrieval on a value for
526   which it has only a Last-Modified time and no opaque validator, it
527   MAY do this only if the Last-Modified time is strong in the sense
528   described here.
529</t>
530<t>
531   A cache or origin server receiving a conditional range request
532   (<xref target="Part5"/>) MUST use the strong comparison function to
533   evaluate the condition.
534</t>
535<t>
536   These rules allow HTTP/1.1 caches and clients to safely perform sub-range
537   retrievals on values that have been obtained from HTTP/1.0
538   servers.
539</t>
540</section>
541
542<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">
543<t>
544   We adopt a set of rules and recommendations for origin servers,
545   clients, and caches regarding when various validator types ought to
546   be used, and for what purposes.
547</t>
548<t>
549   HTTP/1.1 origin servers:
550  <list style="symbols">
551     <t>SHOULD send an entity tag validator unless it is not feasible to
552        generate one.</t>
553
554     <t>MAY send a weak entity tag instead of a strong entity tag, if
555        performance considerations support the use of weak entity tags,
556        or if it is unfeasible to send a strong entity tag.</t>
557
558     <t>SHOULD send a Last-Modified value if it is feasible to send one,
559        unless the risk of a breakdown in semantic transparency that
560        could result from using this date in an If-Modified-Since header
561        would lead to serious problems.</t>
562  </list>
563</t>
564<t>
565   In other words, the preferred behavior for an HTTP/1.1 origin server
566   is to send both a strong entity tag and a Last-Modified value.
567</t>
568<t>
569   In order to be legal, a strong entity tag MUST change whenever the
570   associated entity changes in any way. A weak entity tag SHOULD
571   change whenever the associated entity changes in a semantically
572   significant way.
573</t>
574<t><list>
575  <t>
576    Note: in order to provide semantically transparent caching, an
577    origin server must avoid reusing a specific strong entity tag
578    value for two different entities, or reusing a specific weak
579    entity tag value for two semantically different entities. Cache
580    entries might persist for arbitrarily long periods, regardless of
581    expiration times, so it might be inappropriate to expect that a
582    cache will never again attempt to validate an entry using a
583    validator that it obtained at some point in the past.
584  </t>
585</list></t>
586<t>
587   HTTP/1.1 clients:
588  <list style="symbols">
589     <t>If an entity tag has been provided by the origin server, MUST
590        use that entity tag in any cache-conditional request (using If-Match
591        or If-None-Match).</t>
592
593     <t>If only a Last-Modified value has been provided by the origin
594        server, SHOULD use that value in non-subrange cache-conditional
595        requests (using If-Modified-Since).</t>
596
597     <t>If only a Last-Modified value has been provided by an HTTP/1.0
598        origin server, MAY use that value in subrange cache-conditional
599        requests (using If-Unmodified-Since:). The user agent SHOULD
600        provide a way to disable this, in case of difficulty.</t>
601
602     <t>If both an entity tag and a Last-Modified value have been
603        provided by the origin server, SHOULD use both validators in
604        cache-conditional requests. This allows both HTTP/1.0 and
605        HTTP/1.1 caches to respond appropriately.</t>
606  </list>
607</t>
608<t>
609   An HTTP/1.1 origin server, upon receiving a conditional request that
610   includes both a Last-Modified date (e.g., in an If-Modified-Since or
611   If-Unmodified-Since header field) and one or more entity tags (e.g.,
612   in an If-Match, If-None-Match, or If-Range header field) as cache
613   validators, MUST NOT return a response status of 304 (Not Modified)
614   unless doing so is consistent with all of the conditional header
615   fields in the request.
616</t>
617<t>
618   An HTTP/1.1 caching proxy, upon receiving a conditional request that
619   includes both a Last-Modified date and one or more entity tags as
620   cache validators, MUST NOT return a locally cached response to the
621   client unless that cached response is consistent with all of the
622   conditional header fields in the request.
623  <list><t>
624      Note: The general principle behind these rules is that HTTP/1.1
625      servers and clients should transmit as much non-redundant
626      information as is available in their responses and requests.
627      HTTP/1.1 systems receiving this information will make the most
628      conservative assumptions about the validators they receive.
629  </t><t>
630      HTTP/1.0 clients and caches will ignore entity tags. Generally,
631      last-modified values received or used by these systems will
632      support transparent and efficient caching, and so HTTP/1.1 origin
633      servers should provide Last-Modified values. In those rare cases
634      where the use of a Last-Modified value as a validator by an
635      HTTP/1.0 system could result in a serious problem, then HTTP/1.1
636      origin servers should not provide one.
637  </t></list>
638</t>
639</section>
640
641<section title="Header Field Definitions" anchor="header.fields">
642<t>
643   This section defines the syntax and semantics of HTTP/1.1 header fields
644   related to conditional requests.
645</t>
646<t>
647   For entity-header fields, both sender and recipient refer to either the
648   client or the server, depending on who sends and who receives the entity.
649</t>
650
651<section title="ETag" anchor="header.etag">
652  <iref primary="true" item="ETag header"/>
653  <iref primary="true" item="Headers" subitem="ETag"/>
654 
655 
656<t>
657   The response-header field "ETag" provides the current value of the
658   entity tag (see <xref target="entity.tags"/>) for the requested variant.
659   The headers used with entity
660   tags are described in Sections <xref target="header.if-match" format="counter"/>
661   and <xref target="header.if-none-match" format="counter"/> of this document,
662   and in Section 5.3 of <xref target="Part5"/>. The entity tag
663   MAY be used for comparison with other entities from the same resource
664   (see <xref target="weak.and.strong.validators"/>).
665</t>
666<figure><iref primary="true" item="Grammar" subitem="ETag"/><iref primary="true" item="Grammar" subitem="ETag-v"/><artwork type="abnf2616"><![CDATA[
667  ETag   = "ETag" ":" OWS ETag-v
668  ETag-v = entity-tag
669]]></artwork></figure>
670<figure><preamble>
671  Examples:
672</preamble>
673<artwork type="example"><![CDATA[
674  ETag: "xyzzy"
675  ETag: W/"xyzzy"
676  ETag: ""
677]]></artwork></figure>
678<t>
679   The ETag response-header field value, an entity tag, provides for an
680   "opaque" cache validator. This might allow more reliable validation
681   in situations where it is inconvenient to store modification dates,
682   where the one-second resolution of HTTP date values is not
683   sufficient, or where the origin server wishes to avoid certain
684   paradoxes that might arise from the use of modification dates.
685</t>
686<t>
687   The principle behind entity tags is that only the service author
688   knows the semantics of a resource well enough to select an
689   appropriate cache validation mechanism, and the specification of any
690   validator comparison function more complex than byte-equality would
691   open up a can of worms. Thus, comparisons of any other headers
692   (except Last-Modified, for compatibility with HTTP/1.0) are never
693   used for purposes of validating a cache entry.
694</t>
695</section>
696
697<section title="If-Match" anchor="header.if-match">
698  <iref primary="true" item="If-Match header"/>
699  <iref primary="true" item="Headers" subitem="If-Match"/>
700 
701 
702<t>
703   The request-header field "If-Match" is used with a method to make it
704   conditional. A client that has one or more entities previously
705   obtained from the resource can verify that one of those entities is
706   current by including a list of their associated entity tags in the
707   If-Match header field. Entity tags are defined in <xref target="entity.tags"/>. The
708   purpose of this feature is to allow efficient updates of cached
709   information with a minimum amount of transaction overhead. It is also
710   used, on updating requests, to prevent inadvertent modification of
711   the wrong version of a resource. As a special case, the value "*"
712   matches any current entity of the resource.
713</t>
714<figure><iref primary="true" item="Grammar" subitem="If-Match"/><iref primary="true" item="Grammar" subitem="If-Match-v"/><artwork type="abnf2616"><![CDATA[
715  If-Match   = "If-Match" ":" OWS If-Match-v
716  If-Match-v = "*" / 1#entity-tag
717]]></artwork></figure>
718<t>
719   If any of the entity tags match the entity tag of the entity that
720   would have been returned in the response to a similar GET request
721   (without the If-Match header) on that resource, or if "*" is given
722   and any current entity exists for that resource, then the server MAY
723   perform the requested method as if the If-Match header field did not
724   exist.
725</t>
726<t>
727   A server MUST use the strong comparison function (see <xref target="weak.and.strong.validators"/>)
728   to compare the entity tags in If-Match.
729</t>
730<t>
731   If none of the entity tags match, or if "*" is given and no current
732   entity exists, the server MUST NOT perform the requested method, and
733   MUST return a 412 (Precondition Failed) response. This behavior is
734   most useful when the client wants to prevent an updating method, such
735   as PUT, from modifying a resource that has changed since the client
736   last retrieved it.
737</t>
738<t>
739   If the request would, without the If-Match header field, result in
740   anything other than a 2xx or 412 status, then the If-Match header
741   MUST be ignored.
742</t>
743<t>
744   The meaning of "If-Match: *" is that the method SHOULD be performed
745   if the representation selected by the origin server (or by a cache,
746   possibly using the Vary mechanism, see Section 3.5 of <xref target="Part6"/>) exists, and
747   MUST NOT be performed if the representation does not exist.
748</t>
749<t>
750   A request intended to update a resource (e.g., a PUT) MAY include an
751   If-Match header field to signal that the request method MUST NOT be
752   applied if the entity corresponding to the If-Match value (a single
753   entity tag) is no longer a representation of that resource. This
754   allows the user to indicate that they do not wish the request to be
755   successful if the resource has been changed without their knowledge.
756   Examples:
757</t>
758<figure><artwork type="example"><![CDATA[
759  If-Match: "xyzzy"
760  If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
761  If-Match: *
762]]></artwork></figure>
763<t>
764   The result of a request having both an If-Match header field and
765   either an If-None-Match or an If-Modified-Since header fields is
766   undefined by this specification.
767</t>
768</section>
769
770<section title="If-Modified-Since" anchor="header.if-modified-since">
771  <iref primary="true" item="If-Modified-Since header"/>
772  <iref primary="true" item="Headers" subitem="If-Modified-Since"/>
773 
774 
775<t>
776   The request-header field "If-Modified-Since" is used with a method to
777   make it conditional: if the requested variant has not been modified
778   since the time specified in this field, an entity will not be
779   returned from the server; instead, a 304 (Not Modified) response will
780   be returned without any message-body.
781</t>
782<figure><iref primary="true" item="Grammar" subitem="If-Modified-Since"/><iref primary="true" item="Grammar" subitem="If-Modified-Since-v"/><artwork type="abnf2616"><![CDATA[
783  If-Modified-Since   = "If-Modified-Since" ":" OWS
784                        If-Modified-Since-v
785  If-Modified-Since-v = HTTP-date
786]]></artwork></figure>
787<t>
788   An example of the field is:
789</t>
790<figure><artwork type="example"><![CDATA[
791  If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
792]]></artwork></figure>
793<t>
794   A GET method with an If-Modified-Since header and no Range header
795   requests that the identified entity be transferred only if it has
796   been modified since the date given by the If-Modified-Since header.
797   The algorithm for determining this includes the following cases:
798  <list style="numbers">
799      <t>If the request would normally result in anything other than a
800         200 (OK) status, or if the passed If-Modified-Since date is
801         invalid, the response is exactly the same as for a normal GET.
802         A date which is later than the server's current time is
803         invalid.</t>
804
805      <t>If the variant has been modified since the If-Modified-Since
806         date, the response is exactly the same as for a normal GET.</t>
807
808      <t>If the variant has not been modified since a valid If-Modified-Since
809         date, the server SHOULD return a 304 (Not
810         Modified) response.</t>
811  </list>
812</t>
813<t>
814   The purpose of this feature is to allow efficient updates of cached
815   information with a minimum amount of transaction overhead.
816  <list><t>
817      Note: The Range request-header field modifies the meaning of If-Modified-Since;
818      see Section 5.4 of <xref target="Part5"/> for full details.
819    </t><t>
820      Note: If-Modified-Since times are interpreted by the server, whose
821      clock might not be synchronized with the client.
822    </t><t>
823      Note: When handling an If-Modified-Since header field, some
824      servers will use an exact date comparison function, rather than a
825      less-than function, for deciding whether to send a 304 (Not
826      Modified) response. To get best results when sending an If-Modified-Since
827      header field for cache validation, clients are
828      advised to use the exact date string received in a previous Last-Modified
829      header field whenever possible.
830    </t><t>
831      Note: If a client uses an arbitrary date in the If-Modified-Since
832      header instead of a date taken from the Last-Modified header for
833      the same request, the client should be aware of the fact that this
834      date is interpreted in the server's understanding of time. The
835      client should consider unsynchronized clocks and rounding problems
836      due to the different encodings of time between the client and
837      server. This includes the possibility of race conditions if the
838      document has changed between the time it was first requested and
839      the If-Modified-Since date of a subsequent request, and the
840      possibility of clock-skew-related problems if the If-Modified-Since
841      date is derived from the client's clock without correction
842      to the server's clock. Corrections for different time bases
843      between client and server are at best approximate due to network
844      latency.
845    </t>
846  </list>
847</t>
848<t>
849   The result of a request having both an If-Modified-Since header field
850   and either an If-Match or an If-Unmodified-Since header fields is
851   undefined by this specification.
852</t>
853</section>
854
855<section title="If-None-Match" anchor="header.if-none-match">
856  <iref primary="true" item="If-None-Match header"/>
857  <iref primary="true" item="Headers" subitem="If-None-Match"/>
858 
859 
860<t>
861   The request-header field "If-None-Match" is used with a method to make
862   it conditional. A client that has one or more entities previously
863   obtained from the resource can verify that none of those entities is
864   current by including a list of their associated entity tags in the
865   If-None-Match header field. The purpose of this feature is to allow
866   efficient updates of cached information with a minimum amount of
867   transaction overhead. It is also used to prevent a method (e.g. PUT)
868   from inadvertently modifying an existing resource when the client
869   believes that the resource does not exist.
870</t>
871<t>
872   As a special case, the value "*" matches any current entity of the
873   resource.
874</t>
875<figure><iref primary="true" item="Grammar" subitem="If-None-Match"/><iref primary="true" item="Grammar" subitem="If-None-Match-v"/><artwork type="abnf2616"><![CDATA[
876  If-None-Match   = "If-None-Match" ":" OWS If-None-Match-v
877  If-None-Match-v = "*" / 1#entity-tag
878]]></artwork></figure>
879<t>
880   If any of the entity tags match the entity tag of the entity that
881   would have been returned in the response to a similar GET request
882   (without the If-None-Match header) on that resource, or if "*" is
883   given and any current entity exists for that resource, then the
884   server MUST NOT perform the requested method, unless required to do
885   so because the resource's modification date fails to match that
886   supplied in an If-Modified-Since header field in the request.
887   Instead, if the request method was GET or HEAD, the server SHOULD
888   respond with a 304 (Not Modified) response, including the cache-related
889   header fields (particularly ETag) of one of the entities that
890   matched. For all other request methods, the server MUST respond with
891   a status of 412 (Precondition Failed).
892</t>
893<t>
894   See <xref target="weak.and.strong.validators"/> for rules on how to
895   determine if two entity tags match.
896</t>
897<t>
898   If none of the entity tags match, then the server MAY perform the
899   requested method as if the If-None-Match header field did not exist,
900   but MUST also ignore any If-Modified-Since header field(s) in the
901   request. That is, if no entity tags match, then the server MUST NOT
902   return a 304 (Not Modified) response.
903</t>
904<t>
905   If the request would, without the If-None-Match header field, result
906   in anything other than a 2xx or 304 status, then the If-None-Match
907   header MUST be ignored. (See <xref target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for a discussion of
908   server behavior when both If-Modified-Since and If-None-Match appear
909   in the same request.)
910</t>
911<t>
912   The meaning of "If-None-Match: *" is that the method MUST NOT be
913   performed if the representation selected by the origin server (or by
914   a cache, possibly using the Vary mechanism, see Section 3.5 of <xref target="Part6"/>)
915   exists, and SHOULD be performed if the representation does not exist.
916   This feature is intended to be useful in preventing races between PUT
917   operations.
918</t>
919<t>
920   Examples:
921</t>
922<figure><artwork type="example"><![CDATA[
923  If-None-Match: "xyzzy"
924  If-None-Match: W/"xyzzy"
925  If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
926  If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
927  If-None-Match: *
928]]></artwork></figure>
929<t>
930   The result of a request having both an If-None-Match header field and
931   either an If-Match or an If-Unmodified-Since header fields is
932   undefined by this specification.
933</t>
934</section>
935
936<section title="If-Unmodified-Since" anchor="header.if-unmodified-since">
937  <iref primary="true" item="If-Unmodified-Since header"/>
938  <iref primary="true" item="Headers" subitem="If-Unmodified-Since"/>
939 
940 
941<t>
942   The request-header field "If-Unmodified-Since" is used with a method to
943   make it conditional. If the requested resource has not been modified
944   since the time specified in this field, the server SHOULD perform the
945   requested operation as if the If-Unmodified-Since header were not
946   present.
947</t>
948<t>
949   If the requested variant has been modified since the specified time,
950   the server MUST NOT perform the requested operation, and MUST return
951   a 412 (Precondition Failed).
952</t>
953<figure><iref primary="true" item="Grammar" subitem="If-Unmodified-Since"/><iref primary="true" item="Grammar" subitem="If-Unmodified-Since-v"/><artwork type="abnf2616"><![CDATA[
954  If-Unmodified-Since   = "If-Unmodified-Since" ":" OWS
955                          If-Unmodified-Since-v
956  If-Unmodified-Since-v = HTTP-date
957]]></artwork></figure>
958<t>
959   An example of the field is:
960</t>
961<figure><artwork type="example"><![CDATA[
962  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
963]]></artwork></figure>
964<t>
965   If the request normally (i.e., without the If-Unmodified-Since
966   header) would result in anything other than a 2xx or 412 status, the
967   If-Unmodified-Since header SHOULD be ignored.
968</t>
969<t>
970   If the specified date is invalid, the header is ignored.
971</t>
972<t>
973   The result of a request having both an If-Unmodified-Since header
974   field and either an If-None-Match or an If-Modified-Since header
975   fields is undefined by this specification.
976</t>
977</section>
978
979<section title="Last-Modified" anchor="header.last-modified">
980  <iref primary="true" item="Last-Modified header"/>
981  <iref primary="true" item="Headers" subitem="Last-Modified"/>
982 
983 
984<t>
985   The entity-header field "Last-Modified" indicates the date and time at
986   which the origin server believes the variant was last modified.
987</t>
988<figure><iref primary="true" item="Grammar" subitem="Last-Modified"/><iref primary="true" item="Grammar" subitem="Last-Modified-v"/><artwork type="abnf2616"><![CDATA[
989  Last-Modified   = "Last-Modified" ":" OWS Last-Modified-v
990  Last-Modified-v = HTTP-date
991]]></artwork></figure>
992<t>
993   An example of its use is
994</t>
995<figure><artwork type="example"><![CDATA[
996  Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
997]]></artwork></figure>
998<t>
999   The exact meaning of this header field depends on the implementation
1000   of the origin server and the nature of the original resource. For
1001   files, it may be just the file system last-modified time. For
1002   entities with dynamically included parts, it may be the most recent
1003   of the set of last-modify times for its component parts. For database
1004   gateways, it may be the last-update time stamp of the record. For
1005   virtual objects, it may be the last time the internal state changed.
1006</t>
1007<t>
1008   An origin server MUST NOT send a Last-Modified date which is later
1009   than the server's time of message origination. In such cases, where
1010   the resource's last modification would indicate some time in the
1011   future, the server MUST replace that date with the message
1012   origination date.
1013</t>
1014<t>
1015   An origin server SHOULD obtain the Last-Modified value of the entity
1016   as close as possible to the time that it generates the Date value of
1017   its response. This allows a recipient to make an accurate assessment
1018   of the entity's modification time, especially if the entity changes
1019   near the time that the response is generated.
1020</t>
1021<t>
1022   HTTP/1.1 servers SHOULD send Last-Modified whenever feasible.
1023</t>
1024<t>
1025   The Last-Modified entity-header field value is often used as a cache
1026   validator. In simple terms, a cache entry is considered to be valid
1027   if the entity has not been modified since the Last-Modified value.
1028</t>
1029</section>
1030
1031</section>
1032
1033<section title="IANA Considerations" anchor="IANA.considerations">
1034<section title="Message Header Registration" anchor="message.header.registration">
1035<t>
1036   The Message Header Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> should be updated
1037   with the permanent registrations below (see <xref target="RFC3864"/>):
1038</t>
1039<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
1040<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
1041   <ttcol>Header Field Name</ttcol>
1042   <ttcol>Protocol</ttcol>
1043   <ttcol>Status</ttcol>
1044   <ttcol>Reference</ttcol>
1045
1046   <c>ETag</c>
1047   <c>http</c>
1048   <c>standard</c>
1049   <c>
1050      <xref target="header.etag"/>
1051   </c>
1052   <c>If-Match</c>
1053   <c>http</c>
1054   <c>standard</c>
1055   <c>
1056      <xref target="header.if-match"/>
1057   </c>
1058   <c>If-Modified-Since</c>
1059   <c>http</c>
1060   <c>standard</c>
1061   <c>
1062      <xref target="header.if-modified-since"/>
1063   </c>
1064   <c>If-None-Match</c>
1065   <c>http</c>
1066   <c>standard</c>
1067   <c>
1068      <xref target="header.if-none-match"/>
1069   </c>
1070   <c>If-Unmodified-Since</c>
1071   <c>http</c>
1072   <c>standard</c>
1073   <c>
1074      <xref target="header.if-unmodified-since"/>
1075   </c>
1076   <c>Last-Modified</c>
1077   <c>http</c>
1078   <c>standard</c>
1079   <c>
1080      <xref target="header.last-modified"/>
1081   </c>
1082</texttable>
1083<!--(END)-->
1084<t>
1085   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
1086</t>
1087</section>
1088</section>
1089
1090<section title="Security Considerations" anchor="security.considerations">
1091<t>
1092   No additional security considerations have been identified beyond
1093   those applicable to HTTP in general <xref target="Part1"/>.
1094</t>
1095</section>
1096
1097<section title="Acknowledgments" anchor="ack">
1098</section>
1099</middle>
1100<back>
1101
1102<references title="Normative References">
1103
1104<reference anchor="Part1">
1105  <front>
1106    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
1107    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1108      <organization abbrev="Day Software">Day Software</organization>
1109      <address><email>fielding@gbiv.com</email></address>
1110    </author>
1111    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1112      <organization>One Laptop per Child</organization>
1113      <address><email>jg@laptop.org</email></address>
1114    </author>
1115    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1116      <organization abbrev="HP">Hewlett-Packard Company</organization>
1117      <address><email>JeffMogul@acm.org</email></address>
1118    </author>
1119    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1120      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1121      <address><email>henrikn@microsoft.com</email></address>
1122    </author>
1123    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1124      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1125      <address><email>LMM@acm.org</email></address>
1126    </author>
1127    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1128      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1129      <address><email>paulle@microsoft.com</email></address>
1130    </author>
1131    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1132      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1133      <address><email>timbl@w3.org</email></address>
1134    </author>
1135    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1136      <organization abbrev="W3C">World Wide Web Consortium</organization>
1137      <address><email>ylafon@w3.org</email></address>
1138    </author>
1139    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1140      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1141      <address><email>julian.reschke@greenbytes.de</email></address>
1142    </author>
1143    <date month="July" year="2009"/>
1144  </front>
1145  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-07"/>
1146 
1147</reference>
1148
1149<reference anchor="Part5">
1150  <front>
1151    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
1152    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1153      <organization abbrev="Day Software">Day Software</organization>
1154      <address><email>fielding@gbiv.com</email></address>
1155    </author>
1156    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1157      <organization>One Laptop per Child</organization>
1158      <address><email>jg@laptop.org</email></address>
1159    </author>
1160    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1161      <organization abbrev="HP">Hewlett-Packard Company</organization>
1162      <address><email>JeffMogul@acm.org</email></address>
1163    </author>
1164    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1165      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1166      <address><email>henrikn@microsoft.com</email></address>
1167    </author>
1168    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1169      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1170      <address><email>LMM@acm.org</email></address>
1171    </author>
1172    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1173      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1174      <address><email>paulle@microsoft.com</email></address>
1175    </author>
1176    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1177      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1178      <address><email>timbl@w3.org</email></address>
1179    </author>
1180    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1181      <organization abbrev="W3C">World Wide Web Consortium</organization>
1182      <address><email>ylafon@w3.org</email></address>
1183    </author>
1184    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1185      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1186      <address><email>julian.reschke@greenbytes.de</email></address>
1187    </author>
1188    <date month="July" year="2009"/>
1189  </front>
1190  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-07"/>
1191 
1192</reference>
1193
1194<reference anchor="Part6">
1195  <front>
1196    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
1197    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1198      <organization abbrev="Day Software">Day Software</organization>
1199      <address><email>fielding@gbiv.com</email></address>
1200    </author>
1201    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1202      <organization>One Laptop per Child</organization>
1203      <address><email>jg@laptop.org</email></address>
1204    </author>
1205    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1206      <organization abbrev="HP">Hewlett-Packard Company</organization>
1207      <address><email>JeffMogul@acm.org</email></address>
1208    </author>
1209    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1210      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1211      <address><email>henrikn@microsoft.com</email></address>
1212    </author>
1213    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1214      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1215      <address><email>LMM@acm.org</email></address>
1216    </author>
1217    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1218      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1219      <address><email>paulle@microsoft.com</email></address>
1220    </author>
1221    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1222      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1223      <address><email>timbl@w3.org</email></address>
1224    </author>
1225    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1226      <organization abbrev="W3C">World Wide Web Consortium</organization>
1227      <address><email>ylafon@w3.org</email></address>
1228    </author>
1229    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
1230      <organization/>
1231      <address><email>mnot@mnot.net</email></address>
1232    </author>
1233    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1234      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1235      <address><email>julian.reschke@greenbytes.de</email></address>
1236    </author>
1237    <date month="July" year="2009"/>
1238  </front>
1239  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-07"/>
1240 
1241</reference>
1242
1243<reference anchor="RFC2119">
1244  <front>
1245    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
1246    <author initials="S." surname="Bradner" fullname="Scott Bradner">
1247      <organization>Harvard University</organization>
1248      <address><email>sob@harvard.edu</email></address>
1249    </author>
1250    <date month="March" year="1997"/>
1251  </front>
1252  <seriesInfo name="BCP" value="14"/>
1253  <seriesInfo name="RFC" value="2119"/>
1254</reference>
1255
1256<reference anchor="RFC5234">
1257  <front>
1258    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
1259    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
1260      <organization>Brandenburg InternetWorking</organization>
1261      <address>
1262      <postal>
1263      <street>675 Spruce Dr.</street>
1264      <city>Sunnyvale</city>
1265      <region>CA</region>
1266      <code>94086</code>
1267      <country>US</country></postal>
1268      <phone>+1.408.246.8253</phone>
1269      <email>dcrocker@bbiw.net</email></address> 
1270    </author>
1271    <author initials="P." surname="Overell" fullname="Paul Overell">
1272      <organization>THUS plc.</organization>
1273      <address>
1274      <postal>
1275      <street>1/2 Berkeley Square</street>
1276      <street>99 Berkely Street</street>
1277      <city>Glasgow</city>
1278      <code>G3 7HR</code>
1279      <country>UK</country></postal>
1280      <email>paul.overell@thus.net</email></address>
1281    </author>
1282    <date month="January" year="2008"/>
1283  </front>
1284  <seriesInfo name="STD" value="68"/>
1285  <seriesInfo name="RFC" value="5234"/>
1286</reference>
1287
1288</references>
1289
1290<references title="Informative References">
1291
1292<reference anchor="RFC2616">
1293  <front>
1294    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
1295    <author initials="R." surname="Fielding" fullname="R. Fielding">
1296      <organization>University of California, Irvine</organization>
1297      <address><email>fielding@ics.uci.edu</email></address>
1298    </author>
1299    <author initials="J." surname="Gettys" fullname="J. Gettys">
1300      <organization>W3C</organization>
1301      <address><email>jg@w3.org</email></address>
1302    </author>
1303    <author initials="J." surname="Mogul" fullname="J. Mogul">
1304      <organization>Compaq Computer Corporation</organization>
1305      <address><email>mogul@wrl.dec.com</email></address>
1306    </author>
1307    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
1308      <organization>MIT Laboratory for Computer Science</organization>
1309      <address><email>frystyk@w3.org</email></address>
1310    </author>
1311    <author initials="L." surname="Masinter" fullname="L. Masinter">
1312      <organization>Xerox Corporation</organization>
1313      <address><email>masinter@parc.xerox.com</email></address>
1314    </author>
1315    <author initials="P." surname="Leach" fullname="P. Leach">
1316      <organization>Microsoft Corporation</organization>
1317      <address><email>paulle@microsoft.com</email></address>
1318    </author>
1319    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
1320      <organization>W3C</organization>
1321      <address><email>timbl@w3.org</email></address>
1322    </author>
1323    <date month="June" year="1999"/>
1324  </front>
1325  <seriesInfo name="RFC" value="2616"/>
1326</reference>
1327
1328<reference anchor="RFC3864">
1329  <front>
1330    <title>Registration Procedures for Message Header Fields</title>
1331    <author initials="G." surname="Klyne" fullname="G. Klyne">
1332      <organization>Nine by Nine</organization>
1333      <address><email>GK-IETF@ninebynine.org</email></address>
1334    </author>
1335    <author initials="M." surname="Nottingham" fullname="M. Nottingham">
1336      <organization>BEA Systems</organization>
1337      <address><email>mnot@pobox.com</email></address>
1338    </author>
1339    <author initials="J." surname="Mogul" fullname="J. Mogul">
1340      <organization>HP Labs</organization>
1341      <address><email>JeffMogul@acm.org</email></address>
1342    </author>
1343    <date year="2004" month="September"/>
1344  </front>
1345  <seriesInfo name="BCP" value="90"/>
1346  <seriesInfo name="RFC" value="3864"/>
1347</reference>
1348
1349</references>
1350
1351<section title="Compatibility with Previous Versions" anchor="compatibility">
1352
1353<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
1354<t>
1355  Allow weak entity tags in all requests except range requests (Sections
1356  <xref target="weak.and.strong.validators" format="counter"/> and
1357  <xref target="header.if-none-match" format="counter"/>).
1358</t>
1359</section>
1360
1361</section>
1362
1363<section title="Collected ABNF" anchor="collected.abnf">
1364<figure>
1365<artwork type="abnf" name="p4-conditional.parsed-abnf"><![CDATA[
1366ETag = "ETag:" OWS ETag-v
1367ETag-v = entity-tag
1368
1369HTTP-date = <HTTP-date, defined in [Part1], Section 3.2>
1370
1371If-Match = "If-Match:" OWS If-Match-v
1372If-Match-v = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1373 entity-tag ] ) )
1374If-Modified-Since = "If-Modified-Since:" OWS If-Modified-Since-v
1375If-Modified-Since-v = HTTP-date
1376If-None-Match = "If-None-Match:" OWS If-None-Match-v
1377If-None-Match-v = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1378 entity-tag ] ) )
1379If-Unmodified-Since = "If-Unmodified-Since:" OWS
1380 If-Unmodified-Since-v
1381If-Unmodified-Since-v = HTTP-date
1382
1383Last-Modified = "Last-Modified:" OWS Last-Modified-v
1384Last-Modified-v = HTTP-date
1385
1386OWS = <OWS, defined in [Part1], Section 1.2.2>
1387
1388entity-tag = [ weak ] opaque-tag
1389
1390opaque-tag = quoted-string
1391
1392quoted-string = <quoted-string, defined in [Part1], Section 1.2.2>
1393
1394weak = %x57.2F ; W/
1395]]></artwork>
1396</figure>
1397<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline"><![CDATA[
1398; ETag defined but not used
1399; If-Match defined but not used
1400; If-Modified-Since defined but not used
1401; If-None-Match defined but not used
1402; If-Unmodified-Since defined but not used
1403; Last-Modified defined but not used
1404]]></artwork></figure></section>
1405
1406<section title="Change Log (to be removed by RFC Editor before publication)" anchor="change.log">
1407
1408<section title="Since RFC2616">
1409<t>
1410  Extracted relevant partitions from <xref target="RFC2616"/>.
1411</t>
1412</section>
1413
1414<section title="Since draft-ietf-httpbis-p4-conditional-00">
1415<t>
1416  Closed issues:
1417  <list style="symbols"> 
1418    <t>
1419      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
1420      "Normative and Informative references"
1421    </t>
1422  </list>
1423</t>
1424<t>
1425  Other changes:
1426  <list style="symbols"> 
1427    <t>
1428      Move definitions of 304 and 412 condition codes from Part2.
1429    </t>
1430  </list>
1431</t>
1432</section>
1433
1434<section title="Since draft-ietf-httpbis-p4-conditional-01">
1435<t>
1436  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1437  <list style="symbols"> 
1438    <t>
1439      Add explicit references to BNF syntax and rules imported from other parts of the specification.
1440    </t>
1441  </list>
1442</t>
1443</section>
1444
1445<section title="Since draft-ietf-httpbis-p4-conditional-02" anchor="changes.since.02">
1446<t>
1447  Closed issues:
1448  <list style="symbols"> 
1449    <t>
1450      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/116"/>:
1451      "Weak ETags on non-GET requests"
1452    </t>
1453  </list>
1454</t>
1455<t>
1456  Ongoing work on IANA Message Header Registration (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/40"/>):
1457  <list style="symbols"> 
1458    <t>
1459      Reference RFC 3984, and update header registrations for headers defined
1460      in this document.
1461    </t>
1462  </list>
1463</t>
1464</section>
1465
1466<section title="Since draft-ietf-httpbis-p4-conditional-03" anchor="changes.since.03">
1467<t>
1468  Closed issues:
1469  <list style="symbols"> 
1470    <t>
1471      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/71"/>:
1472      "Examples for ETag matching"
1473    </t>
1474    <t>
1475      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/124"/>:
1476      "'entity value' undefined"
1477    </t>
1478    <t>
1479      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/126"/>:
1480      "bogus 2068 Date header reference"
1481    </t>
1482  </list>
1483</t>
1484</section>
1485
1486<section title="Since draft-ietf-httpbis-p4-conditional-04" anchor="changes.since.04">
1487<t>
1488  Ongoing work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1489  <list style="symbols"> 
1490    <t>
1491      Use "/" instead of "|" for alternatives.
1492    </t>
1493    <t>
1494      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
1495      whitespace ("OWS") and required whitespace ("RWS").
1496    </t>
1497    <t>
1498      Rewrite ABNFs to spell out whitespace rules, factor out
1499      header value format definitions.
1500    </t>
1501  </list>
1502</t>
1503</section>
1504
1505<section title="Since draft-ietf-httpbis-p4-conditional-05" anchor="changes.since.05">
1506<t>
1507  Final work on ABNF conversion (<eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/36"/>):
1508  <list style="symbols"> 
1509    <t>
1510      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
1511    </t>
1512  </list>
1513</t>
1514</section>
1515
1516<section title="Since draft-ietf-httpbis-p4-conditional-06" anchor="changes.since.06">
1517<t>
1518  Closed issues:
1519  <list style="symbols"> 
1520    <t>
1521      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/153"/>:
1522      "case-sensitivity of etag weakness indicator"
1523    </t>
1524  </list>
1525</t>
1526</section>
1527
1528</section>
1529
1530</back>
1531</rfc>
Note: See TracBrowser for help on using the repository browser.