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

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

update rfc2617.xml (ABNF alignment was off from published version), regen all HTML

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