source: draft-ietf-httpbis/latest/p0-introduction.html @ 2049

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

update generated html
  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 29.6 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>Hypertext Transfer Protocol (HTTP/1.1): Introduction</title><script>
7var buttonsAdded = false;
8
9function init() {
10  var fb = document.createElement("div");
11  fb.className = "feedback noprint";
12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
14
15  var bodyl = document.getElementsByTagName("body");
16  bodyl.item(0).appendChild(fb);
17}
18
19function feedback() {
20  toggleButtonsToElementsByName("h1");
21  toggleButtonsToElementsByName("h2");
22  toggleButtonsToElementsByName("h3");
23  toggleButtonsToElementsByName("h4");
24 
25  buttonsAdded = !buttonsAdded;
26}
27
28function toggleButtonsToElementsByName(name) {
29  var list = document.getElementsByTagName(name);
30  for (var i = 0; i < list.length; i++) {
31    toggleButton(list.item(i));
32  }
33}
34
35function toggleButton(node) {
36  if (! buttonsAdded) {
37 
38    // docname
39    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
40
41    var id = node.getAttribute("id");
42    // better id available?
43    var titlelinks = node.getElementsByTagName("a");
44    for (var i = 0; i < titlelinks.length; i++) {
45      var tl = titlelinks.item(i);
46      if (tl.getAttribute("id")) {
47        id = tl.getAttribute("id");
48      }
49    }
50
51    // ref
52    var ref = window.location.toString();
53    var hash = ref.indexOf("#");
54    if (hash != -1) {
55      ref = ref.substring(0, hash);
56    }
57    if (id != "") {
58      ref += "#" + id;
59    }
60   
61    // docname
62    var docname = "draft-ietf-httpbis-p0-introduction-latest";
63
64    // section
65    var section = node.textContent;
66    section = section.replace("\u00a0", " ");
67   
68    // build URI from template
69    var uri = template.replace("{docname}", encodeURIComponent(docname));
70    uri = uri.replace("{section}", encodeURIComponent(section));
71    uri = uri.replace("{ref}", encodeURIComponent(ref));
72 
73    var button = document.createElement("a");
74    button.className = "fbbutton noprint";
75    button.setAttribute("href", uri);
76    button.appendChild(document.createTextNode("send feedback"));
77    node.appendChild(button);
78  }
79  else {
80    var buttons = node.getElementsByTagName("a");
81    for (var i = 0; i < buttons.length; i++) {
82      var b = buttons.item(i);
83      if (b.className == "fbbutton noprint") {
84        node.removeChild(b);
85      }
86    }
87  }
88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
89a {
90  text-decoration: none;
91}
92a.smpl {
93  color: black;
94}
95a:hover {
96  text-decoration: underline;
97}
98a:active {
99  text-decoration: underline;
100}
101address {
102  margin-top: 1em;
103  margin-left: 2em;
104  font-style: normal;
105}
106body {
107  color: black;
108  font-family: verdana, helvetica, arial, sans-serif;
109  font-size: 10pt;
110  margin-right: 2em;
111}
112cite {
113  font-style: normal;
114}
115dl {
116  margin-left: 2em;
117}
118ul.empty {
119  list-style-type: none;
120}
121ul.empty li {
122  margin-top: .5em;
123}
124dl p {
125  margin-left: 0em;
126}
127dt {
128  margin-top: .5em;
129}
130h1 {
131  font-size: 14pt;
132  line-height: 21pt;
133  page-break-after: avoid;
134}
135h1.np {
136  page-break-before: always;
137}
138h1 a {
139  color: #333333;
140}
141h2 {
142  font-size: 12pt;
143  line-height: 15pt;
144  page-break-after: avoid;
145}
146h3, h4, h5, h6 {
147  font-size: 10pt;
148  page-break-after: avoid;
149}
150h2 a, h3 a, h4 a, h5 a, h6 a {
151  color: black;
152}
153img {
154  margin-left: 3em;
155}
156li {
157  margin-left: 2em;
158}
159ol {
160  margin-left: 2em;
161}
162ol.la {
163  list-style-type: lower-alpha;
164}
165ol.ua {
166  list-style-type: upper-alpha;
167}
168ol p {
169  margin-left: 0em;
170}
171p {
172  margin-left: 2em;
173}
174pre {
175  margin-left: 3em;
176  background-color: lightyellow;
177  padding: .25em;
178  page-break-inside: avoid;
179}
180pre.text2 {
181  border-style: dotted;
182  border-width: 1px;
183  background-color: #f0f0f0;
184  width: 69em;
185}
186pre.inline {
187  background-color: white;
188  padding: 0em;
189}
190pre.text {
191  border-style: dotted;
192  border-width: 1px;
193  background-color: #f8f8f8;
194  width: 69em;
195}
196pre.drawing {
197  border-style: solid;
198  border-width: 1px;
199  background-color: #f8f8f8;
200  padding: 2em;
201}
202table {
203  margin-left: 2em;
204}
205table.header {
206  border-spacing: 1px;
207  width: 95%;
208  font-size: 10pt;
209  color: white;
210}
211td.top {
212  vertical-align: top;
213}
214td.topnowrap {
215  vertical-align: top;
216  white-space: nowrap;
217}
218table.header td {
219  background-color: gray;
220  width: 50%;
221}
222td.reference {
223  vertical-align: top;
224  white-space: nowrap;
225  padding-right: 1em;
226}
227thead {
228  display:table-header-group;
229}
230ul.toc, ul.toc ul {
231  list-style: none;
232  margin-left: 1.5em;
233  padding-left: 0em;
234}
235ul.toc li {
236  line-height: 150%;
237  font-weight: bold;
238  font-size: 10pt;
239  margin-left: 0em;
240}
241ul.toc li li {
242  line-height: normal;
243  font-weight: normal;
244  font-size: 9pt;
245  margin-left: 0em;
246}
247li.excluded {
248  font-size: 0pt;
249}
250ul p {
251  margin-left: 0em;
252}
253ul.ind, ul.ind ul {
254  list-style: none;
255  margin-left: 1.5em;
256  padding-left: 0em;
257  page-break-before: avoid;
258}
259ul.ind li {
260  font-weight: bold;
261  line-height: 200%;
262  margin-left: 0em;
263}
264ul.ind li li {
265  font-weight: normal;
266  line-height: 150%;
267  margin-left: 0em;
268}
269.avoidbreak {
270  page-break-inside: avoid;
271}
272
273.comment {
274  background-color: yellow;
275}
276.center {
277  text-align: center;
278}
279.error {
280  color: red;
281  font-style: italic;
282  font-weight: bold;
283}
284.figure {
285  font-weight: bold;
286  text-align: center;
287  font-size: 9pt;
288}
289.filename {
290  color: #333333;
291  font-weight: bold;
292  font-size: 12pt;
293  line-height: 21pt;
294  text-align: center;
295}
296.fn {
297  font-weight: bold;
298}
299.hidden {
300  display: none;
301}
302.left {
303  text-align: left;
304}
305.right {
306  text-align: right;
307}
308.title {
309  color: #990000;
310  font-size: 18pt;
311  line-height: 18pt;
312  font-weight: bold;
313  text-align: center;
314  margin-top: 36pt;
315}
316.vcardline {
317  display: block;
318}
319.warning {
320  font-size: 14pt;
321  background-color: yellow;
322}
323.feedback {
324  position: fixed;
325  bottom: 1%;
326  right: 1%;
327  padding: 3px 5px;
328  color: white;
329  border-radius: 5px;
330  background: #a00000;
331  border: 1px solid silver;
332}
333.fbbutton {
334  margin-left: 1em;
335  color: #303030;
336  font-size: small;
337  font-weight: normal;
338  background: #d0d000;
339  padding: 1px 4px;
340  border: 1px solid silver;
341  border-radius: 5px;
342}
343
344@media print {
345  .noprint {
346    display: none;
347  }
348 
349  a {
350    color: black;
351    text-decoration: none;
352  }
353
354  table.header {
355    width: 90%;
356  }
357
358  td.header {
359    width: 50%;
360    color: black;
361    background-color: white;
362    vertical-align: top;
363    font-size: 12pt;
364  }
365
366  ul.toc a:nth-child(2)::after {
367    content: leader('.') target-counter(attr(href), page);
368  }
369 
370  ul.ind li li a {
371    content: target-counter(attr(href), page);
372  }
373 
374  .print2col {
375    column-count: 2;
376    -moz-column-count: 2;
377    column-fill: auto;
378  }
379}
380
381@page {
382  @top-left {
383       content: "Internet-Draft";
384  }
385  @top-right {
386       content: "December 2012";
387  }
388  @top-center {
389       content: "HTTP/1.1 Introduction";
390  }
391  @bottom-left {
392       content: "Fielding, et al.";
393  }
394  @bottom-center {
395       content: "Expires June 14, 2013";
396  }
397  @bottom-right {
398       content: "[Page " counter(page) "]";
399  }
400}
401
402@page:first {
403    @top-left {
404      content: normal;
405    }
406    @top-right {
407      content: normal;
408    }
409    @top-center {
410      content: normal;
411    }
412}
413</style><link rel="Contents" href="#rfc.toc">
414      <link rel="Author" href="#rfc.authors">
415      <link rel="Copyright" href="#rfc.copyrightnotice">
416      <link rel="Index" href="#rfc.index">
417      <link rel="Chapter" title="1 Introduction to the HTTP Document Series" href="#rfc.section.1">
418      <link rel="Chapter" title="2 What is HTTP?" href="#rfc.section.2">
419      <link rel="Chapter" href="#rfc.section.3" title="3 References">
420      <link href="p1-messaging.html" rel="next">
421      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.588, 2012-08-25 12:28:24, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
422      <link rel="schema.dct" href="http://purl.org/dc/terms/">
423      <meta name="dct.creator" content="Fielding, R.">
424      <meta name="dct.creator" content="Lafon, Y.">
425      <meta name="dct.creator" content="Nottingham, M.">
426      <meta name="dct.creator" content="Reschke, J. F.">
427      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p0-introduction-latest">
428      <meta name="dct.issued" scheme="ISO8601" content="2012-12-11">
429      <meta name="dct.abstract" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
430      <meta name="description" content="This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise known as HTTP/1.1.">
431   </head>
432   <body onload="init();">
433      <table class="header">
434         <tbody>
435            <tr>
436               <td class="left">HTTPbis Working Group</td>
437               <td class="right">R. Fielding, Editor</td>
438            </tr>
439            <tr>
440               <td class="left">Internet-Draft</td>
441               <td class="right">Adobe</td>
442            </tr>
443            <tr>
444               <td class="left">Intended status: Standards Track</td>
445               <td class="right">Y. Lafon, Editor</td>
446            </tr>
447            <tr>
448               <td class="left">Expires: June 14, 2013</td>
449               <td class="right">W3C</td>
450            </tr>
451            <tr>
452               <td class="left"></td>
453               <td class="right">M. Nottingham, Editor</td>
454            </tr>
455            <tr>
456               <td class="left"></td>
457               <td class="right">Akamai</td>
458            </tr>
459            <tr>
460               <td class="left"></td>
461               <td class="right">J. Reschke, Editor</td>
462            </tr>
463            <tr>
464               <td class="left"></td>
465               <td class="right">greenbytes</td>
466            </tr>
467            <tr>
468               <td class="left"></td>
469               <td class="right">December 11, 2012</td>
470            </tr>
471         </tbody>
472      </table>
473      <p class="title">Hypertext Transfer Protocol (HTTP/1.1): Introduction<br><span class="filename">draft-ietf-httpbis-p0-introduction-latest</span></p>
474      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
475      <p>This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise
476         known as HTTP/1.1.
477      </p>
478      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
479      <p>Discussion of this draft takes place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
480      </p> 
481      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
482      </p>   
483      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
484      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
485      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
486         working documents as Internet-Drafts. The list of current Internet-Drafts is at <a href="http://datatracker.ietf.org/drafts/current/">http://datatracker.ietf.org/drafts/current/</a>.
487      </p>
488      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
489         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
490         in progress”.
491      </p>
492      <p>This Internet-Draft will expire on June 14, 2013.</p>
493      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
494      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
495      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights
496         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
497         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
498         BSD License.
499      </p>
500      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
501         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
502         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
503         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
504         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
505         it into languages other than English.
506      </p>
507      <hr class="noprint">
508      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
509      <ul class="toc">
510         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.1">Introduction to the HTTP Document Series</a></li>
511         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#wat">What is HTTP?</a></li>
512         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
513               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
514               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
515            </ul>
516         </li>
517         <li><a href="#rfc.authors">Authors' Addresses</a></li>
518         <li><a href="#rfc.index">Index</a></li>
519      </ul>
520      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;Introduction to the HTTP Document Series
521      </h1>
522      <p id="rfc.section.1.p.1">This document is the first in a series that, collectively, define the HyperText Transfer Protocol, version 1.1; otherwise
523         known as HTTP/1.1.
524      </p>
525      <p id="rfc.section.1.p.2">The document series is organized as follows:</p>
526      <ul>
527         <li>HTTP/1.1 Introduction - this document</li>
528         <li><a href="#Part1" id="rfc.xref.Part1.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[Part1]</cite></a> HTTP/1.1 Message Routing and Syntax - How to parse a HTTP/1.1 (or below) message, and layer it onto connection-oriented protocols.
529            Also includes the HTTP and HTTPS URI schemes.
530         </li>
531         <li><a href="#Part2" id="rfc.xref.Part2.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> HTTP/1.1 Semantics and Payloads - Protocol elements such as methods, status codes, and payload-specific header fields. Also
532            includes content negotiation mechanisms.
533         </li>
534         <li><a href="#Part4" id="rfc.xref.Part4.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests">[Part4]</cite></a> HTTP/1.1 Conditional Requests - An extension to make requests contingent upon their current state.
535         </li>
536         <li><a href="#Part5" id="rfc.xref.Part5.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Range Requests">[Part5]</cite></a> HTTP/1.1 Range Requests - An extension to request that only a portion of a response be sent back.
537         </li>
538         <li><a href="#Part6" id="rfc.xref.Part6.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> HTTP/1.1 Caching - An extension to allow storage and reuse of responses.
539         </li>
540         <li><a href="#Part7" id="rfc.xref.Part7.1"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a> HTTP/1.1 Authentication Framework - extension enabling client authentication to proxy and origin servers
541         </li>
542      </ul>
543      <p id="rfc.section.1.p.4">The "core" of HTTP/1.1 is defined by the first two specifications. The remaining specifications in the series are generally
544         not mandatory for implementations, but might be required in some implementation or deployment scenarios; when this is the
545         case, it will be noted.
546      </p>
547      <p id="rfc.section.1.p.5">Collectively, these documents obsolete <a href="#RFC2616" id="rfc.xref.RFC2616.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. Note that many other specifications extend and refine the use of HTTP (generally, as protocol extensions, where allowed
548         by these specifications); they are not considered part of this series, but they are still "part of HTTP".
549      </p>
550      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="wat" href="#wat">What is HTTP?</a></h1>
551      <p id="rfc.section.2.p.1">The Hypertext Transfer Protocol (HTTP) is an application-level request/response protocol that uses extensible semantics and
552         MIME-like message payloads for flexible interaction with network-based hypertext information systems. HTTP relies upon the
553         Uniform Resource Identifier (URI) standard <a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a> to indicate the target resource and relationships between resources.
554      </p>
555      <p id="rfc.section.2.p.2">HTTP is a generic interface protocol for information systems. It is designed to hide the details of how a service is implemented
556         by presenting a uniform interface to clients that is independent of the types of resources provided. Likewise, servers do
557         not need to be aware of each client's purpose: an HTTP request can be considered in isolation rather than being associated
558         with a specific type of client or a predetermined sequence of application steps. The result is a protocol that can be used
559         effectively in many different contexts and for which implementations can evolve independently over time.
560      </p>
561      <p id="rfc.section.2.p.3">HTTP is also designed for use as an intermediation protocol for translating communication to and from non-HTTP information
562         systems. HTTP proxies and gateways can provide access to alternative information services by translating their diverse protocols
563         into a hypertext format that can be viewed and manipulated by clients in the same way as HTTP services.
564      </p>
565      <p id="rfc.section.2.p.4">One consequence of HTTP flexibility is that the protocol cannot be defined in terms of what occurs behind the interface. Instead,
566         we are limited to defining the syntax of communication, the intent of received communication, and the expected behavior of
567         recipients. If the communication is considered in isolation, then successful actions ought to be reflected in corresponding
568         changes to the observable interface provided by servers. However, since multiple clients might act in parallel and perhaps
569         at cross-purposes, we cannot require that such changes be observable beyond the scope of a single response.
570      </p>
571      <p id="rfc.section.2.p.5"> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TODO: remove corresponding text from p1 Introduction.]</span>
572      </p>
573      <h1 id="rfc.references"><a id="rfc.section.3" href="#rfc.section.3">3.</a> References
574      </h1>
575      <h2 id="rfc.references.1"><a href="#rfc.section.3.1" id="rfc.section.3.1">3.1</a> Normative References
576      </h2>
577      <table>             
578         <tr>
579            <td class="reference"><b id="Part1">[Part1]</b></td>
580            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), December&nbsp;2012.
581            </td>
582         </tr>
583         <tr>
584            <td class="reference"><b id="Part2">[Part2]</b></td>
585            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), December&nbsp;2012.
586            </td>
587         </tr>
588         <tr>
589            <td class="reference"><b id="Part4">[Part4]</b></td>
590            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), December&nbsp;2012.
591            </td>
592         </tr>
593         <tr>
594            <td class="reference"><b id="Part5">[Part5]</b></td>
595            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">Hypertext Transfer Protocol (HTTP/1.1): Range Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), December&nbsp;2012.
596            </td>
597         </tr>
598         <tr>
599            <td class="reference"><b id="Part6">[Part6]</b></td>
600            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Akamai">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">Hypertext Transfer Protocol (HTTP/1.1): Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), December&nbsp;2012.
601            </td>
602         </tr>
603         <tr>
604            <td class="reference"><b id="Part7">[Part7]</b></td>
605            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a> and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">Hypertext Transfer Protocol (HTTP/1.1): Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), December&nbsp;2012.
606            </td>
607         </tr>
608         <tr>
609            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
610            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
611            </td>
612         </tr>
613      </table>
614      <h2 id="rfc.references.2"><a href="#rfc.section.3.2" id="rfc.section.3.2">3.2</a> Informative References
615      </h2>
616      <table> 
617         <tr>
618            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
619            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
620            </td>
621         </tr>
622      </table>
623      <div class="avoidbreak">
624         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
625         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
626               (editor)
627               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
628         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
629               (editor)
630               <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">Email: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
631         <address class="vcard"><span class="vcardline"><span class="fn">Mark Nottingham</span>
632               (editor)
633               <span class="n hidden"><span class="family-name">Nottingham</span><span class="given-name">Mark</span></span></span><span class="org vcardline">Akamai</span><span class="vcardline">Email: <a href="mailto:mnot@mnot.net"><span class="email">mnot@mnot.net</span></a></span><span class="vcardline">URI: <a href="http://www.mnot.net/" class="url">http://www.mnot.net/</a></span></address>
634         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
635               (editor)
636               <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
637      </div>
638      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
639      <p class="noprint"><a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a>
640      </p>
641      <div class="print2col">
642         <ul class="ind">
643            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
644                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1</a>, <a href="#Part1"><b>3.1</b></a></li>
645                  <li><em>Part2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part2.1">1</a>, <a href="#Part2"><b>3.1</b></a></li>
646                  <li><em>Part4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part4.1">1</a>, <a href="#Part4"><b>3.1</b></a></li>
647                  <li><em>Part5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part5.1">1</a>, <a href="#Part5"><b>3.1</b></a></li>
648                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">1</a>, <a href="#Part6"><b>3.1</b></a></li>
649                  <li><em>Part7</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.1">1</a>, <a href="#Part7"><b>3.1</b></a></li>
650               </ul>
651            </li>
652            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
653                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>3.2</b></a></li>
654                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">2</a>, <a href="#RFC3986"><b>3.1</b></a></li>
655               </ul>
656            </li>
657         </ul>
658      </div>
659   </body>
660</html>
Note: See TracBrowser for help on using the repository browser.