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

Last change on this file since 172 was 172, checked in by fielding@…, 12 years ago

editorial: replace redundant "the HTTP protocol" phrases or rephrase

  • Property svn:eol-style set to native
File size: 51.4 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 "January">
16  <!ENTITY ID-YEAR "2008">
17  <!ENTITY messaging                  "<xref target='Part1' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
18  <!ENTITY caching                    "<xref target='Part6' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
19  <!ENTITY header-if-range            "<xref target='Part5' x:rel='#header.if-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY header-range               "<xref target='Part5' x:rel='#header.range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY header-vary                "<xref target='Part6' x:rel='#header.vary' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY clockless                  "<xref target='Part1' x:rel='#clockless.origin.server.operation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23]>
24<?rfc toc="yes" ?>
25<?rfc symrefs="yes" ?>
26<?rfc sortrefs="yes" ?>
27<?rfc compact="yes"?>
28<?rfc subcompact="no" ?>
29<?rfc linkmailto="no" ?>
30<?rfc editing="no" ?>
31<?rfc-ext allow-markup-in-artwork="yes" ?>
32<?rfc-ext include-references-in-index="yes" ?>
33<rfc obsoletes="2616" category="std"
34     ipr="full3978" docName="draft-ietf-httpbis-p4-conditional-&ID-VERSION;"
35     xmlns:x='http://purl.org/net/xml2rfc/ext'>
36<front>
37
38  <title abbrev="HTTP/1.1, Part 4">HTTP/1.1, part 4: Conditional Requests</title>
39
40  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
41    <organization abbrev="Day Software">Day Software</organization>
42    <address>
43      <postal>
44        <street>23 Corporate Plaza DR, Suite 280</street>
45        <city>Newport Beach</city>
46        <region>CA</region>
47        <code>92660</code>
48        <country>USA</country>
49      </postal>
50      <phone>+1-949-706-5300</phone>
51      <facsimile>+1-949-706-5305</facsimile>
52      <email>fielding@gbiv.com</email>
53      <uri>http://roy.gbiv.com/</uri>
54    </address>
55  </author>
56
57  <author initials="J." surname="Gettys" fullname="Jim Gettys">
58    <organization>One Laptop per Child</organization>
59    <address>
60      <postal>
61        <street>21 Oak Knoll Road</street>
62        <city>Carlisle</city>
63        <region>MA</region>
64        <code>01741</code>
65        <country>USA</country>
66      </postal>
67      <email>jg@laptop.org</email>
68      <uri>http://www.laptop.org/</uri>
69    </address>
70  </author>
71 
72  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
73    <organization abbrev="HP">Hewlett-Packard Company</organization>
74    <address>
75      <postal>
76        <street>HP Labs, Large Scale Systems Group</street>
77        <street>1501 Page Mill Road, MS 1177</street>
78        <city>Palo Alto</city>
79        <region>CA</region>
80        <code>94304</code>
81        <country>USA</country>
82      </postal>
83      <email>JeffMogul@acm.org</email>
84    </address>
85  </author>
86
87  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
88    <organization abbrev="Microsoft">Microsoft Corporation</organization>
89    <address>
90      <postal>
91        <street>1 Microsoft Way</street>
92        <city>Redmond</city>
93        <region>WA</region>
94        <code>98052</code>
95        <country>USA</country>
96      </postal>
97      <email>henrikn@microsoft.com</email>
98    </address>
99  </author>
100
101  <author initials="L." surname="Masinter" fullname="Larry Masinter">
102    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
103    <address>
104      <postal>
105        <street>345 Park Ave</street>
106        <city>San Jose</city>
107        <region>CA</region>
108        <code>95110</code>
109        <country>USA</country>
110      </postal>
111      <email>LMM@acm.org</email>
112      <uri>http://larry.masinter.net/</uri>
113    </address>
114  </author>
115 
116  <author initials="P." surname="Leach" fullname="Paul J. Leach">
117    <organization abbrev="Microsoft">Microsoft Corporation</organization>
118    <address>
119      <postal>
120        <street>1 Microsoft Way</street>
121        <city>Redmond</city>
122        <region>WA</region>
123        <code>98052</code>
124      </postal>
125      <email>paulle@microsoft.com</email>
126    </address>
127  </author>
128   
129  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
130    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
131    <address>
132      <postal>
133        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
134        <street>The Stata Center, Building 32</street>
135        <street>32 Vassar Street</street>
136        <city>Cambridge</city>
137        <region>MA</region>
138        <code>02139</code>
139        <country>USA</country>
140      </postal>
141      <email>timbl@w3.org</email>
142      <uri>http://www.w3.org/People/Berners-Lee/</uri>
143    </address>
144  </author>
145
146  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
147    <organization abbrev="W3C">World Wide Web Consortium</organization>
148    <address>
149      <postal>
150        <street>W3C / ERCIM</street>
151        <street>2004, rte des Lucioles</street>
152        <city>Sophia-Antipolis</city>
153        <region>AM</region>
154        <code>06902</code>
155        <country>France</country>
156      </postal>
157      <email>ylafon@w3.org</email>
158      <uri>http://www.raubacapeu.net/people/yves/</uri>
159    </address>
160  </author>
161
162  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
163    <organization abbrev="greenbytes">greenbytes GmbH</organization>
164    <address>
165      <postal>
166        <street>Hafenweg 16</street>
167        <city>Muenster</city><region>NW</region><code>48155</code>
168        <country>Germany</country>
169      </postal>
170      <phone>+49 251 2807760</phone>   
171      <facsimile>+49 251 2807761</facsimile>   
172      <email>julian.reschke@greenbytes.de</email>       
173      <uri>http://greenbytes.de/tech/webdav/</uri>     
174    </address>
175  </author>
176
177  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
178
179<abstract>
180<t>
181   The Hypertext Transfer Protocol (HTTP) is an application-level
182   protocol for distributed, collaborative, hypermedia information
183   systems. HTTP has been in use by the World Wide Web global information
184   initiative since 1990. This document is Part 4 of the seven-part specification
185   that defines the protocol referred to as "HTTP/1.1" and, taken together,
186   obsoletes RFC 2616.  Part 4 defines request header fields for
187   indicating conditional requests and the rules for constructing responses
188   to those requests.
189</t>
190</abstract>
191
192<note title="Editorial Note (To be removed by RFC Editor)">
193  <t>
194    Discussion of this draft should take place on the HTTPBIS working group
195    mailing list (ietf-http-wg@w3.org). The current issues list is
196    at <eref target="http://www.tools.ietf.org/wg/httpbis/trac/report/11"/>
197    and related documents (including fancy diffs) can be found at
198    <eref target="http://www.tools.ietf.org/wg/httpbis/"/>.
199  </t>
200  <t>
201    This draft incorporates those issue resolutions that were either
202    collected in the original RFC2616 errata list (<eref target="http://purl.org/NET/http-errata"/>),
203    or which were agreed upon on the mailing list between October 2006 and
204    November 2007 (as published in "draft-lafon-rfc2616bis-03").
205  </t>
206</note>
207</front>
208<middle>
209<section title="Introduction" anchor="introduction">
210<t>
211   This document defines HTTP/1.1 response metadata for indicating potential
212   changes to payload content, including modification time stamps and opaque
213   entity-tags, and the HTTP conditional request mechanisms that allow
214   preconditions to be placed on a request method.  Conditional GET requests
215   allow for efficient cache updates.  Other conditional request methods are
216   used to protect against overwriting or misunderstanding the state of a
217   resource that has been changed unbeknownst to the requesting client.
218</t>
219<t>
220   This document is currently disorganized in order to minimize the changes
221   between drafts and enable reviewers to see the smaller errata changes.
222   The next draft will reorganize the sections to better reflect the content.
223   In particular, the sections on resource metadata will be discussed first
224   and then followed by each conditional request-header, concluding with a
225   definition of precedence and the expectation of ordering strong validator
226   checks before weak validator checks.  It is likely that more content from
227   &caching; will migrate to this part, where appropriate.
228   The current mess reflects how widely dispersed these topics and associated
229   requirements had become in <xref target="RFC2616"/>.
230</t>
231
232<section title="Requirements" anchor="intro.requirements">
233<t>
234   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
235   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
236   document are to be interpreted as described in <xref target="RFC2119"/>.
237</t>
238<t>
239   An implementation is not compliant if it fails to satisfy one or more
240   of the &MUST; or &REQUIRED; level requirements for the protocols it
241   implements. An implementation that satisfies all the &MUST; or &REQUIRED;
242   level and all the &SHOULD; level requirements for its protocols is said
243   to be "unconditionally compliant"; one that satisfies all the &MUST;
244   level requirements but not all the &SHOULD; level requirements for its
245   protocols is said to be "conditionally compliant."
246</t>
247</section>
248</section>
249
250<section title="Entity Tags" anchor="entity.tags">
251<t>
252   Entity tags are used for comparing two or more entities from the same
253   requested resource. HTTP/1.1 uses entity tags in the ETag (<xref target="header.etag"/>),
254   If-Match (<xref target="header.if-match"/>), If-None-Match (<xref target="header.if-none-match"/>), and
255   If-Range (&header-if-range;) header fields. The definition of how they
256   are used and compared as cache validators is in <xref target="weak.and.strong.validators"/>. An
257   entity tag consists of an opaque quoted string, possibly prefixed by
258   a weakness indicator.
259</t>
260<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"/>
261  entity-tag = [ weak ] opaque-tag
262  weak       = "W/"
263  opaque-tag = quoted-string
264</artwork></figure>
265<t>
266   A "strong entity tag" &MAY; be shared by two entities of a resource
267   only if they are equivalent by octet equality.
268</t>
269<t>
270   A "weak entity tag," indicated by the "W/" prefix, &MAY; be shared by
271   two entities of a resource only if the entities are equivalent and
272   could be substituted for each other with no significant change in
273   semantics. A weak entity tag can only be used for weak comparison.
274</t>
275<t>
276   An entity tag &MUST; be unique across all versions of all entities
277   associated with a particular resource. A given entity tag value &MAY;
278   be used for entities obtained by requests on different URIs. The use
279   of the same entity tag value in conjunction with entities obtained by
280   requests on different URIs does not imply the equivalence of those
281   entities.
282</t>
283</section>
284
285<section title="Status Code Definitions">
286<section title="304 Not Modified" anchor="status.304">
287  <iref primary="true" item="304 Not Modified (status code)" x:for-anchor=""/>
288  <iref primary="true" item="Status Codes" subitem="304 Not Modified" x:for-anchor=""/>
289<t>
290   If the client has performed a conditional GET request and access is
291   allowed, but the document has not been modified, the server &SHOULD;
292   respond with this status code. The 304 response &MUST-NOT; contain a
293   message-body, and thus is always terminated by the first empty line
294   after the header fields.
295</t>
296<t>
297   The response &MUST; include the following header fields:
298  <list style="symbols">
299    <t>Date, unless its omission is required by &clockless;</t>
300  </list>
301</t>
302<t>
303   If a clockless origin server obeys these rules, and proxies and
304   clients add their own Date to any response received without one (as
305   already specified by <xref target="RFC2068" x:sec="14.19" x:fmt=","/>), caches will operate
306   correctly.
307  <list style="symbols">
308    <t>ETag and/or Content-Location, if the header would have been sent
309        in a 200 response to the same request</t>
310    <t>Expires, Cache-Control, and/or Vary, if the field-value might
311        differ from that sent in any previous response for the same
312        variant</t>
313  </list>
314</t>
315<t>
316   If the conditional GET used a strong cache validator (see <xref target="weak.and.strong.validators"/>),
317   the response &SHOULD-NOT;  include other entity-headers.
318   Otherwise (i.e., the conditional GET used a weak validator), the
319   response &MUST-NOT; include other entity-headers; this prevents
320   inconsistencies between cached entity-bodies and updated headers.
321</t>
322<t>
323   If a 304 response indicates an entity not currently cached, then the
324   cache &MUST; disregard the response and repeat the request without the
325   conditional.
326</t>
327<t>
328   If a cache uses a received 304 response to update a cache entry, the
329   cache &MUST; update the entry to reflect any new field values given in
330   the response.
331</t>
332</section>
333
334<section title="412 Precondition Failed" anchor="status.412">
335  <iref primary="true" item="412 Precondition Failed (status code)" x:for-anchor=""/>
336  <iref primary="true" item="Status Codes" subitem="412 Precondition Failed" x:for-anchor=""/>
337<t>
338   The precondition given in one or more of the request-header fields
339   evaluated to false when it was tested on the server. This response
340   code allows the client to place preconditions on the current resource
341   metainformation (header field data) and thus prevent the requested
342   method from being applied to a resource other than the one intended.
343</t>
344</section>
345</section>
346
347<section title="Weak and Strong Validators" anchor="weak.and.strong.validators">
348<t>
349   Since both origin servers and caches will compare two validators to
350   decide if they represent the same or different entities, one normally
351   would expect that if the entity (the entity-body or any entity-headers)
352   changes in any way, then the associated validator would
353   change as well. If this is true, then we call this validator a
354   "strong validator."
355</t>
356<t>
357   However, there might be cases when a server prefers to change the
358   validator only on semantically significant changes, and not when
359   insignificant aspects of the entity change. A validator that does not
360   always change when the resource changes is a "weak validator."
361</t>
362<t>
363   Entity tags are normally "strong validators," but the protocol
364   provides a mechanism to tag an entity tag as "weak." One can think of
365   a strong validator as one that changes whenever the bits of an entity
366   changes, while a weak value changes whenever the meaning of an entity
367   changes. Alternatively, one can think of a strong validator as part
368   of an identifier for a specific entity, while a weak validator is
369   part of an identifier for a set of semantically equivalent entities.
370  <list><t>
371      <x:h>Note:</x:h> One example of a strong validator is an integer that is
372      incremented in stable storage every time an entity is changed.
373    </t><t>
374      An entity's modification time, if represented with one-second
375      resolution, could be a weak validator, since it is possible that
376      the resource might be modified twice during a single second.
377    </t><t>
378      Support for weak validators is optional. However, weak validators
379      allow for more efficient caching of equivalent objects; for
380      example, a hit counter on a site is probably good enough if it is
381      updated every few days or weeks, and any value during that period
382      is likely "good enough" to be equivalent.
383    </t></list>
384</t>
385<t>
386   A "use" of a validator is either when a client generates a request
387   and includes the validator in a validating header field, or when a
388   server compares two validators.
389</t>
390<t>
391   Strong validators are usable in any context. Weak validators are only
392   usable in contexts that do not depend on exact equality of an entity.
393   For example, either kind is usable for a conditional GET of a full
394   entity. However, only a strong validator is usable for a sub-range
395   retrieval, since otherwise the client might end up with an internally
396   inconsistent entity.
397</t>
398<t>
399   Clients &MAY; issue simple (non-subrange) GET requests with either weak
400   validators or strong validators. Clients &MUST-NOT; use weak validators
401   in other forms of request.
402</t>
403<t>
404   The only function that HTTP/1.1 defines on validators is
405   comparison. There are two validator comparison functions, depending
406   on whether the comparison context allows the use of weak validators
407   or not:
408  <list style="symbols">
409     <t>The strong comparison function: in order to be considered equal,
410        both validators &MUST; be identical in every way, and both &MUST-NOT;
411        be weak.</t>
412     <t>The weak comparison function: in order to be considered equal,
413        both validators &MUST; be identical in every way, but either or
414        both of them &MAY; be tagged as "weak" without affecting the
415        result.</t>
416  </list>
417</t>
418<t>
419   An entity tag is strong unless it is explicitly tagged as weak.
420   <xref target="entity.tags"/> gives the syntax for entity tags.
421</t>
422<t>
423   A Last-Modified time, when used as a validator in a request, is
424   implicitly weak unless it is possible to deduce that it is strong,
425   using the following rules:
426  <list style="symbols">
427     <t>The validator is being compared by an origin server to the
428        actual current validator for the entity and,</t>
429     <t>That origin server reliably knows that the associated entity did
430        not change twice during the second covered by the presented
431        validator.</t>
432  </list>
433</t>
434<t>
435   or
436  <list style="symbols">
437     <t>The validator is about to be used by a client in an If-Modified-Since
438        or If-Unmodified-Since header, because the client
439        has a cache entry for the associated entity, and</t>
440     <t>That cache entry includes a Date value, which gives the time
441        when the origin server sent the original response, and</t>
442     <t>The presented Last-Modified time is at least 60 seconds before
443        the Date value.</t>
444  </list>
445</t>
446<t>
447   or
448  <list style="symbols">
449     <t>The validator is being compared by an intermediate cache to the
450        validator stored in its cache entry for the entity, and</t>
451     <t>That cache entry includes a Date value, which gives the time
452        when the origin server sent the original response, and</t>
453     <t>The presented Last-Modified time is at least 60 seconds before
454        the Date value.</t>
455  </list>
456</t>
457<t>
458   This method relies on the fact that if two different responses were
459   sent by the origin server during the same second, but both had the
460   same Last-Modified time, then at least one of those responses would
461   have a Date value equal to its Last-Modified time. The arbitrary 60-second
462   limit guards against the possibility that the Date and Last-Modified
463   values are generated from different clocks, or at somewhat
464   different times during the preparation of the response. An
465   implementation &MAY; use a value larger than 60 seconds, if it is
466   believed that 60 seconds is too short.
467</t>
468<t>
469   If a client wishes to perform a sub-range retrieval on a value for
470   which it has only a Last-Modified time and no opaque validator, it
471   &MAY; do this only if the Last-Modified time is strong in the sense
472   described here.
473</t>
474<t>
475   A cache or origin server receiving a conditional request, other than
476   a full-body GET request, &MUST; use the strong comparison function to
477   evaluate the condition.
478</t>
479<t>
480   These rules allow HTTP/1.1 caches and clients to safely perform sub-range
481   retrievals on values that have been obtained from HTTP/1.0
482   servers.
483</t>
484</section>
485
486<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">
487<t>
488   We adopt a set of rules and recommendations for origin servers,
489   clients, and caches regarding when various validator types ought to
490   be used, and for what purposes.
491</t>
492<t>
493   HTTP/1.1 origin servers:
494  <list style="symbols">
495     <t>&SHOULD; send an entity tag validator unless it is not feasible to
496        generate one.</t>
497
498     <t>&MAY; send a weak entity tag instead of a strong entity tag, if
499        performance considerations support the use of weak entity tags,
500        or if it is unfeasible to send a strong entity tag.</t>
501
502     <t>&SHOULD; send a Last-Modified value if it is feasible to send one,
503        unless the risk of a breakdown in semantic transparency that
504        could result from using this date in an If-Modified-Since header
505        would lead to serious problems.</t>
506  </list>
507</t>
508<t>
509   In other words, the preferred behavior for an HTTP/1.1 origin server
510   is to send both a strong entity tag and a Last-Modified value.
511</t>
512<t>
513   In order to be legal, a strong entity tag &MUST; change whenever the
514   associated entity value changes in any way. A weak entity tag &SHOULD;
515   change whenever the associated entity changes in a semantically
516   significant way.
517  <list><t>
518      <x:h>Note:</x:h> in order to provide semantically transparent caching, an
519      origin server must avoid reusing a specific strong entity tag
520      value for two different entities, or reusing a specific weak
521      entity tag value for two semantically different entities. Cache
522      entries might persist for arbitrarily long periods, regardless of
523      expiration times, so it might be inappropriate to expect that a
524      cache will never again attempt to validate an entry using a
525      validator that it obtained at some point in the past.
526  </t></list>
527</t>
528<t>
529   HTTP/1.1 clients:
530  <list style="symbols">
531     <t>If an entity tag has been provided by the origin server, &MUST;
532        use that entity tag in any cache-conditional request (using If-Match
533        or If-None-Match).</t>
534
535     <t>If only a Last-Modified value has been provided by the origin
536        server, &SHOULD; use that value in non-subrange cache-conditional
537        requests (using If-Modified-Since).</t>
538
539     <t>If only a Last-Modified value has been provided by an HTTP/1.0
540        origin server, &MAY; use that value in subrange cache-conditional
541        requests (using If-Unmodified-Since:). The user agent &SHOULD;
542        provide a way to disable this, in case of difficulty.</t>
543
544     <t>If both an entity tag and a Last-Modified value have been
545        provided by the origin server, &SHOULD; use both validators in
546        cache-conditional requests. This allows both HTTP/1.0 and
547        HTTP/1.1 caches to respond appropriately.</t>
548  </list>
549</t>
550<t>
551   An HTTP/1.1 origin server, upon receiving a conditional request that
552   includes both a Last-Modified date (e.g., in an If-Modified-Since or
553   If-Unmodified-Since header field) and one or more entity tags (e.g.,
554   in an If-Match, If-None-Match, or If-Range header field) as cache
555   validators, &MUST-NOT; return a response status of 304 (Not Modified)
556   unless doing so is consistent with all of the conditional header
557   fields in the request.
558</t>
559<t>
560   An HTTP/1.1 caching proxy, upon receiving a conditional request that
561   includes both a Last-Modified date and one or more entity tags as
562   cache validators, &MUST-NOT; return a locally cached response to the
563   client unless that cached response is consistent with all of the
564   conditional header fields in the request.
565  <list><t>
566      <x:h>Note:</x:h> The general principle behind these rules is that HTTP/1.1
567      servers and clients should transmit as much non-redundant
568      information as is available in their responses and requests.
569      HTTP/1.1 systems receiving this information will make the most
570      conservative assumptions about the validators they receive.
571  </t><t>
572      HTTP/1.0 clients and caches will ignore entity tags. Generally,
573      last-modified values received or used by these systems will
574      support transparent and efficient caching, and so HTTP/1.1 origin
575      servers should provide Last-Modified values. In those rare cases
576      where the use of a Last-Modified value as a validator by an
577      HTTP/1.0 system could result in a serious problem, then HTTP/1.1
578      origin servers should not provide one.
579  </t></list>
580</t>
581</section>
582
583<section title="Header Field Definitions" anchor="header.fields">
584<t>
585   This section defines the syntax and semantics of HTTP/1.1 header fields
586   related to conditional requests.
587</t>
588<t>
589   For entity-header fields, both sender and recipient refer to either the
590   client or the server, depending on who sends and who receives the entity.
591</t>
592
593<section title="ETag" anchor="header.etag">
594  <iref primary="true" item="ETag header" x:for-anchor=""/>
595  <iref primary="true" item="Headers" subitem="ETag" x:for-anchor=""/>
596<t>
597   The ETag response-header field provides the current value of the
598   entity tag for the requested variant. The headers used with entity
599   tags are described in Sections <xref target="header.if-match" format="counter"/>
600   and <xref target="header.if-none-match" format="counter"/> of this document,
601   and in &header-if-range;. The entity tag
602   &MAY; be used for comparison with other entities from the same resource
603   (see <xref target="weak.and.strong.validators"/>).
604</t>
605<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="ETag"/>
606  ETag = "ETag" ":" entity-tag
607</artwork></figure>
608<figure><preamble>
609   Examples:
610</preamble>
611<artwork type="example">
612   ETag: "xyzzy"
613   ETag: W/"xyzzy"
614   ETag: ""
615</artwork></figure>
616</section>
617
618<section title="If-Match" anchor="header.if-match">
619  <iref primary="true" item="If-Match header" x:for-anchor=""/>
620  <iref primary="true" item="Headers" subitem="If-Match" x:for-anchor=""/>
621<t>
622   The If-Match request-header field is used with a method to make it
623   conditional. A client that has one or more entities previously
624   obtained from the resource can verify that one of those entities is
625   current by including a list of their associated entity tags in the
626   If-Match header field. Entity tags are defined in <xref target="entity.tags"/>. The
627   purpose of this feature is to allow efficient updates of cached
628   information with a minimum amount of transaction overhead. It is also
629   used, on updating requests, to prevent inadvertent modification of
630   the wrong version of a resource. As a special case, the value "*"
631   matches any current entity of the resource.
632</t>
633<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Match"/>
634  If-Match = "If-Match" ":" ( "*" | 1#entity-tag )
635</artwork></figure>
636<t>
637   If any of the entity tags match the entity tag of the entity that
638   would have been returned in the response to a similar GET request
639   (without the If-Match header) on that resource, or if "*" is given
640   and any current entity exists for that resource, then the server &MAY;
641   perform the requested method as if the If-Match header field did not
642   exist.
643</t>
644<t>
645   A server &MUST; use the strong comparison function (see <xref target="weak.and.strong.validators"/>)
646   to compare the entity tags in If-Match.
647</t>
648<t>
649   If none of the entity tags match, or if "*" is given and no current
650   entity exists, the server &MUST-NOT; perform the requested method, and
651   &MUST; return a 412 (Precondition Failed) response. This behavior is
652   most useful when the client wants to prevent an updating method, such
653   as PUT, from modifying a resource that has changed since the client
654   last retrieved it.
655</t>
656<t>
657   If the request would, without the If-Match header field, result in
658   anything other than a 2xx or 412 status, then the If-Match header
659   &MUST; be ignored.
660</t>
661<t>
662   The meaning of "If-Match: *" is that the method &SHOULD; be performed
663   if the representation selected by the origin server (or by a cache,
664   possibly using the Vary mechanism, see &header-vary;) exists, and
665   &MUST-NOT; be performed if the representation does not exist.
666</t>
667<t>
668   A request intended to update a resource (e.g., a PUT) &MAY; include an
669   If-Match header field to signal that the request method &MUST-NOT; be
670   applied if the entity corresponding to the If-Match value (a single
671   entity tag) is no longer a representation of that resource. This
672   allows the user to indicate that they do not wish the request to be
673   successful if the resource has been changed without their knowledge.
674   Examples:
675</t>
676<figure><artwork type="example">
677    If-Match: "xyzzy"
678    If-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
679    If-Match: *
680</artwork></figure>
681<t>
682   The result of a request having both an If-Match header field and
683   either an If-None-Match or an If-Modified-Since header fields is
684   undefined by this specification.
685</t>
686</section>
687
688<section title="If-Modified-Since" anchor="header.if-modified-since">
689  <iref primary="true" item="If-Modified-Since header" x:for-anchor=""/>
690  <iref primary="true" item="Headers" subitem="If-Modified-Since" x:for-anchor=""/>
691<t>
692   The If-Modified-Since request-header field is used with a method to
693   make it conditional: if the requested variant has not been modified
694   since the time specified in this field, an entity will not be
695   returned from the server; instead, a 304 (Not Modified) response will
696   be returned without any message-body.
697</t>
698<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Modified-Since"/>
699  If-Modified-Since = "If-Modified-Since" ":" HTTP-date
700</artwork></figure>
701<t>
702   An example of the field is:
703</t>
704<figure><artwork type="example">
705    If-Modified-Since: Sat, 29 Oct 1994 19:43:31 GMT
706</artwork></figure>
707<t>
708   A GET method with an If-Modified-Since header and no Range header
709   requests that the identified entity be transferred only if it has
710   been modified since the date given by the If-Modified-Since header.
711   The algorithm for determining this includes the following cases:
712  <list style="numbers">
713      <t>If the request would normally result in anything other than a
714         200 (OK) status, or if the passed If-Modified-Since date is
715         invalid, the response is exactly the same as for a normal GET.
716         A date which is later than the server's current time is
717         invalid.</t>
718
719      <t>If the variant has been modified since the If-Modified-Since
720         date, the response is exactly the same as for a normal GET.</t>
721
722      <t>If the variant has not been modified since a valid If-Modified-Since
723         date, the server &SHOULD; return a 304 (Not
724         Modified) response.</t>
725  </list>
726</t>
727<t>
728   The purpose of this feature is to allow efficient updates of cached
729   information with a minimum amount of transaction overhead.
730  <list><t>
731      <x:h>Note:</x:h> The Range request-header field modifies the meaning of If-Modified-Since;
732      see &header-range; for full details.
733    </t><t>
734      <x:h>Note:</x:h> If-Modified-Since times are interpreted by the server, whose
735      clock might not be synchronized with the client.
736    </t><t>
737      <x:h>Note:</x:h> When handling an If-Modified-Since header field, some
738      servers will use an exact date comparison function, rather than a
739      less-than function, for deciding whether to send a 304 (Not
740      Modified) response. To get best results when sending an If-Modified-Since
741      header field for cache validation, clients are
742      advised to use the exact date string received in a previous Last-Modified
743      header field whenever possible.
744    </t><t>
745      <x:h>Note:</x:h> If a client uses an arbitrary date in the If-Modified-Since
746      header instead of a date taken from the Last-Modified header for
747      the same request, the client should be aware of the fact that this
748      date is interpreted in the server's understanding of time. The
749      client should consider unsynchronized clocks and rounding problems
750      due to the different encodings of time between the client and
751      server. This includes the possibility of race conditions if the
752      document has changed between the time it was first requested and
753      the If-Modified-Since date of a subsequent request, and the
754      possibility of clock-skew-related problems if the If-Modified-Since
755      date is derived from the client's clock without correction
756      to the server's clock. Corrections for different time bases
757      between client and server are at best approximate due to network
758      latency.
759    </t>
760  </list>
761</t>
762<t>
763   The result of a request having both an If-Modified-Since header field
764   and either an If-Match or an If-Unmodified-Since header fields is
765   undefined by this specification.
766</t>
767</section>
768
769<section title="If-None-Match" anchor="header.if-none-match">
770  <iref primary="true" item="If-None-Match header" x:for-anchor=""/>
771  <iref primary="true" item="Headers" subitem="If-None-Match" x:for-anchor=""/>
772<t>
773   The If-None-Match request-header field is used with a method to make
774   it conditional. A client that has one or more entities previously
775   obtained from the resource can verify that none of those entities is
776   current by including a list of their associated entity tags in the
777   If-None-Match header field. The purpose of this feature is to allow
778   efficient updates of cached information with a minimum amount of
779   transaction overhead. It is also used to prevent a method (e.g. PUT)
780   from inadvertently modifying an existing resource when the client
781   believes that the resource does not exist.
782</t>
783<t>
784   As a special case, the value "*" matches any current entity of the
785   resource.
786</t>
787<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-None-Match"/>
788  If-None-Match = "If-None-Match" ":" ( "*" | 1#entity-tag )
789</artwork></figure>
790<t>
791   If any of the entity tags match the entity tag of the entity that
792   would have been returned in the response to a similar GET request
793   (without the If-None-Match header) on that resource, or if "*" is
794   given and any current entity exists for that resource, then the
795   server &MUST-NOT; perform the requested method, unless required to do
796   so because the resource's modification date fails to match that
797   supplied in an If-Modified-Since header field in the request.
798   Instead, if the request method was GET or HEAD, the server &SHOULD;
799   respond with a 304 (Not Modified) response, including the cache-related
800   header fields (particularly ETag) of one of the entities that
801   matched. For all other request methods, the server &MUST; respond with
802   a status of 412 (Precondition Failed).
803</t>
804<t>
805   See <xref target="weak.and.strong.validators"/> for rules on how to determine if two entities tags
806   match. The weak comparison function can only be used with GET or HEAD
807   requests.
808</t>
809<t>
810   If none of the entity tags match, then the server &MAY; perform the
811   requested method as if the If-None-Match header field did not exist,
812   but &MUST; also ignore any If-Modified-Since header field(s) in the
813   request. That is, if no entity tags match, then the server &MUST-NOT;
814   return a 304 (Not Modified) response.
815</t>
816<t>
817   If the request would, without the If-None-Match header field, result
818   in anything other than a 2xx or 304 status, then the If-None-Match
819   header &MUST; be ignored. (See <xref target="rules.for.when.to.use.entity.tags.and.last-modified.dates"/> for a discussion of
820   server behavior when both If-Modified-Since and If-None-Match appear
821   in the same request.)
822</t>
823<t>
824   The meaning of "If-None-Match: *" is that the method &MUST-NOT; be
825   performed if the representation selected by the origin server (or by
826   a cache, possibly using the Vary mechanism, see &header-vary;)
827   exists, and &SHOULD; be performed if the representation does not exist.
828   This feature is intended to be useful in preventing races between PUT
829   operations.
830</t>
831<t>
832   Examples:
833</t>
834<figure><artwork type="example">
835    If-None-Match: "xyzzy"
836    If-None-Match: W/"xyzzy"
837    If-None-Match: "xyzzy", "r2d2xxxx", "c3piozzzz"
838    If-None-Match: W/"xyzzy", W/"r2d2xxxx", W/"c3piozzzz"
839    If-None-Match: *
840</artwork></figure>
841<t>
842   The result of a request having both an If-None-Match header field and
843   either an If-Match or an If-Unmodified-Since header fields is
844   undefined by this specification.
845</t>
846</section>
847
848<section title="If-Unmodified-Since" anchor="header.if-unmodified-since">
849  <iref primary="true" item="If-Unmodified-Since header" x:for-anchor=""/>
850  <iref primary="true" item="Headers" subitem="If-Unmodified-Since" x:for-anchor=""/>
851<t>
852   The If-Unmodified-Since request-header field is used with a method to
853   make it conditional. If the requested resource has not been modified
854   since the time specified in this field, the server &SHOULD; perform the
855   requested operation as if the If-Unmodified-Since header were not
856   present.
857</t>
858<t>
859   If the requested variant has been modified since the specified time,
860   the server &MUST-NOT; perform the requested operation, and &MUST; return
861   a 412 (Precondition Failed).
862</t>
863<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="If-Unmodified-Since"/>
864  If-Unmodified-Since = "If-Unmodified-Since" ":" HTTP-date
865</artwork></figure>
866<t>
867   An example of the field is:
868</t>
869<figure><artwork type="example">
870    If-Unmodified-Since: Sat, 29 Oct 1994 19:43:31 GMT
871</artwork></figure>
872<t>
873   If the request normally (i.e., without the If-Unmodified-Since
874   header) would result in anything other than a 2xx or 412 status, the
875   If-Unmodified-Since header &SHOULD; be ignored.
876</t>
877<t>
878   If the specified date is invalid, the header is ignored.
879</t>
880<t>
881   The result of a request having both an If-Unmodified-Since header
882   field and either an If-None-Match or an If-Modified-Since header
883   fields is undefined by this specification.
884</t>
885</section>
886
887<section title="Last-Modified" anchor="header.last-modified">
888  <iref primary="true" item="Last-Modified header" x:for-anchor=""/>
889  <iref primary="true" item="Headers" subitem="Last-Modified" x:for-anchor=""/>
890<t>
891   The Last-Modified entity-header field indicates the date and time at
892   which the origin server believes the variant was last modified.
893</t>
894<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Last-Modified"/>
895  Last-Modified  = "Last-Modified" ":" HTTP-date
896</artwork></figure>
897<t>
898   An example of its use is
899</t>
900<figure><artwork type="example">
901    Last-Modified: Tue, 15 Nov 1994 12:45:26 GMT
902</artwork></figure>
903<t>
904   The exact meaning of this header field depends on the implementation
905   of the origin server and the nature of the original resource. For
906   files, it may be just the file system last-modified time. For
907   entities with dynamically included parts, it may be the most recent
908   of the set of last-modify times for its component parts. For database
909   gateways, it may be the last-update time stamp of the record. For
910   virtual objects, it may be the last time the internal state changed.
911</t>
912<t>
913   An origin server &MUST-NOT; send a Last-Modified date which is later
914   than the server's time of message origination. In such cases, where
915   the resource's last modification would indicate some time in the
916   future, the server &MUST; replace that date with the message
917   origination date.
918</t>
919<t>
920   An origin server &SHOULD; obtain the Last-Modified value of the entity
921   as close as possible to the time that it generates the Date value of
922   its response. This allows a recipient to make an accurate assessment
923   of the entity's modification time, especially if the entity changes
924   near the time that the response is generated.
925</t>
926<t>
927   HTTP/1.1 servers &SHOULD; send Last-Modified whenever feasible.
928</t>
929</section>
930
931</section>
932
933<section title="IANA Considerations" anchor="IANA.considerations">
934<t>
935   TBD.
936</t>
937</section>
938
939<section title="Security Considerations" anchor="security.considerations">
940<t>
941   No additional security considerations have been identified beyond
942   those applicable to HTTP in general &messaging;.
943</t>
944</section>
945
946<section title="Acknowledgments" anchor="ack">
947</section>
948</middle>
949<back>
950
951<references title="Normative References">
952
953<reference anchor="Part1">
954  <front>
955    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
956    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
957      <organization abbrev="Day Software">Day Software</organization>
958      <address><email>fielding@gbiv.com</email></address>
959    </author>
960    <author initials="J." surname="Gettys" fullname="Jim Gettys">
961      <organization>One Laptop per Child</organization>
962      <address><email>jg@laptop.org</email></address>
963    </author>
964    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
965      <organization abbrev="HP">Hewlett-Packard Company</organization>
966      <address><email>JeffMogul@acm.org</email></address>
967    </author>
968    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
969      <organization abbrev="Microsoft">Microsoft Corporation</organization>
970      <address><email>henrikn@microsoft.com</email></address>
971    </author>
972    <author initials="L." surname="Masinter" fullname="Larry Masinter">
973      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
974      <address><email>LMM@acm.org</email></address>
975    </author>
976    <author initials="P." surname="Leach" fullname="Paul J. Leach">
977      <organization abbrev="Microsoft">Microsoft Corporation</organization>
978      <address><email>paulle@microsoft.com</email></address>
979    </author>
980    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
981      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
982      <address><email>timbl@w3.org</email></address>
983    </author>
984    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
985      <organization abbrev="W3C">World Wide Web Consortium</organization>
986      <address><email>ylafon@w3.org</email></address>
987    </author>
988    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
989      <organization abbrev="greenbytes">greenbytes GmbH</organization>
990      <address><email>julian.reschke@greenbytes.de</email></address>
991    </author>
992    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
993  </front>
994  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
995  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
996</reference>
997
998<reference anchor="Part5">
999  <front>
1000    <title abbrev="HTTP/1.1">HTTP/1.1, part 5: Range Requests and Partial Responses</title>
1001    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1002      <organization abbrev="Day Software">Day Software</organization>
1003      <address><email>fielding@gbiv.com</email></address>
1004    </author>
1005    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1006      <organization>One Laptop per Child</organization>
1007      <address><email>jg@laptop.org</email></address>
1008    </author>
1009    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1010      <organization abbrev="HP">Hewlett-Packard Company</organization>
1011      <address><email>JeffMogul@acm.org</email></address>
1012    </author>
1013    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1014      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1015      <address><email>henrikn@microsoft.com</email></address>
1016    </author>
1017    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1018      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1019      <address><email>LMM@acm.org</email></address>
1020    </author>
1021    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1022      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1023      <address><email>paulle@microsoft.com</email></address>
1024    </author>
1025    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1026      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1027      <address><email>timbl@w3.org</email></address>
1028    </author>
1029    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1030      <organization abbrev="W3C">World Wide Web Consortium</organization>
1031      <address><email>ylafon@w3.org</email></address>
1032    </author>
1033    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1034      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1035      <address><email>julian.reschke@greenbytes.de</email></address>
1036    </author>
1037    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1038  </front>
1039  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p5-range-&ID-VERSION;"/>
1040  <x:source href="p5-range.xml" basename="p5-range"/>
1041</reference>
1042
1043<reference anchor="Part6">
1044  <front>
1045    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
1046    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
1047      <organization abbrev="Day Software">Day Software</organization>
1048      <address><email>fielding@gbiv.com</email></address>
1049    </author>
1050    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1051      <organization>One Laptop per Child</organization>
1052      <address><email>jg@laptop.org</email></address>
1053    </author>
1054    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1055      <organization abbrev="HP">Hewlett-Packard Company</organization>
1056      <address><email>JeffMogul@acm.org</email></address>
1057    </author>
1058    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
1059      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1060      <address><email>henrikn@microsoft.com</email></address>
1061    </author>
1062    <author initials="L." surname="Masinter" fullname="Larry Masinter">
1063      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
1064      <address><email>LMM@acm.org</email></address>
1065    </author>
1066    <author initials="P." surname="Leach" fullname="Paul J. Leach">
1067      <organization abbrev="Microsoft">Microsoft Corporation</organization>
1068      <address><email>paulle@microsoft.com</email></address>
1069    </author>
1070    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1071      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1072      <address><email>timbl@w3.org</email></address>
1073    </author>
1074    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
1075      <organization abbrev="W3C">World Wide Web Consortium</organization>
1076      <address><email>ylafon@w3.org</email></address>
1077    </author>
1078    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
1079      <organization abbrev="greenbytes">greenbytes GmbH</organization>
1080      <address><email>julian.reschke@greenbytes.de</email></address>
1081    </author>
1082    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
1083  </front>
1084  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
1085  <x:source href="p6-cache.xml" basename="p6-cache"/>
1086</reference>
1087
1088<reference anchor="RFC2119">
1089  <front>
1090    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
1091    <author initials="S." surname="Bradner" fullname="Scott Bradner">
1092      <organization>Harvard University</organization>
1093      <address><email>sob@harvard.edu</email></address>
1094    </author>
1095    <date month="March" year="1997"/>
1096  </front>
1097  <seriesInfo name="BCP" value="14"/>
1098  <seriesInfo name="RFC" value="2119"/>
1099</reference>
1100
1101</references>
1102
1103<references title="Informative References">
1104
1105<reference anchor="RFC2068">
1106  <front>
1107    <title abbrev="HTTP/1.1">Hypertext Transfer Protocol -- HTTP/1.1</title>
1108    <author initials="R." surname="Fielding" fullname="Roy T. Fielding">
1109      <organization>University of California, Irvine, Department of Information and Computer Science</organization>
1110      <address><email>fielding@ics.uci.edu</email></address>
1111    </author>
1112    <author initials="J." surname="Gettys" fullname="Jim Gettys">
1113      <organization>MIT Laboratory for Computer Science</organization>
1114      <address><email>jg@w3.org</email></address>
1115    </author>
1116    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
1117      <organization>Digital Equipment Corporation, Western Research Laboratory</organization>
1118      <address><email>mogul@wrl.dec.com</email></address>
1119    </author>
1120    <author initials="H." surname="Nielsen" fullname="Henrik Frystyk Nielsen">
1121      <organization>MIT Laboratory for Computer Science</organization>
1122      <address><email>frystyk@w3.org</email></address>
1123    </author>
1124    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
1125      <organization>MIT Laboratory for Computer Science</organization>
1126      <address><email>timbl@w3.org</email></address>
1127    </author>
1128    <date month="January" year="1997"/>
1129  </front>
1130  <seriesInfo name="RFC" value="2068"/>
1131</reference>
1132
1133<reference anchor="RFC2616">
1134  <front>
1135    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
1136    <author initials="R." surname="Fielding" fullname="R. Fielding">
1137      <organization>University of California, Irvine</organization>
1138      <address><email>fielding@ics.uci.edu</email></address>
1139    </author>
1140    <author initials="J." surname="Gettys" fullname="J. Gettys">
1141      <organization>W3C</organization>
1142      <address><email>jg@w3.org</email></address>
1143    </author>
1144    <author initials="J." surname="Mogul" fullname="J. Mogul">
1145      <organization>Compaq Computer Corporation</organization>
1146      <address><email>mogul@wrl.dec.com</email></address>
1147    </author>
1148    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
1149      <organization>MIT Laboratory for Computer Science</organization>
1150      <address><email>frystyk@w3.org</email></address>
1151    </author>
1152    <author initials="L." surname="Masinter" fullname="L. Masinter">
1153      <organization>Xerox Corporation</organization>
1154      <address><email>masinter@parc.xerox.com</email></address>
1155    </author>
1156    <author initials="P." surname="Leach" fullname="P. Leach">
1157      <organization>Microsoft Corporation</organization>
1158      <address><email>paulle@microsoft.com</email></address>
1159    </author>
1160    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
1161      <organization>W3C</organization>
1162      <address><email>timbl@w3.org</email></address>
1163    </author>
1164    <date month="June" year="1999"/>
1165  </front>
1166  <seriesInfo name="RFC" value="2616"/>
1167</reference>
1168
1169</references>
1170
1171<section title="Compatibility with Previous Versions" anchor="compatibility">
1172
1173<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
1174</section>
1175
1176</section>
1177
1178<section title="Change Log (to be removed by RFC Editor before publication)">
1179
1180<section title="Since RFC2616">
1181<t>
1182  Extracted relevant partitions from <xref target="RFC2616"/>.
1183</t>
1184</section>
1185
1186<section title="Since draft-ietf-httpbis-p4-conditional-00">
1187<t>
1188  Closed issues:
1189  <list style="symbols"> 
1190    <t>
1191      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
1192      "Normative and Informative references"
1193    </t>
1194  </list>
1195</t>
1196<t>
1197  Other changes:
1198  <list style="symbols"> 
1199    <t>
1200      Move definitions of 304 and 412 condition codes from Part2.
1201    </t>
1202  </list>
1203</t>
1204</section>
1205
1206<section title="Since draft-ietf-httpbis-p4-conditional-01">
1207<t>
1208</t>
1209</section>
1210
1211</section>
1212
1213</back>
1214</rfc>
Note: See TracBrowser for help on using the repository browser.