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

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

List Yves Lafon & Julian Reschke as Editors everywhere, remove specific ack for Julian.

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