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

Last change on this file since 1262 was 1262, checked in by mnot@…, 9 years ago

Clarify comparison function for If-* headers (see #269).

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