source: draft-ietf-httpbis/orig/rfc2145.html @ 598

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

fix Makefile, add RFC 2817/2818, re-gen HTML

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html
File size: 30.8 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>Use and Interpretation of HTTP Version Numbers</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
9}
10a.smpl {
11  color: black;
12}
13a:hover {
14  text-decoration: underline;
15}
16a:active {
17  text-decoration: underline;
18}
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
23}
24blockquote {
25  border-style: solid;
26  border-color: gray;
27  border-width: 0 0 0 .25em;
28  font-style: italic;
29  padding-left: 0.5em;
30}
31body {
32  color: black;
33  font-family: verdana, helvetica, arial, sans-serif;
34  font-size: 10pt;
35}
36cite {
37  font-style: normal;
38}
39div.note {
40  margin-left: 2em;
41}
42dd {
43  margin-right: 2em;
44}
45dl {
46  margin-left: 2em;
47}
48
49dl.empty dd {
50  margin-top: .5em;
51}
52dl p {
53  margin-left: 0em;
54}
55dt {
56  margin-top: .5em;
57}
58h1 {
59  font-size: 14pt;
60  line-height: 21pt;
61  page-break-after: avoid;
62}
63h1.np {
64  page-break-before: always;
65}
66h1 a {
67  color: #333333;
68}
69h2 {
70  font-size: 12pt;
71  line-height: 15pt;
72  page-break-after: avoid;
73}
74h3, h4, h5, h6 {
75  font-size: 10pt;
76  page-break-after: avoid;
77}
78h2 a, h3 a, h4 a, h5 a, h6 a {
79  color: black;
80}
81img {
82  margin-left: 3em;
83}
84li {
85  margin-left: 2em;
86  margin-right: 2em;
87}
88ol {
89  margin-left: 2em;
90  margin-right: 2em;
91}
92ol p {
93  margin-left: 0em;
94}
95p {
96  margin-left: 2em;
97  margin-right: 2em;
98}
99pre {
100  margin-left: 3em;
101  background-color: lightyellow;
102  padding: .25em;
103}
104pre.text2 {
105  border-style: dotted;
106  border-width: 1px;
107  background-color: #f0f0f0;
108  width: 69em;
109}
110pre.inline {
111  background-color: white;
112  padding: 0em;
113}
114pre.text {
115  border-style: dotted;
116  border-width: 1px;
117  background-color: #f8f8f8;
118  width: 69em;
119}
120pre.drawing {
121  border-style: solid;
122  border-width: 1px;
123  background-color: #f8f8f8;
124  padding: 2em;
125}
126table {
127  margin-left: 2em;
128}
129table.header {
130  width: 95%;
131  font-size: 10pt;
132  color: white;
133}
134td.top {
135  vertical-align: top;
136}
137td.topnowrap {
138  vertical-align: top;
139  white-space: nowrap; 
140}
141td.header {
142  background-color: gray;
143  width: 50%;
144}
145td.reference {
146  vertical-align: top;
147  white-space: nowrap;
148  padding-right: 1em;
149}
150thead {
151  display:table-header-group;
152}
153ul.toc {
154  list-style: none;
155  margin-left: 1.5em;
156  margin-right: 0em;
157  padding-left: 0em;
158}
159li.tocline0 {
160  line-height: 150%;
161  font-weight: bold;
162  font-size: 10pt;
163  margin-left: 0em;
164  margin-right: 0em;
165}
166li.tocline1 {
167  line-height: normal;
168  font-weight: normal;
169  font-size: 9pt;
170  margin-left: 0em;
171  margin-right: 0em;
172}
173li.tocline2 {
174  font-size: 0pt;
175}
176ul p {
177  margin-left: 0em;
178}
179.bcp14 {
180  font-style: normal;
181  text-transform: lowercase;
182  font-variant: small-caps;
183}
184blockquote > * .bcp14 {
185  font-style: italic;
186}
187.comment {
188  background-color: yellow;
189}
190.center {
191  text-align: center;
192}
193.error {
194  color: red;
195  font-style: italic;
196  font-weight: bold;
197}
198.figure {
199  font-weight: bold;
200  text-align: center;
201  font-size: 9pt;
202}
203.filename {
204  color: #333333;
205  font-weight: bold;
206  font-size: 12pt;
207  line-height: 21pt;
208  text-align: center;
209}
210.fn {
211  font-weight: bold;
212}
213.hidden {
214  display: none;
215}
216.left {
217  text-align: left;
218}
219.right {
220  text-align: right;
221}
222.title {
223  color: #990000;
224  font-size: 18pt;
225  line-height: 18pt;
226  font-weight: bold;
227  text-align: center;
228  margin-top: 36pt;
229}
230.vcardline {
231  display: block;
232}
233.warning {
234  font-size: 14pt;
235  background-color: yellow;
236}
237
238
239@media print {
240  .noprint {
241    display: none;
242  }
243 
244  a {
245    color: black;
246    text-decoration: none;
247  }
248
249  table.header {
250    width: 90%;
251  }
252
253  td.header {
254    width: 50%;
255    color: black;
256    background-color: white;
257    vertical-align: top;
258    font-size: 12pt;
259  }
260
261  ul.toc a::after {
262    content: leader('.') target-counter(attr(href), page);
263  }
264 
265  a.iref {
266    content: target-counter(attr(href), page);
267  }
268 
269  .print2col {
270    column-count: 2;
271    -moz-column-count: 2;
272    column-fill: auto;
273  }
274}
275
276@page {
277  @top-left {
278       content: "RFC 2145"; 
279  } 
280  @top-right {
281       content: "May 1997"; 
282  } 
283  @top-center {
284       content: "HTTP Version Numbers"; 
285  } 
286  @bottom-left {
287       content: "Mogul, et al."; 
288  } 
289  @bottom-center {
290       content: "Informational"; 
291  } 
292  @bottom-right {
293       content: "[Page " counter(page) "]"; 
294  } 
295}
296
297@page:first { 
298    @top-left {
299      content: normal;
300    }
301    @top-right {
302      content: normal;
303    }
304    @top-center {
305      content: normal;
306    }
307}
308</style><link rel="Contents" href="#rfc.toc">
309      <link rel="Author" href="#rfc.authors">
310      <link rel="Copyright" href="#rfc.copyright">
311      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
312      <link rel="Chapter" title="2 HTTP version numbers" href="#rfc.section.2">
313      <link rel="Chapter" title="3 Security Considerations" href="#rfc.section.3">
314      <link rel="Chapter" href="#rfc.section.4" title="4 References">
315      <link rel="Alternate" title="Authorative ASCII Version" href="http://www.ietf.org/rfc/rfc2145.txt">
316      <link rel="Help" title="Additional Information on tools.ietf.org" href="http://tools.ietf.org/html/rfc2145">
317      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.438, 2009-05-27 13:34:05, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
318      <meta name="keywords" content="HTTP, hypertext transfer protocol">
319      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
320      <meta name="DC.Creator" content="Mogul, J. C.">
321      <meta name="DC.Creator" content="Fielding, R. T.">
322      <meta name="DC.Creator" content="Gettys, J.">
323      <meta name="DC.Creator" content="Frystyk, H.">
324      <meta name="DC.Identifier" content="urn:ietf:rfc:2145">
325      <meta name="DC.Date.Issued" scheme="ISO8601" content="1997-05">
326      <meta name="DC.Description.Abstract" content="HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.">
327      <meta name="DC.isPartOf" content="urn:ISSN:2070-1721">
328   </head>
329   <body>
330      <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
331         <tr>
332            <td class="header left">Network Working Group</td>
333            <td class="header right">J. C. Mogul</td>
334         </tr>
335         <tr>
336            <td class="header left">Request for Comments: 2145</td>
337            <td class="header right">DEC</td>
338         </tr>
339         <tr>
340            <td class="header left">Category: Informational</td>
341            <td class="header right">R. T. Fielding</td>
342         </tr>
343         <tr>
344            <td class="header left"></td>
345            <td class="header right">UC Irvine</td>
346         </tr>
347         <tr>
348            <td class="header left"></td>
349            <td class="header right">J. Gettys</td>
350         </tr>
351         <tr>
352            <td class="header left"></td>
353            <td class="header right">DEC</td>
354         </tr>
355         <tr>
356            <td class="header left"></td>
357            <td class="header right">H. Frystyk</td>
358         </tr>
359         <tr>
360            <td class="header left"></td>
361            <td class="header right">MIT/LCS</td>
362         </tr>
363         <tr>
364            <td class="header left"></td>
365            <td class="header right">May 1997</td>
366         </tr>
367      </table>
368      <p class="title">Use and Interpretation of HTTP Version Numbers</p>
369      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
370      <p>This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution
371         of this memo is unlimited.
372      </p>
373      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
374      <p>Copyright © The Internet Society (1997). All Rights Reserved.</p>
375      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
376      <p>HTTP request and response messages include an HTTP protocol version number. Some confusion exists concerning the proper use
377         and interpretation of HTTP version numbers, and concerning interoperability of HTTP implementations of different protocol
378         versions. This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing
379         HTTP/1.0 and HTTP/1.1 documents, but it does describe the intention of the authors of those documents, and can be considered
380         definitive when there is any ambiguity in those documents concerning HTTP version numbers, for all versions of HTTP.
381      </p> 
382      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note</a></h1> 
383      <p>Distribution of this document is unlimited. Please send comments to the HTTP working group at &lt;http-wg@cuckoo.hpl.hp.com&gt;.
384         Discussions of the working group are archived at &lt;URL:http://www.ics.uci.edu/pub/ietf/http/&gt;. General discussions about HTTP
385         and the applications which use HTTP should take place on the &lt;www-talk@w3.org&gt; mailing list.
386      </p> 
387      <hr class="noprint">
388      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
389      <ul class="toc">
390         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Introduction</a><ul class="toc">
391               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1.1">Robustness Principle</a></li>
392            </ul>
393         </li>
394         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">HTTP version numbers</a><ul class="toc">
395               <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#proxy.behavior">Proxy behavior</a></li>
396               <li class="tocline1">2.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.2">Compatibility between minor versions of the same major version</a></li>
397               <li class="tocline1">2.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2.3">Which version number to send in a message</a></li>
398            </ul>
399         </li>
400         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Security Considerations</a></li>
401         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a></li>
402         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#rfc.authors">Authors' Addresses</a></li>
403         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
404      </ul>
405      <hr class="noprint">
406      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction
407      </h1>
408      <p id="rfc.section.1.p.1">HTTP request and response messages include an HTTP protocol version number. According to section <a href="http://tools.ietf.org/html/rfc2068#section-3.1">3.1</a> of the HTTP/1.1 specification <a href="#RFC2068"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[2]</cite></a>,
409      </p>
410      <blockquote id="rfc.section.1.p.2" cite="http://tools.ietf.org/html/rfc2068#section-3.1"> 
411         <p>HTTP uses a "&lt;major&gt;.&lt;minor&gt;" numbering scheme to indicate versions of the protocol. The protocol versioning policy is intended
412            to allow the sender to indicate the format of a message and its capacity for understanding further HTTP communication, rather
413            than the features obtained via that communication. No change is made to the version number for the addition of message components
414            which do not affect communication behavior or which only add to extensible field values. The &lt;minor&gt; number is incremented
415            when the changes made to the protocol add features which do not change the general message parsing algorithm, but which may
416            add to the message semantics and imply additional capabilities of the sender. The &lt;major&gt; number is incremented when the format
417            of a message within the protocol is changed.
418         </p> 
419      </blockquote>
420      <p id="rfc.section.1.p.3">The same language appears in the description of HTTP/1.0 <a href="#RFC1945"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[1]</cite></a>.
421      </p>
422      <p id="rfc.section.1.p.4">Many readers of these documents have expressed some confusion about the intended meaning of this policy. Also, some people
423         who wrote HTTP implementations before RFC1945 <a href="#RFC1945"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[1]</cite></a> was issued were not aware of the intentions behind the introduction of version numbers in HTTP/1.0. This has led to debate
424         and inconsistency regarding the use and interpretation of HTTP version numbers, and has led to interoperability problems in
425         certain cases.
426      </p>
427      <p id="rfc.section.1.p.5">This document is an attempt to clarify the situation. It is not a modification of the intended meaning of the existing HTTP/1.0
428         and HTTP/1.1 documents, but it does describe the intention of the authors of those documents. In any case where either of
429         those two documents is ambiguous regarding the use and interpretation of HTTP version numbers, this document should be considered
430         the definitive as to the intentions of the designers of HTTP.
431      </p>
432      <p id="rfc.section.1.p.6">The specification described in this document is not part of the specification of any individual version of HTTP, such as HTTP/1.0
433         or HTTP/1.1. Rather, this document describes the use of HTTP version numbers in any version of HTTP (except for HTTP/0.9,
434         which did not include version numbers).
435      </p>
436      <p id="rfc.section.1.p.7">No vendor or other provider of an HTTP implementation should claim any compliance with any IETF HTTP specification unless
437         the implementation conditionally complies with the rules in this document.
438      </p>
439      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;Robustness Principle
440      </h2>
441      <p id="rfc.section.1.1.p.1">RFC791 <a href="#RFC0791"><cite title="Internet Protocol">[4]</cite></a> defines the "robustness principle" in section <a href="http://tools.ietf.org/html/rfc791#section-3.2">3.2</a>:
442      </p>
443      <blockquote id="rfc.section.1.1.p.2" cite="http://tools.ietf.org/html/rfc791#section-3.2"> 
444         <p>an implementation must be conservative in its sending behavior, and liberal in its receiving behavior.</p> 
445      </blockquote>
446      <p id="rfc.section.1.1.p.3">This principle applies to HTTP, as well. It is the fundamental basis for interpreting any part of the HTTP specification that
447         might still be ambiguous. In particular, implementations of HTTP <em class="bcp14">SHOULD NOT</em> reject messages or generate errors unnecessarily.
448      </p>
449      <hr class="noprint">
450      <h1 id="rfc.section.2" class="np"><a href="#rfc.section.2">2.</a>&nbsp;HTTP version numbers
451      </h1>
452      <p id="rfc.section.2.p.1">We start by restating the language quoted above from section <a href="http://tools.ietf.org/html/rfc2068#section-3.1">3.1</a> of the HTTP/1.1 specification <a href="#RFC2068"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[2]</cite></a>:
453      </p>
454      <dl class="empty">
455         <dd>It is, and has always been, the explicit intent of the HTTP specification that the interpretation of an HTTP message header
456            does not change between minor versions of the same major version.
457         </dd>
458         <dd>It is, and has always been, the explicit intent of the HTTP specification that an implementation receiving a message header
459            that it does not understand <em class="bcp14">MUST</em> ignore that header. (The word "ignore" has a special meaning for proxies; see section <a href="#proxy.behavior" title="Proxy behavior">2.1</a> below.)
460         </dd>
461      </dl>
462      <p id="rfc.section.2.p.2">To make this as clear as possible: The major version sent in a message <em class="bcp14">MAY</em> indicate the interpretation of other header fields. The minor version sent in a message <em class="bcp14">MUST NOT</em> indicate the interpretation of other header fields. This reflects the principle that the minor version labels the capability
463         of the sender, not the interpretation of the message.
464      </p>
465      <div class="note"> 
466         <p>Note: In a future version of HTTP, we may introduce a mechanism that explicitly requires a receiving implementation to reject
467            a message if it does not understand certain headers. For example, this might be implemented by means of a header that lists
468            a set of other message headers that must be understood by the recipient. Any implementation claiming at least conditional
469            compliance with this future version of HTTP would have to implement this mechanism. However, no implementation claiming compliance
470            with a lower HTTP version (in particular, HTTP/1.1) will have to implement this mechanism.
471         </p> 
472         <p>This future change may be required to support the Protocol Extension Protocol (PEP) <a href="#Kha"><cite title="HTTP/1.2 Extension Protocol (PEP)">[3]</cite></a>.
473         </p> 
474      </div>
475      <p id="rfc.section.2.p.4">One consequence of these rules is that an HTTP/1.1 message sent to an HTTP/1.0 recipient (or a recipient whose version is
476         unknown) <em class="bcp14">MUST</em> be constructed so that it remains a valid HTTP/1.0 message when all headers not defined in the HTTP/1.0 specification <a href="#RFC1945"><cite title="Hypertext Transfer Protocol -- HTTP/1.0">[1]</cite></a> are removed.
477      </p>
478      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="proxy.behavior" href="#proxy.behavior">Proxy behavior</a></h2>
479      <p id="rfc.section.2.1.p.1">A proxy <em class="bcp14">MUST</em> forward an unknown header, unless it is protected by a Connection header. A proxy implementing an HTTP version &gt;= 1.1 <em class="bcp14">MUST NOT</em> forward unknown headers that are protected by a Connection header, as described in section <a href="http://tools.ietf.org/html/rfc2068#section-14.10">14.10</a> of the HTTP/1.1 specification <a href="#RFC2068"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[2]</cite></a>.
480      </p>
481      <p id="rfc.section.2.1.p.2">We remind the reader that that HTTP version numbers are hop-by-hop components of HTTP messages, and are not end-to-end. That
482         is, an HTTP proxy never "forwards" an HTTP version number in either a request or response.
483      </p>
484      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;Compatibility between minor versions of the same major version
485      </h2>
486      <p id="rfc.section.2.2.p.1">An implementation of HTTP/x.b sending a message to a recipient whose version is known to be HTTP/x.a, a &lt; b, <em class="bcp14">MAY</em> send a header that is not defined in the specification for HTTP/x.a. For example, an HTTP/1.1 server may send a "Cache-control"
487         header to an HTTP/1.0 client; this may be useful if the immediate recipient is an HTTP/1.0 proxy, but the ultimate recipient
488         is an HTTP/1.1 client.
489      </p>
490      <p id="rfc.section.2.2.p.2">An implementation of HTTP/x.b sending a message to a recipient whose version is known to be HTTP/x.a, a &lt; b, <em class="bcp14">MUST NOT</em> depend on the recipient understanding a header not defined in the specification for HTTP/x.a. For example, HTTP/1.0 clients
491         cannot be expected to understand chunked encodings, and so an HTTP/1.1 server must never send "Transfer-Encoding: chunked"
492         in response to an HTTP/1.0 request.
493      </p>
494      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;Which version number to send in a message
495      </h2>
496      <p id="rfc.section.2.3.p.1">The most strenuous debate over the use of HTTP version numbers has centered on the problem of implementations that do not
497         follow the robustness principle, and which fail to produce useful results when they receive a message with an HTTP minor version
498         higher than the minor version they implement. We consider these implementations buggy, but we recognize that the robustness
499         principle also implies that message senders should make concessions to buggy implementations when this is truly necessary
500         for interoperation.
501      </p>
502      <p id="rfc.section.2.3.p.2">An HTTP client <em class="bcp14">SHOULD</em> send a request version equal to the highest version for which the client is at least conditionally compliant, and whose major
503         version is no higher than the highest version supported by the server, if this is known. An HTTP client <em class="bcp14">MUST NOT</em> send a version for which it is not at least conditionally compliant.
504      </p>
505      <p id="rfc.section.2.3.p.3">An HTTP client <em class="bcp14">MAY</em> send a lower request version, if it is known that the server incorrectly implements the HTTP specification, but only after
506         the client has determined that the server is actually buggy.
507      </p>
508      <p id="rfc.section.2.3.p.4">An HTTP server <em class="bcp14">SHOULD</em> send a response version equal to the highest version for which the server is at least conditionally compliant, and whose major
509         version is less than or equal to the one received in the request. An HTTP server <em class="bcp14">MUST NOT</em> send a version for which it is not at least conditionally compliant. A server <em class="bcp14">MAY</em> send a 505 (HTTP Version Not Supported) response if cannot send a response using the major version used in the client's request.
510      </p>
511      <p id="rfc.section.2.3.p.5">An HTTP server <em class="bcp14">MAY</em> send a lower response version, if it is known or suspected that the client incorrectly implements the HTTP specification,
512         but this should not be the default, and this <em class="bcp14">SHOULD</em> NOT be done if the request version is HTTP/1.1 or greater.
513      </p>
514      <hr class="noprint">
515      <h1 id="rfc.section.3" class="np"><a href="#rfc.section.3">3.</a>&nbsp;Security Considerations
516      </h1>
517      <p id="rfc.section.3.p.1">None, except to the extent that security mechanisms introduced in one version of HTTP might depend on the proper interpretation
518         of HTTP version numbers in older implementations.
519      </p>
520      <h1 class="np" id="rfc.references"><a href="#rfc.section.4" id="rfc.section.4">4.</a> References
521      </h1>
522      <table summary="References"> 
523         <tr>
524            <td class="reference"><b id="RFC1945">[1]</b></td>
525            <td class="top"><a href="mailto:timbl@w3.org" title="MIT, Laboratory for Computer Science">Berners-Lee, T.</a>, <a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.T.</a>, and <a href="mailto:frystyk@w3.org" title="W3 Consortium, MIT Laboratory for Computer Science">H.F. Nielsen</a>, “<a href="http://tools.ietf.org/html/rfc1945">Hypertext Transfer Protocol -- HTTP/1.0</a>”, RFC&nbsp;1945, May&nbsp;1996.
526            </td>
527         </tr> 
528         <tr>
529            <td class="reference"><b id="RFC2068">[2]</b></td>
530            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a href="mailto:timbl@w3.org" title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
531            </td>
532         </tr> 
533         <tr>
534            <td class="reference"><b id="Kha">[3]</b></td>
535            <td class="top">Khare, R., “HTTP/1.2 Extension Protocol (PEP)”.<br>HTTP Working Group, Work in Progress.
536            </td>
537         </tr> 
538         <tr>
539            <td class="reference"><b id="RFC0791">[4]</b></td>
540            <td class="top">Postel, J., “<a href="http://tools.ietf.org/html/rfc791">Internet Protocol</a>”, RFC&nbsp;791, September&nbsp;1981.
541            </td>
542         </tr> 
543      </table>
544      <hr class="noprint">
545      <h1 id="rfc.authors" class="np"><a href="#rfc.section.5" id="rfc.section.5">5.</a> <a href="#rfc.authors">Authors' Addresses</a></h1>
546      <address class="vcard"><span class="vcardline"><span class="fn">Jeffrey C. Mogul</span><span class="n hidden"><span class="family-name">Mogul</span><span class="given-name">Jeffrey C.</span></span></span><span class="org vcardline">Western Research Laboratory</span><span class="adr"><span class="street-address vcardline">Digital Equipment Corporation</span><span class="street-address vcardline">250 University Avenue</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">California</span>&nbsp;<span class="postal-code">94305</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">EMail: <a href="mailto:mogul@wrl.dec.com"><span class="email">mogul@wrl.dec.com</span></a></span></address>
547      <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span><span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Department of Information and Computer Science</span><span class="adr"><span class="street-address vcardline">University of California</span><span class="vcardline"><span class="locality">Irvine</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">92717-3425</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(714)824-4056"><span class="value">+1 (714) 824-4056</span></a></span><span class="vcardline">EMail: <a href="mailto:fielding@ics.uci.edu"><span class="email">fielding@ics.uci.edu</span></a></span></address>
548      <address class="vcard"><span class="vcardline"><span class="fn">Jim Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">Jim</span></span></span><span class="org vcardline">MIT Laboratory for Computer Science</span><span class="adr"><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)2588682"><span class="value">+1 (617) 258 8682</span></a></span><span class="vcardline">EMail: <a href="mailto:jg@w3.org"><span class="email">jg@w3.org</span></a></span></address>
549      <address class="vcard"><span class="vcardline"><span class="fn">Henrik Frystyk Nielsen</span><span class="n hidden"><span class="family-name">Frystyk</span></span></span><span class="org vcardline">W3 Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span>&nbsp;<span class="postal-code">02139</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)2588682"><span class="value">+1 (617) 258 8682</span></a></span><span class="vcardline">EMail: <a href="mailto:frystyk@w3.org"><span class="email">frystyk@w3.org</span></a></span></address>
550      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
551      <p>Copyright © The Internet Society (1997). All Rights Reserved.</p>
552      <p>This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise
553         explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without
554         restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative
555         works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references
556         to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards
557         in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to
558         translate it into languages other than English.
559      </p>
560      <p>The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees.</p>
561      <p>This document and the information contained herein is provided on an “AS IS” basis and THE INTERNET SOCIETY AND THE INTERNET
562         ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE
563         OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR
564         PURPOSE.
565      </p>
566      <hr class="noprint">
567      <h1 class="np"><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
568      <p>The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed
569         to pertain to the implementation or use of the technology described in this document or the extent to which any license under
570         such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.
571         Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be
572         found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available,
573         or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementors
574         or users of this specification can be obtained from the IETF Secretariat.
575      </p>
576      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
577         rights which may cover technology that may be required to practice this standard. Please address the information to the IETF
578         Executive Director.
579      </p>
580   </body>
581</html>
Note: See TracBrowser for help on using the repository browser.