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

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

Note change for [1223], see #89.

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