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

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

shorten "defined in" to "see" to avoid overlong lines in artwork (#553)

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 68.8 KB
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=''>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns=''>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns=''>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns=''>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns=''>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns=''>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns=''>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns=''>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns=''>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns=''>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "May">
16  <!ENTITY ID-YEAR "2014">
17  <!ENTITY mdash "&#8212;">
18  <!ENTITY Note "<x:h xmlns:x=''>Note:</x:h>">
19  <!ENTITY architecture               "<xref target='RFC7230' x:rel='#architecture' xmlns:x=''/>">
20  <!ENTITY conformance                "<xref target='RFC7230' x:rel='#conformance' xmlns:x=''/>">
21  <!ENTITY notation                   "<xref target='RFC7230' x:rel='#notation' xmlns:x=''/>">
22  <!ENTITY abnf-extension             "<xref target='RFC7230' x:rel='#abnf.extension' xmlns:x=''/>">
23  <!ENTITY acks                       "<xref target='RFC7230' x:rel='#acks' xmlns:x=''/>">
24  <!ENTITY whitespace                 "<xref target='RFC7230' x:rel='#whitespace' xmlns:x=''/>">
25  <!ENTITY field-components           "<xref target='RFC7230' x:rel='#field.components' xmlns:x=''/>">
26  <!ENTITY header-date                "<xref target='RFC7231' x:rel='' xmlns:x=''/>">
27  <!ENTITY safe-methods               "<xref target='RFC7231' x:rel='#safe.methods' xmlns:x=''/>">
28  <!ENTITY representation             "<xref target='RFC7231' x:rel='#representations' xmlns:x=''/>">
29  <!ENTITY messaging                  "<xref target='RFC7230' xmlns:x=''/>">
30  <!ENTITY semantics                  "<xref target='RFC7231' xmlns:x=''/>">
31  <!ENTITY caching                    "<xref target='RFC7234' xmlns:x=''/>">
32  <!ENTITY cache-key                  "<xref target='RFC7234' x:rel='#constructing.responses.from.caches' xmlns:x=''/>">
33  <!ENTITY cache-validation-received  "<xref target='RFC7234' x:rel='#validation.received' xmlns:x=''/>">
34  <!ENTITY freshening-responses       "<xref target='RFC7234' x:rel='#freshening.responses' xmlns:x=''/>">
35  <!ENTITY header-accept-encoding     "<xref target='RFC7231' x:rel='#header.accept-encoding' xmlns:x=''/>">
36  <!ENTITY header-if-range            "<xref target='RFC7233' x:rel='#header.if-range' xmlns:x=''/>">
37  <!ENTITY header-range               "<xref target='RFC7233' x:rel='#header.range' xmlns:x=''/>">
38  <!ENTITY header-vary                "<xref target='RFC7231' x:rel='#header.vary' xmlns:x=''/>">
39  <!ENTITY http-date                  "<xref target='RFC7231' x:rel='' xmlns:x=''/>">
40  <!ENTITY transfer-codings           "<xref target='RFC7230' x:rel='#transfer.codings' xmlns:x=''/>">
41  <!ENTITY content-negotiation        "<xref target='RFC7231' x:rel='#content.negotiation' xmlns:x=''/>">
43<?rfc toc="yes" ?>
44<?rfc symrefs="yes" ?>
45<?rfc sortrefs="yes" ?>
46<?rfc compact="yes"?>
47<?rfc subcompact="no" ?>
48<?rfc linkmailto="no" ?>
49<?rfc editing="no" ?>
50<?rfc comments="yes"?>
51<?rfc inline="yes"?>
52<?rfc rfcedstyle="yes"?>
53<?rfc-ext allow-markup-in-artwork="yes" ?>
54<?rfc-ext include-references-in-index="yes" ?>
55<rfc obsoletes="2616" category="std" x:maturity-level="proposed"
56     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"
57     xmlns:x=''>
58<x:link rel="prev" basename="p2-semantics"/>
59<x:link rel="next" basename="p5-range"/>
60<x:feedback template="{docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
63  <title abbrev="HTTP/1.1 Conditional Requests">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</title>
65  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
66    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
67    <address>
68      <postal>
69        <street>345 Park Ave</street>
70        <city>San Jose</city>
71        <region>CA</region>
72        <code>95110</code>
73        <country>USA</country>
74      </postal>
75      <email></email>
76      <uri></uri>
77    </address>
78  </author>
80  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
81    <organization abbrev="greenbytes">greenbytes GmbH</organization>
82    <address>
83      <postal>
84        <street>Hafenweg 16</street>
85        <city>Muenster</city><region>NW</region><code>48155</code>
86        <country>Germany</country>
87      </postal>
88      <email></email>
89      <uri></uri>
90    </address>
91  </author>
93  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
95  <area>Applications</area>
96  <workgroup>HTTPbis</workgroup>
98  <keyword>Hypertext Transfer Protocol</keyword>
99  <keyword>HTTP</keyword>
100  <keyword>HTTP conditional requests</keyword>
104   The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for
105   distributed, collaborative, hypertext information systems. This document
106   defines HTTP/1.1 conditional requests, including metadata header fields
107   for indicating state changes, request header fields for making
108   preconditions on such state, and rules for constructing the responses to a
109   conditional request when one or more preconditions evaluate to false.
113<note title="Editorial Note (To be removed by RFC Editor)">
114  <t>
115    Discussion of this draft takes place on the HTTPBIS working group
116    mailing list (, which is archived at
117    <eref target=""/>.
118  </t>
119  <t>
120    The current issues list is at
121    <eref target=""/> and related
122    documents (including fancy diffs) can be found at
123    <eref target=""/>.
124  </t>
125  <t>
126    <spanx>This is a temporary document for the purpose of tracking the editorial changes made during the AUTH48 (RFC publication) phase.</spanx>
127  </t>
132<section title="Introduction" anchor="introduction">
134   Conditional requests are HTTP requests <xref target="RFC7231"/> that include
135   one or more header fields indicating a precondition to be tested before
136   applying the method semantics to the target resource.
137   This document defines the HTTP/1.1 conditional request mechanisms in terms
138   of the architecture, syntax notation, and conformance criteria defined in
139   <xref target="RFC7230"/>.
142   Conditional GET requests are the most efficient mechanism for HTTP
143   cache updates &caching;.  Conditionals can also be
144   applied to state-changing methods, such as PUT and DELETE, to prevent
145   the "lost update" problem: one client accidentally overwriting
146   the work of another client that has been acting in parallel.
148<t><iref primary="true" item="selected representation"/>
149   Conditional request preconditions are based on the state of the target
150   resource as a whole (its current value set) or the state as observed
151   in a previously obtained representation (one value in that set).
152   A resource might have multiple current representations, each with its
153   own observable state.  The conditional request mechanisms assume that
154   the mapping of requests to a "selected representation" (&representation;)
155   will be consistent over time if the server intends to take advantage of
156   conditionals. Regardless, if the mapping is inconsistent and the server is
157   unable to select the appropriate representation, then no harm will result
158   when the precondition evaluates to false.
161   The conditional request preconditions defined by this specification
162   (<xref target="preconditions"/>) are evaluated when applicable to the
163   recipient (<xref target="evaluation"/>) according to their order of
164   precedence (<xref target="precedence"/>).
167<section title="Conformance and Error Handling" anchor="conformance">
169   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
170   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
171   document are to be interpreted as described in <xref target="RFC2119"/>.
174   Conformance criteria and considerations regarding error handling
175   are defined in &conformance;.
179<section title="Syntax Notation" anchor="notation">
181   This specification uses the Augmented Backus-Naur Form (ABNF) notation of
182   <xref target="RFC5234"/> with a list extension, defined in
183   &abnf-extension;, that allows for compact definition of
184   comma-separated lists using a '#' operator (similar to how the '*' operator
185   indicates repetition).
186   <xref target="imported.abnf"/> describes rules imported from
187   other documents.
188   <xref target="collected.abnf"/> shows the collected grammar with all list
189   operators expanded to standard ABNF notation.
194<section title="Validators" anchor="validators">
195   <iref primary="true" item="metadata"/>
196   <iref primary="true" item="validator"/>
198   This specification defines two forms of metadata that are commonly used
199   to observe resource state and test for preconditions: modification dates
200   (<xref target="header.last-modified"/>) and opaque entity tags
201   (<xref target="header.etag"/>).  Additional metadata that reflects resource state
202   has been defined by various extensions of HTTP, such as WebDAV
203   <xref target="RFC4918"/>, that are beyond the scope of this specification.
204   A resource metadata value is referred to as a "<x:dfn>validator</x:dfn>"
205   when it is used within a precondition.
208<section title="Weak versus Strong" anchor="weak.and.strong.validators">
209   <iref primary="true" item="validator" subitem="weak"/>
210   <iref primary="true" item="validator" subitem="strong"/>
212   Validators come in two flavors: strong or weak.  Weak validators are easy
213   to generate but are far less useful for comparisons.  Strong validators
214   are ideal for comparisons but can be very difficult (and occasionally
215   impossible) to generate efficiently.  Rather than impose that all forms
216   of resource adhere to the same strength of validator, HTTP exposes the
217   type of validator in use and imposes restrictions on when weak validators
218   can be used as preconditions.
221   A "strong validator" is representation metadata that changes value whenever
222   a change occurs to the representation data that would be observable in the
223   payload body of a <x:ref>200 (OK)</x:ref> response to GET.
226   A strong validator might change for reasons other than a change to the
227   representation data, such as when a
228   semantically significant part of the representation metadata is changed
229   (e.g., <x:ref>Content-Type</x:ref>), but it is in the best interests of the
230   origin server to only change the value when it is necessary to invalidate
231   the stored responses held by remote caches and authoring tools.
234   Cache entries might persist for arbitrarily long periods, regardless
235   of expiration times.  Thus, a cache might attempt to validate an
236   entry using a validator that it obtained in the distant past.
237   A strong validator is unique across all versions of all
238   representations associated with a particular resource over time.
239   However, there is no implication of uniqueness across representations
240   of different resources (i.e., the same strong validator might be
241   in use for representations of multiple resources at the same time
242   and does not imply that those representations are equivalent).
245   There are a variety of strong validators used in practice.  The best are
246   based on strict revision control, wherein each change to a representation
247   always results in a unique node name and revision identifier being assigned
248   before the representation is made accessible to GET.  A collision-resistant hash
249   function applied to the representation data is also sufficient if the data
250   is available prior to the response header fields being sent and the digest
251   does not need to be recalculated every time a validation request is
252   received.  However, if a resource has distinct representations that differ
253   only in their metadata, such as might occur with content negotiation over
254   media types that happen to share the same data format, then the origin
255   server needs to incorporate additional information in the validator to
256   distinguish those representations.
259   In contrast, a "weak validator" is representation metadata that
260   might not change for every change to the representation data.  This
261   weakness might be due to limitations in how the value is calculated, such
262   as clock resolution or an inability to ensure uniqueness for all possible
263   representations of the resource, or due to a desire by the resource owner
264   to group representations by some self-determined set of equivalency
265   rather than unique sequences of data.  An origin server &SHOULD; change a
266   weak entity-tag whenever it considers prior representations to be
267   unacceptable as a substitute for the current representation. In other words,
268   a weak entity-tag ought to change whenever the origin server wants caches to
269   invalidate old responses.
272   For example, the representation of a weather report that changes in
273   content every second, based on dynamic measurements, might be grouped
274   into sets of equivalent representations (from the origin server's
275   perspective) with the same weak validator in order to allow cached
276   representations to be valid for a reasonable period of time (perhaps
277   adjusted dynamically based on server load or weather quality).
278   Likewise, a representation's modification time, if defined with only
279   one-second resolution, might be a weak validator if it is possible
280   for the representation to be modified twice during a single second and
281   retrieved between those modifications.
284   Likewise, a validator is weak if it is shared by two or more
285   representations of a given resource at the same time, unless those
286   representations have identical representation data. For example, if the
287   origin server sends the same validator for a representation with a gzip
288   content coding applied as it does for a representation with no content
289   coding, then that validator is weak. However, two simultaneous
290   representations might share the same strong validator if they differ only
291   in the representation metadata, such as when two different media types are
292   available for the same representation data.
295   Strong validators are usable for all conditional requests, including cache
296   validation, partial content ranges, and "lost update" avoidance.
297   Weak validators are only usable when the client does not require exact
298   equality with previously obtained representation data, such as when
299   validating a cache entry or limiting a web traversal to recent changes.
303<section title="Last-Modified" anchor="header.last-modified">
304  <iref primary="true" item="Last-Modified header field" x:for-anchor=""/>
305  <x:anchor-alias value="Last-Modified"/>
307   The "Last-Modified" header field in a response provides a timestamp
308   indicating the date and time at which the origin server believes the
309   selected representation was last modified, as determined at the conclusion
310   of handling the request.
312<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Last-Modified"/>
313  <x:ref>Last-Modified</x:ref> = <x:ref>HTTP-date</x:ref>
316   An example of its use is
318<figure><artwork type="example">
319  Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
322<section title="Generation" anchor="lastmod.generation">
324   An origin server &SHOULD; send Last-Modified for any selected
325   representation for which a last modification date can be reasonably
326   and consistently determined, since its use in conditional requests
327   and evaluating cache freshness (&caching;) results in a substantial
328   reduction of HTTP traffic on the Internet and can be a significant
329   factor in improving service scalability and reliability.
332   A representation is typically the sum of many parts behind the
333   resource interface.  The last-modified time would usually be
334   the most recent time that any of those parts were changed.
335   How that value is determined for any given resource is an
336   implementation detail beyond the scope of this specification.
337   What matters to HTTP is how recipients of the Last-Modified
338   header field can use its value to make conditional requests
339   and test the validity of locally cached responses.
342   An origin server &SHOULD; obtain the Last-Modified value of the
343   representation as close as possible to the time that it generates the
344   <x:ref>Date</x:ref> field value for its response. This allows a recipient to
345   make an accurate assessment of the representation's modification time,
346   especially if the representation changes near the time that the
347   response is generated.
350   An origin server with a clock &MUST-NOT; send a Last-Modified date
351   that is later than the server's time of message origination (<x:ref>Date</x:ref>).
352   If the last modification time is derived from implementation-specific
353   metadata that evaluates to some time in the future, according to the
354   origin server's clock, then the origin server &MUST; replace that
355   value with the message origination date. This prevents a future
356   modification date from having an adverse impact on cache validation.
359   An origin server without a clock &MUST-NOT; assign Last-Modified
360   values to a response unless these values were associated
361   with the resource by some other system or user with a reliable clock.
365<section title="Comparison" anchor="lastmod.comparison">
367   A Last-Modified time, when used as a validator in a request, is
368   implicitly weak unless it is possible to deduce that it is strong,
369   using the following rules:
370  <list style="symbols">
371     <t>The validator is being compared by an origin server to the
372        actual current validator for the representation and,</t>
373     <t>That origin server reliably knows that the associated representation did
374        not change twice during the second covered by the presented
375        validator.</t>
376  </list>
379   or
380  <list style="symbols">
381     <t>The validator is about to be used by a client in an <x:ref>If-Modified-Since</x:ref>,
382        <x:ref>If-Unmodified-Since</x:ref> header field, because the client has
383        a cache entry, or <x:ref>If-Range</x:ref> for the associated
384        representation, and</t>
385     <t>That cache entry includes a <x:ref>Date</x:ref> value, which gives the
386        time when the origin server sent the original response, and</t>
387     <t>The presented Last-Modified time is at least 60 seconds before
388        the Date value.</t>
389  </list>
392   or
393  <list style="symbols">
394     <t>The validator is being compared by an intermediate cache to the
395        validator stored in its cache entry for the representation, and</t>
396     <t>That cache entry includes a <x:ref>Date</x:ref> value, which gives the
397        time 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>
403   This method relies on the fact that if two different responses were
404   sent by the origin server during the same second, but both had the
405   same Last-Modified time, then at least one of those responses would
406   have a <x:ref>Date</x:ref> value equal to its Last-Modified time. The
407   arbitrary 60-second limit guards against the possibility that the Date and
408   Last-Modified values are generated from different clocks, or at somewhat
409   different times during the preparation of the response. An
410   implementation &MAY; use a value larger than 60 seconds, if it is
411   believed that 60 seconds is too short.
416<section title="ETag" anchor="header.etag">
417  <iref primary="true" item="ETag header field" x:for-anchor=""/>
418  <x:anchor-alias value="ETag"/>
419  <x:anchor-alias value="entity-tag"/>
420  <x:anchor-alias value="opaque-tag"/>
421  <x:anchor-alias value="weak"/>
422  <x:anchor-alias value="etagc"/>
424   The "ETag" header field in a response provides the current entity-tag for
425   the selected representation, as determined at the conclusion of handling
426   the request.
427   An entity-tag is an opaque validator for differentiating between
428   multiple representations of the same resource, regardless of whether
429   those multiple representations are due to resource state changes over
430   time, content negotiation resulting in multiple representations being
431   valid at the same time, or both. An entity-tag consists of an opaque
432   quoted string, possibly prefixed by a weakness indicator.
434<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"/>
435  <x:ref>ETag</x:ref>       = <x:ref>entity-tag</x:ref>
437  <x:ref>entity-tag</x:ref> = [ <x:ref>weak</x:ref> ] <x:ref>opaque-tag</x:ref>
438  <x:ref>weak</x:ref>       = <x:abnf-char-sequence>"W/"</x:abnf-char-sequence> ; "W/", case-sensitive
439  <x:ref>opaque-tag</x:ref> = <x:ref>DQUOTE</x:ref> *<x:ref>etagc</x:ref> <x:ref>DQUOTE</x:ref>
440  <x:ref>etagc</x:ref>      = %x21 / %x23-7E / <x:ref>obs-text</x:ref>
441             ; <x:ref>VCHAR</x:ref> except double quotes, plus obs-text
444  <t>
445    &Note; Previously, opaque-tag was defined to be a quoted-string
446    (<xref target="RFC2616" x:fmt="," x:sec="3.11"/>), thus some recipients
447    might perform backslash unescaping. Servers therefore ought to avoid
448    backslash characters in entity tags.
449  </t>
452   An entity-tag can be more reliable for validation than a modification
453   date in situations where it is inconvenient to store modification
454   dates, where the one-second resolution of HTTP date values is not
455   sufficient, or where modification dates are not consistently maintained.
458  Examples:
460<artwork type="example">
461  ETag: "xyzzy"
462  ETag: W/"xyzzy"
463  ETag: ""
466   An entity-tag can be either a weak or strong validator, with
467   strong being the default.  If an origin server provides an entity-tag
468   for a representation and the generation of that entity-tag does not satisfy
469   all of the characteristics of a strong validator
470   (<xref target="weak.and.strong.validators"/>), then the origin server
471   &MUST; mark the entity-tag as weak by prefixing its opaque value
472   with "W/" (case-sensitive).
475<section title="Generation" anchor="entity.tag.generation">
477   The principle behind entity-tags is that only the service author
478   knows the implementation of a resource well enough to select the
479   most accurate and efficient validation mechanism for that resource,
480   and that any such mechanism can be mapped to a simple sequence of
481   octets for easy comparison.  Since the value is opaque, there is no
482   need for the client to be aware of how each entity-tag is constructed.
485   For example, a resource that has implementation-specific versioning
486   applied to all changes might use an internal revision number, perhaps
487   combined with a variance identifier for content negotiation, to
488   accurately differentiate between representations.
489   Other implementations might use a collision-resistant hash of
490   representation content, a combination of various file attributes, or
491   a modification timestamp that has sub-second resolution.
494   An origin server &SHOULD; send ETag for any selected representation
495   for which detection of changes can be reasonably and consistently
496   determined, since the entity-tag's use in conditional requests and
497   evaluating cache freshness (&caching;) can result in a substantial
498   reduction of HTTP network traffic and can be a significant factor in
499   improving service scalability and reliability.
503<section title="Comparison" anchor="entity.tag.comparison">
504  <x:anchor-alias value="validator.comparison"/>
505  <x:anchor-alias value="strong comparison"/>
506  <x:anchor-alias value="weak comparison"/>
508   There are two entity-tag comparison functions, depending
509   on whether the comparison context allows the use of weak validators
510   or not:
511  <list style="symbols">
512     <t><x:dfn>Strong comparison</x:dfn>: two entity-tags are equivalent if both
513        are not weak and their opaque-tags match character-by-character.</t>
514     <t><x:dfn>Weak comparison</x:dfn>: two entity-tags are equivalent if their opaque-tags
515        match character-by-character, regardless of either or both
516        being tagged as "weak".</t>
517  </list>
520   The example below shows the results for a set of entity-tag pairs,
521   and both the weak and strong comparison function results:
523<texttable align="left">
524  <ttcol>ETag 1</ttcol>
525  <ttcol>ETag 2</ttcol>
526  <ttcol>Strong Comparison</ttcol>
527  <ttcol>Weak Comparison</ttcol>
529  <c>W/"1"</c>
530  <c>W/"1"</c>
531  <c>no match</c>
532  <c>match</c>
534  <c>W/"1"</c>
535  <c>W/"2"</c>
536  <c>no match</c>
537  <c>no match</c>
539  <c>W/"1"</c>
540  <c>"1"</c>
541  <c>no match</c>
542  <c>match</c>
544  <c>"1"</c>
545  <c>"1"</c>
546  <c>match</c>
547  <c>match</c>
551<section title="Example: Entity-tags Varying on Content-Negotiated Resources" anchor="example.entity.tag.vs.conneg">
553   Consider a resource that is subject to content negotiation
554   (&content-negotiation;), and where the representations sent in response to
555   a GET request vary based on the <x:ref>Accept-Encoding</x:ref> request
556   header field (&header-accept-encoding;):
558<figure><preamble>>> Request:</preamble><artwork type="message/http; msgtype=&#34;request&#34;"  x:indent-with="  ">
559GET /index HTTP/1.1
561Accept-Encoding: gzip
565   In this case, the response might or might not use the gzip content coding.
566   If it does not, the response might look like:
568<figure><preamble>>> Response:</preamble><artwork type="message/http; msgtype=&#34;response&#34;"  x:indent-with="  ">
569HTTP/1.1 200 OK
570Date: Fri, 26 Mar 2010 00:05:00 GMT
571ETag: "123-a"
572Content-Length: <x:length-of target="exbody"/>
573Vary: Accept-Encoding
574Content-Type: text/plain
576<x:span anchor="exbody">Hello World!
577Hello World!
578Hello World!
579Hello World!
580Hello World!
583   An alternative representation that does use gzip content coding would be:
585<figure><preamble>>> Response:</preamble><artwork type="message/http; msgtype=&#34;response&#34;"  x:indent-with="  ">
586HTTP/1.1 200 OK
587Date: Fri, 26 Mar 2010 00:05:00 GMT
588ETag: "123-b"
589Content-Length: 43
590Vary: Accept-Encoding
591Content-Type: text/plain
592Content-Encoding: gzip
594<spanx>...binary data...</spanx></artwork></figure>
596  <t>
597    &Note; Content codings are a property of the representation data,
598    so a strong entity-tag for a content-encoded representation has to be
599    distinct from the entity tag of an unencoded representation to prevent
600    potential conflicts during cache updates and range requests. In contrast,
601    transfer codings (&transfer-codings;) apply only during message transfer
602    and do not result in distinct entity-tags.
603  </t>
608<section title="When to Use Entity-tags and Last-Modified Dates" anchor="">
610   In <x:ref>200 (OK)</x:ref> responses to GET or HEAD, an origin server:
611  <list style="symbols">
612     <t>&SHOULD; send an entity-tag validator unless it is not feasible to
613        generate one.</t>
615     <t>&MAY; send a weak entity-tag instead of a strong entity-tag, if
616        performance considerations support the use of weak entity-tags,
617        or if it is unfeasible to send a strong entity-tag.</t>
619     <t>&SHOULD; send a <x:ref>Last-Modified</x:ref> value if it is feasible to
620        send one.</t>
621  </list>
624   In other words, the preferred behavior for an origin server
625   is to send both a strong entity-tag and a <x:ref>Last-Modified</x:ref>
626   value in successful responses to a retrieval request.
629   A client:
630  <list style="symbols">
631     <t>&MUST; send that entity-tag in any cache validation request (using
632        <x:ref>If-Match</x:ref> or <x:ref>If-None-Match</x:ref>) if an
633        entity-tag has been provided by the origin server.</t>
635     <t>&SHOULD; send the <x:ref>Last-Modified</x:ref> value in non-subrange
636        cache validation requests (using <x:ref>If-Modified-Since</x:ref>)
637        if only a Last-Modified value has been provided by the origin server.</t>
639     <t>&MAY; send the <x:ref>Last-Modified</x:ref> value in subrange
640        cache validation requests (using <x:ref>If-Unmodified-Since</x:ref>)
641        if only a Last-Modified value has been provided by an HTTP/1.0 origin
642        server. The user agent &SHOULD; provide a way to disable this, in case
643        of difficulty.</t>
645     <t>&SHOULD; send both validators in cache validation requests if both an
646        entity-tag and a <x:ref>Last-Modified</x:ref> value have been provided
647        by the origin server. This allows both HTTP/1.0 and HTTP/1.1 caches to
648        respond appropriately.</t>
649  </list>
654<section title="Precondition Header Fields" anchor="preconditions">
656   This section defines the syntax and semantics of HTTP/1.1 header fields
657   for applying preconditions on requests.
658   <xref target="evaluation"/> defines when the preconditions are applied.
659   <xref target="precedence"/> defines the order of evaluation when more than
660   one precondition is present.
663<section title="If-Match" anchor="header.if-match">
664  <iref primary="true" item="If-Match header field" x:for-anchor=""/>
665  <x:anchor-alias value="If-Match"/>
667   The "If-Match" header field makes the request method conditional on the
668   recipient origin server either having at least one current
669   representation of the target resource, when the field-value is "*", or
670   having a current representation of the target resource that has an
671   entity-tag matching a member of the list of entity-tags provided in the
672   field-value.
675   An origin server &MUST; use the strong comparison function when comparing
676   entity-tags for If-Match (<xref target="entity.tag.comparison"/>), since
677   the client intends this precondition to prevent the method from being
678   applied if there have been any changes to the representation data.
680<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Match"/>
681  <x:ref>If-Match</x:ref> = "*" / 1#<x:ref>entity-tag</x:ref>
684   Examples:
686<figure><artwork type="example">
687  If-Match: "xyzzy"
688  If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
689  If-Match: *
692   If-Match is most often used with state-changing methods (e.g., POST, PUT,
693   DELETE) to prevent accidental overwrites when multiple user agents might be
694   acting in parallel on the same resource (i.e., to prevent the "lost update"
695   problem). It can also be used with safe methods to abort a request if the
696   <x:ref>selected representation</x:ref> does not match one already stored
697   (or partially stored) from a prior request.
700   An origin server that receives an If-Match header field &MUST; evaluate the
701   condition prior to performing the method (<xref target="evaluation"/>).
702   If the field-value is "*", the condition is false if the origin server
703   does not have a current representation for the target resource.
704   If the field-value is a list of entity-tags, the condition is false if
705   none of the listed tags match the entity-tag of the selected representation.
708   An origin server &MUST-NOT; perform the requested method if a received
709   If-Match condition evaluates to false; instead the origin server &MUST;
710   respond with either:
711   a) the <x:ref>412 (Precondition Failed)</x:ref> status code; or,
712   b) one of the <x:ref>2xx (Successful)</x:ref> status codes if the origin
713   server has verified that a state change is being requested and the final
714   state is already reflected in the current state of the target resource
715   (i.e., the change requested by the user agent has already succeeded, but
716   the user agent might not be aware of it, perhaps because the prior response
717   was lost or a compatible change was made by some other user agent).
718   In the latter case, the origin server &MUST-NOT; send a validator header
719   field in the response unless it can verify that the request is a duplicate
720   of an immediately prior change made by the same user agent.
723   The If-Match header field can be ignored by caches and intermediaries
724   because it is not applicable to a stored response.
728<section title="If-None-Match" anchor="header.if-none-match">
729  <iref primary="true" item="If-None-Match header field" x:for-anchor=""/>
730  <x:anchor-alias value="If-None-Match"/>
732   The "If-None-Match" header field makes the request method conditional on
733   a recipient cache or origin server either not having any current
734   representation of the target resource, when the field-value is "*", or
735   having a selected representation with an entity-tag that does not match any
736   of those listed in the field-value.
739   A recipient &MUST; use the weak comparison function when comparing
740   entity-tags for If-None-Match (<xref target="entity.tag.comparison"/>),
741   since weak entity-tags can be used for cache validation even if there have
742   been changes to the representation data.
744<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-None-Match"/>
745  <x:ref>If-None-Match</x:ref> = "*" / 1#<x:ref>entity-tag</x:ref>
748   Examples:
750<figure><artwork type="example">
751  If-None-Match: "xyzzy"
752  If-None-Match: W/"xyzzy"
753  If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
754  If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
755  If-None-Match: *
758   If-None-Match is primarily used in conditional GET requests to enable
759   efficient updates of cached information with a minimum amount of
760   transaction overhead. When a client desires to update one or more stored
761   responses that have entity-tags, the client &SHOULD; generate an
762   If-None-Match header field containing a list of those entity-tags when
763   making a GET request; this allows recipient servers to send a
764   <x:ref>304 (Not Modified)</x:ref> response to indicate when one of those
765   stored responses matches the selected representation.
768   If-None-Match can also be used with a value of "*" to prevent an unsafe
769   request method (e.g., PUT) from inadvertently modifying an existing
770   representation of the target resource when the client believes that
771   the resource does not have a current representation (&safe-methods;).
772   This is a variation on the "lost update" problem that might arise if more
773   than one client attempts to create an initial representation for the target
774   resource.
777   An origin server that receives an If-None-Match header field &MUST;
778   evaluate the condition prior to performing the method
779   (<xref target="evaluation"/>).
780   If the field-value is "*", the condition is false if the origin server
781   has a current representation for the target resource.
782   If the field-value is a list of entity-tags, the condition is false if
783   one of the listed tags match the entity-tag of the selected representation.
786   An origin server &MUST-NOT; perform the requested method if the condition
787   evaluates to false; instead, the origin server &MUST; respond with either
788   a) the <x:ref>304 (Not Modified)</x:ref> status code if the request method
789   is GET or HEAD; or,
790   b) the <x:ref>412 (Precondition Failed)</x:ref> status code for all other
791   request methods.
794   Requirements on cache handling of a received If-None-Match header field
795   are defined in &cache-validation-received;.
799<section title="If-Modified-Since" anchor="header.if-modified-since">
800  <iref primary="true" item="If-Modified-Since header field" x:for-anchor=""/>
801  <x:anchor-alias value="If-Modified-Since"/>
803   The "If-Modified-Since" header field makes a GET or HEAD request method
804   conditional on the selected representation's modification date being more
805   recent than the date provided in the field-value. Transfer of the selected
806   representation's data is avoided if that data has not changed.
808<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Modified-Since"/>
809  <x:ref>If-Modified-Since</x:ref> = <x:ref>HTTP-date</x:ref>
812   An example of the field is:
814<figure><artwork type="example">
815  If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
818   A recipient &MUST; ignore If-Modified-Since if the request contains an
819   <x:ref>If-None-Match</x:ref> header field; the condition in
820   <x:ref>If-None-Match</x:ref> is considered to be a more accurate
821   replacement for the condition in If-Modified-Since and the two are only
822   combined for the sake of interoperating with older intermediaries that
823   might not implement <x:ref>If-None-Match</x:ref>.
826   A recipient &MUST; ignore the If-Modified-Since header field if the
827   received field-value is not a valid HTTP-date, or if the request method
828   is neither GET nor HEAD.
831   A recipient &MUST; interpret an If-Modified-Since field-value's timestamp
832   in terms of the origin server's clock.
835   If-Modified-Since is typically used for two distinct purposes:
836   1) to allow efficient updates of a cached representation that does not
837   have an entity-tag; and,
838   2) to limit the scope of a web traversal to resources that have recently
839   changed.
842   When used for cache updates, a cache will typically use the value of the
843   cached message's <x:ref>Last-Modified</x:ref> field to generate the field
844   value of If-Modified-Since. This behavior is most interoperable for cases
845   where clocks are poorly synchronized or when the server has chosen to only
846   honor exact timestamp matches (due to a problem with Last-Modified dates
847   that appear to go "back in time" when the origin server's clock is
848   corrected or a representation is restored from an archived backup).
849   However, caches occasionally generate the field value based on other data,
850   such as the <x:ref>Date</x:ref> header field of the cached message or the
851   local clock time that the message was received, particularly when the
852   cached message does not contain a <x:ref>Last-Modified</x:ref> field.
855   When used for limiting the scope of retrieval to a recent time window, a
856   user agent will generate an If-Modified-Since field value based on either
857   its own local clock or a <x:ref>Date</x:ref> header field received from the
858   server in a prior response. Origin servers that choose an exact timestamp
859   match based on the selected representation's <x:ref>Last-Modified</x:ref>
860   field will not be able to help the user agent limit its data transfers to
861   only those changed during the specified window.
864   An origin server that receives an If-Modified-Since header field &SHOULD;
865   evaluate the condition prior to performing the method
866   (<xref target="evaluation"/>).
867   The origin server &SHOULD-NOT; perform the requested method if the selected
868   representation's last modification date is earlier than or equal to the
869   date provided in the field-value; instead, the origin server &SHOULD;
870   generate a <x:ref>304 (Not Modified)</x:ref> response, including only those
871   metadata that are useful for identifying or updating a previously cached
872   response.
875   Requirements on cache handling of a received If-Modified-Since header field
876   are defined in &cache-validation-received;.
880<section title="If-Unmodified-Since" anchor="header.if-unmodified-since">
881  <iref primary="true" item="If-Unmodified-Since header field" x:for-anchor=""/>
882  <x:anchor-alias value="If-Unmodified-Since"/>
884   The "If-Unmodified-Since" header field makes the request method conditional
885   on the selected representation's last modification date being earlier than or
886   equal to the date provided in the field-value. This field accomplishes the
887   same purpose as <x:ref>If-Match</x:ref> for cases where the user agent does
888   not have an entity-tag for the representation.
890<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Unmodified-Since"/>
891  <x:ref>If-Unmodified-Since</x:ref> = <x:ref>HTTP-date</x:ref>
894   An example of the field is:
896<figure><artwork type="example">
897  If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
900   A recipient &MUST; ignore If-Unmodified-Since if the request contains an
901   <x:ref>If-Match</x:ref> header field; the condition in
902   <x:ref>If-Match</x:ref> is considered to be a more accurate replacement for
903   the condition in If-Unmodified-Since and the two are only combined for the
904   sake of interoperating with older intermediaries that might not implement
905   <x:ref>If-Match</x:ref>.
908   A recipient &MUST; ignore the If-Unmodified-Since header field if the
909   received field-value is not a valid HTTP-date.
912   A recipient &MUST; interpret an If-Unmodified-Since field-value's timestamp
913   in terms of the origin server's clock.
916   If-Unmodified-Since is most often used with state-changing methods
917   (e.g., POST, PUT, DELETE) to prevent accidental overwrites when multiple
918   user agents might be acting in parallel on a resource that does
919   not supply entity-tags with its representations (i.e., to prevent the
920   "lost update" problem). It can also be used with safe methods to abort a
921   request if the <x:ref>selected representation</x:ref> does not match one
922   already stored (or partially stored) from a prior request.
925   An origin server that receives an If-Unmodified-Since header field &MUST;
926   evaluate the condition prior to performing the method
927   (<xref target="evaluation"/>).
928   The origin server &MUST-NOT; perform the requested method if the selected
929   representation's last modification date is more recent than the date
930   provided in the field-value; instead the
931   origin server &MUST; respond with either:
932   a) the <x:ref>412 (Precondition Failed)</x:ref> status code; or,
933   b) one of the <x:ref>2xx (Successful)</x:ref> status codes if the origin
934   server has verified that a state change is being requested and the final
935   state is already reflected in the current state of the target resource
936   (i.e., the change requested by the user agent has already succeeded, but
937   the user agent might not be aware of that because the prior response message
938   was lost or a compatible change was made by some other user agent).
939   In the latter case, the origin server &MUST-NOT; send a validator header
940   field in the response unless it can verify that the request is a duplicate
941   of an immediately prior change made by the same user agent.
944   The If-Unmodified-Since header field can be ignored by caches and
945   intermediaries because it is not applicable to a stored response.
949<section title="If-Range" anchor="header.if-range">
951   The "If-Range" header field provides a special conditional request
952   mechanism that is similar to the <x:ref>If-Match</x:ref> and
953   <x:ref>If-Unmodified-Since</x:ref> header fields but instructs the
954   recipient to ignore the <x:ref>Range</x:ref> header field if the validator
955   doesn't match, resulting in transfer of the new selected representation
956   instead of a 412 response. If-Range is defined in &header-if-range;.
961<section title="Status Code Definitions" anchor="status.code.definitions">
962<section title="304 Not Modified" anchor="status.304">
963  <iref primary="true" item="304 Not Modified (status code)" x:for-anchor=""/>
964  <x:anchor-alias value="304"/>
965  <x:anchor-alias value="304 (Not Modified)"/>
967   The <x:dfn>304 (Not Modified)</x:dfn> status code indicates that a
968   conditional GET or HEAD request has been
969   received and would have resulted in a <x:ref>200 (OK)</x:ref> response
970   if it were not for the fact that the condition has evaluated to false.
971   In other words, there is no need for the server to transfer a
972   representation of the target resource because the request indicates that
973   the client, which made the request conditional, already has a valid
974   representation; the server is therefore redirecting the client to make
975   use of that stored representation as if it were the payload of a
976   <x:ref>200 (OK)</x:ref> response.
979   The server generating a 304 response &MUST; generate any of the following
980   header fields that would have been sent in a <x:ref>200 (OK)</x:ref>
981   response to the same request:
982   <x:ref>Cache-Control</x:ref>,
983   <x:ref>Content-Location</x:ref>,
984   <x:ref>Date</x:ref>,
985   <x:ref>ETag</x:ref>,
986   <x:ref>Expires</x:ref>, and
987   <x:ref>Vary</x:ref>.
990   Since the goal of a 304 response is to minimize information transfer
991   when the recipient already has one or more cached representations,
992   a sender &SHOULD-NOT; generate representation metadata other
993   than the above listed fields unless said metadata exists for the
994   purpose of guiding cache updates (e.g., <x:ref>Last-Modified</x:ref> might
995   be useful if the response does not have an <x:ref>ETag</x:ref> field).
998   Requirements on a cache that receives a 304 response are defined in
999   &freshening-responses;. If the conditional request originated with an
1000   outbound client, such as a user agent with its own cache sending a
1001   conditional GET to a shared proxy, then the proxy &SHOULD; forward the
1002   304 response to that client.
1005   A 304 response cannot contain a message-body; it is always
1006   terminated by the first empty line after the header fields.
1010<section title="412 Precondition Failed" anchor="status.412">
1011  <iref primary="true" item="412 Precondition Failed (status code)" x:for-anchor=""/>
1012  <x:anchor-alias value="412 (Precondition Failed)"/>
1014   The <x:dfn>412 (Precondition Failed)</x:dfn> status code indicates that one
1015   or more conditions given in the request header fields evaluated to false
1016   when tested on the server. This response code allows the client to place
1017   preconditions on the current resource state (its current representations
1018   and metadata) and thus prevent the request method from being applied if the
1019   target resource is in an unexpected state.
1024<section title="Evaluation" anchor="evaluation">
1026   Except when excluded below, a recipient cache or origin server &MUST;
1027   evaluate received request preconditions after it has successfully performed
1028   its normal request checks and just before it would perform the action
1029   associated with the request method.
1030   A server &MUST; ignore all received preconditions if its response to the
1031   same request without those conditions would have been a status code other
1032   than a <x:ref>2xx</x:ref> or <x:ref>412 (Precondition Failed)</x:ref>.
1033   In other words, redirects and failures take precedence over the evaluation
1034   of preconditions in conditional requests.
1037   A server that is not the origin server for the target resource and cannot
1038   act as a cache for requests on the target resource &MUST-NOT; evaluate the
1039   conditional request header fields defined by this specification, and
1040   &MUST; forward them if the request is forwarded, since the generating
1041   client intends that they be evaluated by a server that can provide a
1042   current representation.
1043   Likewise, a server &MUST; ignore the conditional request header fields
1044   defined by this specification when received with a request method that does
1045   not involve the selection or modification of a
1046   <x:ref>selected representation</x:ref>, such as CONNECT, OPTIONS, or TRACE.
1049   Conditional request header fields that are defined by extensions to HTTP
1050   might place conditions on all recipients, on the state of the target
1051   resource in general, or on a group of resources. For instance, the "If"
1052   header field in WebDAV can make a request conditional on various aspects
1053   of multiple resources, such as locks, if the recipient understands and
1054   implements that field (<xref target="RFC4918" x:fmt="," x:sec="10.4"/>).
1057   Although conditional request header fields are defined as being usable with
1058   the HEAD method (to keep HEAD's semantics consistent with those of GET),
1059   there is no point in sending a conditional HEAD because a successful
1060   response is around the same size as a <x:ref>304 (Not Modified)</x:ref>
1061   response and more useful than a <x:ref>412 (Precondition Failed)</x:ref>
1062   response.
1066<section title="Precedence" anchor="precedence">
1068   When more than one conditional request header field is present in a request,
1069   the order in which the fields are evaluated becomes important. In practice,
1070   the fields defined in this document are consistently implemented in a
1071   single, logical order, since "lost update" preconditions have more strict
1072   requirements than cache validation, a validated cache is more efficient
1073   than a partial response, and entity tags are presumed to be more accurate
1074   than date validators.
1077   A recipient cache or origin server &MUST; evaluate the request
1078   preconditions defined by this specification in the following order:
1079   <list style="numbers">
1080     <t anchor="precedence1">When recipient is the origin server and
1081       <x:ref>If-Match</x:ref> is present,
1082       evaluate the <x:ref>If-Match</x:ref> precondition:
1083       <list style="symbols">
1084         <t>if true, continue to step <xref target="precedence3" format="counter"/></t>
1085         <t>if false, respond <x:ref>412 (Precondition Failed)</x:ref> unless
1086            it can be determined that the state-changing request has already
1087            succeeded (see <xref target="header.if-match"/>)</t>
1088       </list>
1089     </t>
1090     <t anchor="precedence2">When recipient is the origin server,
1091       <x:ref>If-Match</x:ref> is not present, and
1092       <x:ref>If-Unmodified-Since</x:ref> is present,
1093       evaluate the <x:ref>If-Unmodified-Since</x:ref> precondition:
1094       <list style="symbols">
1095         <t>if true, continue to step <xref target="precedence3" format="counter"/></t>
1096         <t>if false, respond <x:ref>412 (Precondition Failed)</x:ref> unless
1097            it can be determined that the state-changing request has already
1098            succeeded (see <xref target="header.if-unmodified-since"/>)</t>
1099       </list>
1100     </t>
1101     <t anchor="precedence3">When <x:ref>If-None-Match</x:ref> is present,
1102       evaluate the <x:ref>If-None-Match</x:ref> precondition:
1103       <list style="symbols">
1104         <t>if true, continue to step <xref target="precedence5" format="counter"/></t>
1105         <t>if false for GET/HEAD, respond <x:ref>304 (Not Modified)</x:ref></t>
1106         <t>if false for other methods, respond <x:ref>412 (Precondition Failed)</x:ref></t>
1107       </list>
1108     </t>
1109     <t anchor="precedence4">When the method is GET or HEAD,
1110       <x:ref>If-None-Match</x:ref> is not present, and
1111       <x:ref>If-Modified-Since</x:ref> is present,
1112       evaluate the <x:ref>If-Modified-Since</x:ref> precondition:
1113       <list style="symbols">
1114         <t>if true, continue to step <xref target="precedence5" format="counter"/></t>
1115         <t>if false, respond <x:ref>304 (Not Modified)</x:ref></t>
1116       </list>
1117     </t>
1118     <t anchor="precedence5">When the method is GET and both
1119       <x:ref>Range</x:ref> and <x:ref>If-Range</x:ref> are present,
1120       evaluate the <x:ref>If-Range</x:ref> precondition:
1121       <list style="symbols">
1122         <t>if the validator matches and the Range specification is
1123            applicable to the selected representation, respond
1124            <x:ref>206 (Partial Content)</x:ref> <xref target="RFC7233"/></t>
1125       </list>
1126     </t>
1127     <t anchor="precedencelast">Otherwise,
1128       <list style="symbols">
1129         <t>all conditions are met, so perform the requested action and
1130            respond according to its success or failure.</t>
1131       </list>
1132     </t>
1133   </list>
1136   Any extension to HTTP/1.1 that defines additional conditional request
1137   header fields ought to define its own expectations regarding the order
1138   for evaluating such fields in relation to those defined in this document
1139   and other conditionals that might be found in practice.
1143<section title="IANA Considerations" anchor="IANA.considerations">
1145<section title="Status Code Registration" anchor="status.code.registration">
1147   The "Hypertext Transfer Protocol (HTTP) Status Code Registry" located at <eref target=""/>
1148   has been updated with the registrations below:
1150<?BEGININC p4-conditional.iana-status-codes ?>
1151<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
1152<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
1153   <ttcol>Value</ttcol>
1154   <ttcol>Description</ttcol>
1155   <ttcol>Reference</ttcol>
1156   <c>304</c>
1157   <c>Not Modified</c>
1158   <c>
1159      <xref target="status.304"/>
1160   </c>
1161   <c>412</c>
1162   <c>Precondition Failed</c>
1163   <c>
1164      <xref target="status.412"/>
1165   </c>
1168<?ENDINC p4-conditional.iana-status-codes ?>
1171<section title="Header Field Registration" anchor="header.field.registration">
1173   HTTP header fields are registered within the "Message Headers" registry
1174   maintained at
1175   <eref target=""/>.
1178   This document defines the following HTTP header fields, so the
1179   "Permanent Message Header Field Names" registry has been updated
1180   accordingly (see <xref target="BCP90"/>).
1182<?BEGININC p4-conditional.iana-headers ?>
1183<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
1184<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
1185   <ttcol>Header Field Name</ttcol>
1186   <ttcol>Protocol</ttcol>
1187   <ttcol>Status</ttcol>
1188   <ttcol>Reference</ttcol>
1190   <c>ETag</c>
1191   <c>http</c>
1192   <c>standard</c>
1193   <c>
1194      <xref target="header.etag"/>
1195   </c>
1196   <c>If-Match</c>
1197   <c>http</c>
1198   <c>standard</c>
1199   <c>
1200      <xref target="header.if-match"/>
1201   </c>
1202   <c>If-Modified-Since</c>
1203   <c>http</c>
1204   <c>standard</c>
1205   <c>
1206      <xref target="header.if-modified-since"/>
1207   </c>
1208   <c>If-None-Match</c>
1209   <c>http</c>
1210   <c>standard</c>
1211   <c>
1212      <xref target="header.if-none-match"/>
1213   </c>
1214   <c>If-Unmodified-Since</c>
1215   <c>http</c>
1216   <c>standard</c>
1217   <c>
1218      <xref target="header.if-unmodified-since"/>
1219   </c>
1220   <c>Last-Modified</c>
1221   <c>http</c>
1222   <c>standard</c>
1223   <c>
1224      <xref target="header.last-modified"/>
1225   </c>
1228<?ENDINC p4-conditional.iana-headers ?>
1230   The change controller is: "IETF ( - Internet Engineering Task Force".
1235<section title="Security Considerations" anchor="security.considerations">
1237   This section is meant to inform developers, information providers, and
1238   users of known security concerns specific to the HTTP conditional
1239   request mechanisms. More general security considerations are addressed
1240   in HTTP messaging &messaging; and semantics &semantics;.
1243   The validators defined by this specification are not intended to ensure
1244   the validity of a representation, guard against malicious changes, or
1245   detect man-in-the-middle attacks. At best, they enable more efficient cache
1246   updates and optimistic concurrent writes when all participants are behaving
1247   nicely. At worst, the conditions will fail and the client will receive a
1248   response that is no more harmful than an HTTP exchange without conditional
1249   requests.
1252   An entity-tag can be abused in ways that create privacy risks. For example,
1253   a site might deliberately construct a semantically invalid entity-tag that
1254   is unique to the user or user agent, send it in a cacheable response with a
1255   long freshness time, and then read that entity-tag in later conditional
1256   requests as a means of re-identifying that user or user agent. Such an
1257   identifying tag would become a persistent identifier for as long as the
1258   user agent retained the original cache entry. User agents that cache
1259   representations ought to ensure that the cache is cleared or replaced
1260   whenever the user performs privacy-maintaining actions, such as clearing
1261   stored cookies or changing to a private browsing mode.
1265<section title="Acknowledgments" anchor="acks">
1267  See &acks;.
1273<references title="Normative References">
1275<reference anchor="RFC7230">
1276  <front>
1277    <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
1278    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1279      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1280      <address><email></email></address>
1281    </author>
1282    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1283      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1284      <address><email></email></address>
1285    </author>
1286    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1287  </front>
1288  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
1289  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
1292<reference anchor="RFC7231">
1293  <front>
1294    <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
1295    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1296      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1297      <address><email></email></address>
1298    </author>
1299    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1300      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1301      <address><email></email></address>
1302    </author>
1303    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1304  </front>
1305  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;"/>
1306  <x:source href="p2-semantics.xml" basename="p2-semantics">
1307    <x:defines>2xx</x:defines>
1308    <x:defines>2xx (Successful)</x:defines>
1309    <x:defines>200 (OK)</x:defines>
1310    <x:defines>204 (No Content)</x:defines>
1311    <x:defines>Accept-Encoding</x:defines>
1312    <x:defines>Content-Location</x:defines>
1313    <x:defines>Content-Type</x:defines>
1314    <x:defines>Date</x:defines>
1315    <x:defines>Location</x:defines>
1316    <x:defines>Vary</x:defines>
1317    <x:defines>selected representation</x:defines>
1318  </x:source>
1321<reference anchor="RFC7233">
1322  <front>
1323    <title>Hypertext Transfer Protocol (HTTP/1.1): Range Requests</title>
1324    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1325      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1326      <address><email></email></address>
1327    </author>
1328    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1329      <organization abbrev="W3C">World Wide Web Consortium</organization>
1330      <address><email></email></address>
1331    </author>
1332    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1333      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1334      <address><email></email></address>
1335    </author>
1336    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1337  </front>
1338  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
1339  <x:source href="p5-range.xml" basename="p5-range">
1340    <x:defines>If-Range</x:defines>
1341    <x:defines>Range</x:defines>
1342    <x:defines>206 (Partial Content)</x:defines>
1343  </x:source>
1346<reference anchor="RFC7234">
1347  <front>
1348    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
1349    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1350      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
1351      <address><email></email></address>
1352    </author>
1353    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
1354      <organization>Akamai</organization>
1355      <address><email></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></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    <x:defines>Cache-Control</x:defines>
1366    <x:defines>Expires</x:defines>
1367  </x:source>
1370<reference anchor="RFC2119">
1371  <front>
1372    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
1373    <author initials="S." surname="Bradner" fullname="Scott Bradner">
1374      <organization>Harvard University</organization>
1375      <address><email></email></address>
1376    </author>
1377    <date month="March" year="1997"/>
1378  </front>
1379  <seriesInfo name="BCP" value="14"/>
1380  <seriesInfo name="RFC" value="2119"/>
1383<reference anchor="RFC5234">
1384  <front>
1385    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
1386    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
1387      <organization>Brandenburg InternetWorking</organization>
1388      <address>
1389        <email></email>
1390      </address> 
1391    </author>
1392    <author initials="P." surname="Overell" fullname="Paul Overell">
1393      <organization>THUS plc.</organization>
1394      <address>
1395        <email></email>
1396      </address>
1397    </author>
1398    <date month="January" year="2008"/>
1399  </front>
1400  <seriesInfo name="STD" value="68"/>
1401  <seriesInfo name="RFC" value="5234"/>
1406<references title="Informative References">
1408<reference anchor="RFC2616">
1409  <front>
1410    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
1411    <author initials="R." surname="Fielding" fullname="R. Fielding">
1412      <organization>University of California, Irvine</organization>
1413      <address><email></email></address>
1414    </author>
1415    <author initials="J." surname="Gettys" fullname="J. Gettys">
1416      <organization>W3C</organization>
1417      <address><email></email></address>
1418    </author>
1419    <author initials="J." surname="Mogul" fullname="J. Mogul">
1420      <organization>Compaq Computer Corporation</organization>
1421      <address><email></email></address>
1422    </author>
1423    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
1424      <organization>MIT Laboratory for Computer Science</organization>
1425      <address><email></email></address>
1426    </author>
1427    <author initials="L." surname="Masinter" fullname="L. Masinter">
1428      <organization>Xerox Corporation</organization>
1429      <address><email></email></address>
1430    </author>
1431    <author initials="P." surname="Leach" fullname="P. Leach">
1432      <organization>Microsoft Corporation</organization>
1433      <address><email></email></address>
1434    </author>
1435    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
1436      <organization>W3C</organization>
1437      <address><email></email></address>
1438    </author>
1439    <date month="June" year="1999"/>
1440  </front>
1441  <seriesInfo name="RFC" value="2616"/>
1444<reference anchor='BCP90'>
1445  <front>
1446    <title>Registration Procedures for Message Header Fields</title>
1447    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
1448      <organization>Nine by Nine</organization>
1449      <address><email></email></address>
1450    </author>
1451    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
1452      <organization>BEA Systems</organization>
1453      <address><email></email></address>
1454    </author>
1455    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
1456      <organization>HP Labs</organization>
1457      <address><email></email></address>
1458    </author>
1459    <date year='2004' month='September' />
1460  </front>
1461  <seriesInfo name='BCP' value='90' />
1462  <seriesInfo name='RFC' value='3864' />
1465<reference anchor='RFC4918'>
1466  <front>
1467    <title>HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)</title>
1468    <author initials="L.M." surname="Dusseault" fullname="Lisa Dusseault" role="editor" >
1469      <organization abbrev="CommerceNet">CommerceNet</organization>
1470      <address><email></email></address>
1471    </author>
1472    <date month="June" year="2007" />
1473  </front>
1474  <seriesInfo name='RFC' value='4918' />
1478<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
1480  The definition of validator weakness has been expanded and clarified.
1481  (<xref target="weak.and.strong.validators" />)
1484  Weak entity-tags are now allowed in all requests except range requests.
1485  (Sections <xref target="weak.and.strong.validators" format="counter"/> and
1486  <xref target="header.if-none-match" format="counter"/>)
1489  The <x:ref>ETag</x:ref> header field ABNF has been changed to not use
1490  quoted-string, thus avoiding escaping issues.
1491  (<xref target="header.etag" />)
1494  ETag is defined to provide an entity tag for the selected representation,
1495  thereby clarifying what it applies to in various situations (such as a
1496  PUT response).
1497  (<xref target="header.etag" />)
1500  The precedence for evaluation of conditional requests has been defined.
1501  (<xref target="precedence" />)
1505<section title="Imported ABNF" anchor="imported.abnf">
1506  <x:anchor-alias value="ALPHA"/>
1507  <x:anchor-alias value="CR"/>
1508  <x:anchor-alias value="DIGIT"/>
1509  <x:anchor-alias value="DQUOTE"/>
1510  <x:anchor-alias value="LF"/>
1511  <x:anchor-alias value="OCTET"/>
1512  <x:anchor-alias value="VCHAR"/>
1513  <x:anchor-alias value="core.rules"/>
1514  <x:anchor-alias value="obs-text"/>
1515  <x:anchor-alias value="OWS"/>
1516  <x:anchor-alias value="HTTP-date"/>
1518  The following core rules are included by
1519  reference, as defined in <xref target="RFC5234" x:fmt="of" x:sec="B.1"/>:
1520  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
1521  DIGIT (decimal 0-9), DQUOTE (double quote),
1522  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
1523  OCTET (any 8-bit sequence of data), SP (space), and
1524  VCHAR (any visible US-ASCII character).
1527  The rules below are defined in <xref target="RFC7230"/>:
1529<figure><artwork type="abnf2616">
1530  <x:ref>OWS</x:ref>           = &lt;OWS, see &whitespace;&gt;
1531  <x:ref>obs-text</x:ref>      = &lt;obs-text, see &field-components;&gt;
1534  The rules below are defined in other parts:
1536<figure><artwork type="abnf2616">
1537  <x:ref>HTTP-date</x:ref>     = &lt;HTTP-date, see &http-date;&gt;
1541<?BEGININC p4-conditional.abnf-appendix ?>
1542<section xmlns:x="" title="Collected ABNF" anchor="collected.abnf">
1544  In the collected ABNF below, list rules are expanded as per <xref target="RFC7230" x:rel="#notation"/>.
1546<artwork type="abnf" name="p4-conditional.parsed-abnf">
1547<x:ref>ETag</x:ref> = entity-tag
1549<x:ref>HTTP-date</x:ref> = &lt;HTTP-date, see [RFC7231], Section;
1551<x:ref>If-Match</x:ref> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1552 entity-tag ] ) )
1553<x:ref>If-Modified-Since</x:ref> = HTTP-date
1554<x:ref>If-None-Match</x:ref> = "*" / ( *( "," OWS ) entity-tag *( OWS "," [ OWS
1555 entity-tag ] ) )
1556<x:ref>If-Unmodified-Since</x:ref> = HTTP-date
1558<x:ref>Last-Modified</x:ref> = HTTP-date
1560<x:ref>OWS</x:ref> = &lt;OWS, see [RFC7230], Section 3.2.3&gt;
1562<x:ref>entity-tag</x:ref> = [ weak ] opaque-tag
1563<x:ref>etagc</x:ref> = "!" / %x23-7E ; '#'-'~'
1564 / obs-text
1566<x:ref>obs-text</x:ref> = &lt;obs-text, see [RFC7230], Section 3.2.6&gt;
1567<x:ref>opaque-tag</x:ref> = DQUOTE *etagc DQUOTE
1569<x:ref>weak</x:ref> = %x57.2F ; W/
1573<?ENDINC p4-conditional.abnf-appendix ?>
Note: See TracBrowser for help on using the repository browser.