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

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

Collected ABNF section: explain ABNF list expansion (see #436)

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