source: draft-ietf-httpbis/01/p7-auth.html

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

update to latest version of rfc2629.xslt, regen all HTML

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 47.4 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>HTTP/1.1, part 7: Authentication</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}
24body {
25  color: black;
26  font-family: cambria, helvetica, arial, sans-serif;
27  font-size: 11pt;
28  margin-right: 2em;
29}
30cite {
31  font-style: normal;
32}
33dl {
34  margin-left: 2em;
35}
36ul.empty {
37  list-style-type: none;
38}
39ul.empty li {
40  margin-top: .5em;
41}
42dl p {
43  margin-left: 0em;
44}
45dt {
46  margin-top: .5em;
47}
48h1 {
49  font-size: 130%;
50  line-height: 21pt;
51  page-break-after: avoid;
52}
53h1.np {
54  page-break-before: always;
55}
56h2 {
57  font-size: 120%;
58  line-height: 15pt;
59  page-break-after: avoid;
60}
61h3 {
62  font-size: 110%;
63  page-break-after: avoid;
64}
65h4, h5, h6 {
66  page-break-after: avoid;
67}
68h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
69  color: black;
70}
71img {
72  margin-left: 3em;
73}
74li {
75  margin-left: 2em;
76}
77ol {
78  margin-left: 2em;
79}
80ol.la {
81  list-style-type: lower-alpha;
82}
83ol.ua {
84  list-style-type: upper-alpha;
85}
86ol p {
87  margin-left: 0em;
88}
89p {
90  margin-left: 2em;
91}
92pre {
93  margin-left: 3em;
94  background-color: lightyellow;
95  padding: .25em;
96  page-break-inside: avoid;
97}
98pre.text2 {
99  border-style: dotted;
100  border-width: 1px;
101  background-color: #f0f0f0;
102  width: 69em;
103}
104pre.inline {
105  background-color: white;
106  padding: 0em;
107}
108pre.text {
109  border-style: dotted;
110  border-width: 1px;
111  background-color: #f8f8f8;
112  width: 69em;
113}
114pre.drawing {
115  border-style: solid;
116  border-width: 1px;
117  background-color: #f8f8f8;
118  padding: 2em;
119}
120table {
121  margin-left: 2em;
122}
123table.header {
124  border-spacing: 1px;
125  width: 95%;
126  font-size: 11pt;
127  color: white;
128}
129td.top {
130  vertical-align: top;
131}
132td.topnowrap {
133  vertical-align: top;
134  white-space: nowrap;
135}
136table.header td {
137  background-color: gray;
138  width: 50%;
139}
140table.header a {
141  color: white;
142}
143td.reference {
144  vertical-align: top;
145  white-space: nowrap;
146  padding-right: 1em;
147}
148thead {
149  display:table-header-group;
150}
151ul.toc, ul.toc ul {
152  list-style: none;
153  margin-left: 1.5em;
154  padding-left: 0em;
155}
156ul.toc li {
157  line-height: 150%;
158  font-weight: bold;
159  margin-left: 0em;
160}
161ul.toc li li {
162  line-height: normal;
163  font-weight: normal;
164  font-size: 10pt;
165  margin-left: 0em;
166}
167li.excluded {
168  font-size: 0pt;
169}
170ul p {
171  margin-left: 0em;
172}
173.title, .filename, h1, h2, h3, h4 {
174  font-family: candara, helvetica, arial, sans-serif;
175}
176samp, tt, code, pre {
177  font: consolas, monospace;
178}
179ul.ind, ul.ind ul {
180  list-style: none;
181  margin-left: 1.5em;
182  padding-left: 0em;
183  page-break-before: avoid;
184}
185ul.ind li {
186  font-weight: bold;
187  line-height: 200%;
188  margin-left: 0em;
189}
190ul.ind li li {
191  font-weight: normal;
192  line-height: 150%;
193  margin-left: 0em;
194}
195.avoidbreak {
196  page-break-inside: avoid;
197}
198.bcp14 {
199  font-style: normal;
200  text-transform: lowercase;
201  font-variant: small-caps;
202}
203.comment {
204  background-color: yellow;
205}
206.center {
207  text-align: center;
208}
209.error {
210  color: red;
211  font-style: italic;
212  font-weight: bold;
213}
214.figure {
215  font-weight: bold;
216  text-align: center;
217  font-size: 10pt;
218}
219.filename {
220  color: #333333;
221  font-size: 75%;
222  font-weight: bold;
223  line-height: 21pt;
224  text-align: center;
225}
226.fn {
227  font-weight: bold;
228}
229.left {
230  text-align: left;
231}
232.right {
233  text-align: right;
234}
235.title {
236  color: green;
237  font-size: 150%;
238  line-height: 18pt;
239  font-weight: bold;
240  text-align: center;
241  margin-top: 36pt;
242}
243.warning {
244  font-size: 130%;
245  background-color: yellow;
246}
247
248
249@media print {
250  .noprint {
251    display: none;
252  }
253
254  a {
255    color: black;
256    text-decoration: none;
257  }
258
259  table.header {
260    width: 90%;
261  }
262
263  td.header {
264    width: 50%;
265    color: black;
266    background-color: white;
267    vertical-align: top;
268    font-size: 110%;
269  }
270
271  ul.toc a:nth-child(2)::after {
272    content: leader('.') target-counter(attr(href), page);
273  }
274
275  ul.ind li li a {
276    content: target-counter(attr(href), page);
277  }
278
279  .print2col {
280    column-count: 2;
281    -moz-column-count: 2;
282    column-fill: auto;
283  }
284}
285
286@page {
287  @top-left {
288       content: "Internet-Draft";
289  }
290  @top-right {
291       content: "January 2008";
292  }
293  @top-center {
294       content: "HTTP/1.1, Part 7";
295  }
296  @bottom-left {
297       content: "Fielding, et al.";
298  }
299  @bottom-center {
300       content: "Expires July 15, 2008";
301  }
302  @bottom-right {
303       content: "[Page " counter(page) "]";
304  }
305}
306
307@page:first {
308    @top-left {
309      content: normal;
310    }
311    @top-right {
312      content: normal;
313    }
314    @top-center {
315      content: normal;
316    }
317}
318</style><link rel="Contents" href="#rfc.toc">
319      <link rel="Author" href="#rfc.authors">
320      <link rel="Copyright" href="#rfc.copyright">
321      <link rel="Index" href="#rfc.index">
322      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
323      <link rel="Chapter" title="2 Status Code Definitions" href="#rfc.section.2">
324      <link rel="Chapter" title="3 Header Field Definitions" href="#rfc.section.3">
325      <link rel="Chapter" title="4 IANA Considerations" href="#rfc.section.4">
326      <link rel="Chapter" title="5 Security Considerations" href="#rfc.section.5">
327      <link rel="Chapter" title="6 Acknowledgments" href="#rfc.section.6">
328      <link rel="Chapter" href="#rfc.section.7" title="7 References">
329      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
330      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
331      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
332      <link rel="schema.dct" href="http://purl.org/dc/terms/">
333      <meta name="dct.creator" content="Fielding, R.">
334      <meta name="dct.creator" content="Gettys, J.">
335      <meta name="dct.creator" content="Mogul, J.">
336      <meta name="dct.creator" content="Frystyk, H.">
337      <meta name="dct.creator" content="Masinter, L.">
338      <meta name="dct.creator" content="Leach, P.">
339      <meta name="dct.creator" content="Berners-Lee, T.">
340      <meta name="dct.creator" content="Lafon, Y.">
341      <meta name="dct.creator" content="Reschke, J. F.">
342      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-01">
343      <meta name="dct.issued" scheme="ISO8601" content="2008-01-12">
344      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
345      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">
346      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">
347   </head>
348   <body>
349      <table class="header">
350         <tbody>
351            <tr>
352               <td class="left">Network Working Group</td>
353               <td class="right">R. Fielding, Editor</td>
354            </tr>
355            <tr>
356               <td class="left">Internet-Draft</td>
357               <td class="right">Day Software</td>
358            </tr>
359            <tr>
360               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
361               </td>
362               <td class="right">J. Gettys</td>
363            </tr>
364            <tr>
365               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2617">2617</a> (if approved)
366               </td>
367               <td class="right">One Laptop per Child</td>
368            </tr>
369            <tr>
370               <td class="left">Intended status: Standards Track</td>
371               <td class="right">J. Mogul</td>
372            </tr>
373            <tr>
374               <td class="left">Expires: July 15, 2008</td>
375               <td class="right">HP</td>
376            </tr>
377            <tr>
378               <td class="left"></td>
379               <td class="right">H. Frystyk</td>
380            </tr>
381            <tr>
382               <td class="left"></td>
383               <td class="right">Microsoft</td>
384            </tr>
385            <tr>
386               <td class="left"></td>
387               <td class="right">L. Masinter</td>
388            </tr>
389            <tr>
390               <td class="left"></td>
391               <td class="right">Adobe Systems</td>
392            </tr>
393            <tr>
394               <td class="left"></td>
395               <td class="right">P. Leach</td>
396            </tr>
397            <tr>
398               <td class="left"></td>
399               <td class="right">Microsoft</td>
400            </tr>
401            <tr>
402               <td class="left"></td>
403               <td class="right">T. Berners-Lee</td>
404            </tr>
405            <tr>
406               <td class="left"></td>
407               <td class="right">W3C/MIT</td>
408            </tr>
409            <tr>
410               <td class="left"></td>
411               <td class="right">Y. Lafon, Editor</td>
412            </tr>
413            <tr>
414               <td class="left"></td>
415               <td class="right">W3C</td>
416            </tr>
417            <tr>
418               <td class="left"></td>
419               <td class="right">J. Reschke, Editor</td>
420            </tr>
421            <tr>
422               <td class="left"></td>
423               <td class="right">greenbytes</td>
424            </tr>
425            <tr>
426               <td class="left"></td>
427               <td class="right">January 12, 2008</td>
428            </tr>
429         </tbody>
430      </table>
431      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-01</span></p>
432      <div id="rfc.status">
433         <h1><a href="#rfc.status">Status of this Memo</a></h1>
434         <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
435            is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
436            6 of BCP 79.
437         </p>
438         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
439            that other groups may also distribute working documents as Internet-Drafts.
440         </p>
441         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
442            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
443            in progress”.
444         </p>
445         <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
446         </p>
447         <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
448         </p>
449         <p>This Internet-Draft will expire on July 15, 2008.</p>
450      </div>
451      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
452      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
453         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
454         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
455         7 defines HTTP Authentication.
456      </p>
457      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
458      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
459         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
460      </p>
461      <p>This draft incorporates those issue resolutions that were either collected in the original RFC2616 errata list (&lt;<a href="http://purl.org/NET/http-errata">http://purl.org/NET/http-errata</a>&gt;), or which were agreed upon on the mailing list between October 2006 and November 2007 (as published in "draft-lafon-rfc2616bis-03").
462      </p>
463      <hr class="noprint">
464      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
465      <ul class="toc">
466         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
467               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
468            </ul>
469         </li>
470         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Status Code Definitions</a><ul>
471               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
472               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
473            </ul>
474         </li>
475         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
476               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
477               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
478               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
479               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
480            </ul>
481         </li>
482         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
483         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
484               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
485            </ul>
486         </li>
487         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
488         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
489               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
490               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
491            </ul>
492         </li>
493         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
494               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
495            </ul>
496         </li>
497         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul>
498               <li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
499               <li><a href="#rfc.section.B.2">B.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
500            </ul>
501         </li>
502         <li><a href="#rfc.index">Index</a></li>
503         <li><a href="#rfc.authors">Authors' Addresses</a></li>
504         <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
505      </ul>
506      <div id="introduction">
507         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
508         <p id="rfc.section.1.p.1">This document defines HTTP/1.1 access control and authentication. Right now it includes the extracted relevant sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> with only minor changes. The intention is to move the general framework for HTTP authentication here, as currently specified
509            in <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, and allow the individual authentication mechanisms to be defined elsewhere. This introduction will be rewritten when that
510            occurs.
511         </p>
512         <p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-response authentication mechanisms which can be used by a server to challenge a client request and by a client to
513            provide authentication information. The general framework for access authentication, and the specification of "basic" and
514            "digest" authentication, are specified in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.2"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. This specification adopts the definitions of "challenge" and "credentials" from that specification.
515         </p>
516         <div id="intro.requirements">
517            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
518            <p id="rfc.section.1.1.p.1">The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL"
519               in this document are to be interpreted as described in <a href="#RFC2119" id="rfc.xref.RFC2119.1"><cite title="Key words for use in RFCs to Indicate Requirement Levels">[RFC2119]</cite></a>.
520            </p>
521            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
522            </p>
523         </div>
524      </div>
525      <div>
526         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Status Code Definitions
527         </h1>
528         <div id="status.401">
529            <div id="rfc.iref.4.1"></div>
530            <div id="rfc.iref.s.1"></div>
531            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#status.401">401 Unauthorized</a></h2>
532            <p id="rfc.section.2.1.p.1">The request requires user authentication. The response <em class="bcp14">MUST</em> include a WWW-Authenticate header field (<a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.1" title="WWW-Authenticate">Section&nbsp;3.4</a>) containing a challenge applicable to the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Authorization header field (<a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;3.1</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
533               refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
534               already attempted authentication at least once, then the user <em class="bcp14">SHOULD</em> be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP
535               access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
536            </p>
537         </div>
538         <div id="status.407">
539            <div id="rfc.iref.4.2"></div>
540            <div id="rfc.iref.s.2"></div>
541            <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></h2>
542            <p id="rfc.section.2.2.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The
543               proxy <em class="bcp14">MUST</em> return a Proxy-Authenticate header field (<a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.1" title="Proxy-Authenticate">Section&nbsp;3.2</a>) containing a challenge applicable to the proxy for the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Proxy-Authorization header field (<a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.1" title="Proxy-Authorization">Section&nbsp;3.3</a>). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
544            </p>
545         </div>
546      </div>
547      <div id="header.fields">
548         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
549         <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
550         <div id="header.authorization">
551            <div id="rfc.iref.a.1"></div>
552            <div id="rfc.iref.h.1"></div>
553            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.authorization">Authorization</a></h2>
554            <p id="rfc.section.3.1.p.1">A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does
555               so by including an Authorization request-header field with the request. The Authorization field value consists of credentials
556               containing the authentication information of the user agent for the realm of the resource being requested.
557            </p>
558            <div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span>  Authorization  = "Authorization" ":" credentials
559</pre><p id="rfc.section.3.1.p.3">HTTP access authentication is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.5"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. If a request is authenticated and a realm specified, the same credentials <em class="bcp14">SHOULD</em> be valid for all other requests within this realm (assuming that the authentication scheme itself does not require otherwise,
560               such as credentials that vary according to a challenge value or using synchronized clocks).
561            </p>
562            <p id="rfc.section.3.1.p.4">When a shared cache (see <a href="p6-cache.html#shared.and.non-shared.caches" title="Shared and Non-Shared Caches">Section 8</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) receives a request containing an Authorization field, it <em class="bcp14">MUST NOT</em> return the corresponding response as a reply to any other request, unless one of the following specific exceptions holds:
563            </p>
564            <p id="rfc.section.3.1.p.5"></p>
565            <ol>
566               <li>If the response includes the "s-maxage" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But (if the specified maximum age has passed) a proxy cache <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
567                  the new request. (This is the defined behavior for s-maxage.) If the response includes "s-maxage=0", the proxy <em class="bcp14">MUST</em> always revalidate it before re-using it.
568               </li>
569               <li>If the response includes the "must-revalidate" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But if the response is stale, all caches <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
570                  the new request.
571               </li>
572               <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
573               </li>
574            </ol>
575         </div>
576         <div id="header.proxy-authenticate">
577            <div id="rfc.iref.p.1"></div>
578            <div id="rfc.iref.h.2"></div>
579            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
580            <p id="rfc.section.3.2.p.1">The Proxy-Authenticate response-header field <em class="bcp14">MUST</em> be included as part of a 407 (Proxy Authentication Required) response. The field value consists of a challenge that indicates
581               the authentication scheme and parameters applicable to the proxy for this Request-URI.
582            </p>
583            <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.2"></span>  Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
584</pre><p id="rfc.section.3.2.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.6"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to the current connection and <em class="bcp14">SHOULD NOT</em> be passed on to downstream clients. However, an intermediate proxy might need to obtain its own credentials by requesting
585               them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
586               header field.
587            </p>
588         </div>
589         <div id="header.proxy-authorization">
590            <div id="rfc.iref.p.2"></div>
591            <div id="rfc.iref.h.3"></div>
592            <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></h2>
593            <p id="rfc.section.3.3.p.1">The Proxy-Authorization request-header field allows the client to identify itself (or its user) to a proxy which requires
594               authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the
595               user agent for the proxy and/or realm of the resource being requested.
596            </p>
597            <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  Proxy-Authorization     = "Proxy-Authorization" ":" credentials
598</pre><p id="rfc.section.3.3.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.7"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. Unlike Authorization, the Proxy-Authorization header field applies only to the next outbound proxy that demanded authentication
599               using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
600               by the first outbound proxy that was expecting to receive credentials. A proxy <em class="bcp14">MAY</em> relay the credentials from the client request to the next proxy if that is the mechanism by which the proxies cooperatively
601               authenticate a given request.
602            </p>
603         </div>
604         <div id="header.www-authenticate">
605            <div id="rfc.iref.w.1"></div>
606            <div id="rfc.iref.h.4"></div>
607            <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></h2>
608            <p id="rfc.section.3.4.p.1">The WWW-Authenticate response-header field <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages. The field value consists of at least one challenge that indicates the
609               authentication scheme(s) and parameters applicable to the Request-URI.
610            </p>
611            <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
612</pre><p id="rfc.section.3.4.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.8"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one
613               challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
614               comma-separated list of authentication parameters.
615            </p>
616         </div>
617      </div>
618      <div id="IANA.considerations">
619         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
620         <p id="rfc.section.4.p.1">TBD.</p>
621      </div>
622      <div id="security.considerations">
623         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
624         <p id="rfc.section.5.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
625            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
626            make some suggestions for reducing security risks.
627         </p>
628         <div id="auth.credentials.and.idle.clients">
629            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
630            <p id="rfc.section.5.1.p.1">Existing HTTP clients and user agents typically retain authentication information indefinitely. HTTP/1.1 does not provide
631               a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
632               extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
633               but are not limited to:
634            </p>
635            <ul>
636               <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
637                  the user for credentials.
638               </li>
639               <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
640                  the server side of the application `knows' that there is no further reason for the client to retain the credentials.
641               </li>
642            </ul>
643            <p id="rfc.section.5.1.p.2">This is currently under separate study. There are a number of work-arounds to parts of this problem, and we encourage the
644               use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
645               in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
646               for discarding cached credentials under user control.
647            </p>
648         </div>
649      </div>
650      <div id="ack">
651         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
652         <p id="rfc.section.6.p.1">TBD.</p>
653      </div>
654      <h1 id="rfc.references"><a id="rfc.section.7" href="#rfc.section.7">7.</a> References
655      </h1>
656      <h2 id="rfc.references.1"><a href="#rfc.section.7.1" id="rfc.section.7.1">7.1</a> Normative References
657      </h2>
658      <table>
659         <tr>
660            <td class="reference"><b id="Part6">[Part6]</b></td>
661            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</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="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-01">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-01 (work in progress), January&nbsp;2008.
662            </td>
663         </tr>
664         <tr>
665            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
666            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
667            </td>
668         </tr>
669         <tr>
670            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
671            <td class="top"><a href="mailto:john@math.nwu.edu" title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a href="mailto:pbaker@verisign.com" title="Verisign Inc.">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com" title="AbiSource, Inc.">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com" title="Open Market, Inc.">L. Stewart</a>, “<a href="https://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
672            </td>
673         </tr>
674      </table>
675      <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References
676      </h2>
677      <table>
678         <tr>
679            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
680            <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="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
681            </td>
682         </tr>
683      </table>
684      <div id="compatibility">
685         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
686         <div id="changes.from.rfc.2616">
687            <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
688         </div>
689      </div>
690      <div>
691         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
692         </h1>
693         <div>
694            <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
695            </h2>
696            <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
697            </p>
698         </div>
699         <div>
700            <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
701            </h2>
702            <p id="rfc.section.B.2.p.1">Closed issues: </p>
703            <ul>
704               <li>&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
705               </li>
706            </ul>
707         </div>
708      </div>
709      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
710      <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.W">W</a> 
711      </p>
712      <div class="print2col">
713         <ul class="ind">
714            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
715                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>2.1</b></a></li>
716                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.2"><b>2.2</b></a></li>
717               </ul>
718            </li>
719            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
720                  <li>Authorization header&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">2.1</a>, <a href="#rfc.iref.a.1"><b>3.1</b></a></li>
721               </ul>
722            </li>
723            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
724                  <li><tt>Grammar</tt>&nbsp;&nbsp;
725                     <ul>
726                        <li><tt>Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>3.1</b></a></li>
727                        <li><tt>Proxy-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>3.2</b></a></li>
728                        <li><tt>Proxy-Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.3</b></a></li>
729                        <li><tt>WWW-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.4</b></a></li>
730                     </ul>
731                  </li>
732               </ul>
733            </li>
734            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
735                  <li>Headers&nbsp;&nbsp;
736                     <ul>
737                        <li>Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">2.1</a>, <a href="#rfc.iref.h.1"><b>3.1</b></a></li>
738                        <li>Proxy-Authenticate&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">2.2</a>, <a href="#rfc.iref.h.2"><b>3.2</b></a></li>
739                        <li>Proxy-Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">2.2</a>, <a href="#rfc.iref.h.3"><b>3.3</b></a></li>
740                        <li>WWW-Authenticate&nbsp;&nbsp;<a href="#rfc.xref.header.www-authenticate.1">2.1</a>, <a href="#rfc.iref.h.4"><b>3.4</b></a></li>
741                     </ul>
742                  </li>
743               </ul>
744            </li>
745            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
746                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a>, <a href="#Part6"><b>7.1</b></a><ul>
747                        <li><em>Section 8</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a></li>
748                     </ul>
749                  </li>
750                  <li>Proxy-Authenticate header&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">2.2</a>, <a href="#rfc.iref.p.1"><b>3.2</b></a></li>
751                  <li>Proxy-Authorization header&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">2.2</a>, <a href="#rfc.iref.p.2"><b>3.3</b></a></li>
752               </ul>
753            </li>
754            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
755                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>7.1</b></a></li>
756                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>7.2</b></a>, <a href="#rfc.xref.RFC2616.2">B.1</a></li>
757                  <li><em>RFC2617</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2617.1">1</a>, <a href="#rfc.xref.RFC2617.2">1</a>, <a href="#rfc.xref.RFC2617.3">2.1</a>, <a href="#rfc.xref.RFC2617.4">2.2</a>, <a href="#rfc.xref.RFC2617.5">3.1</a>, <a href="#rfc.xref.RFC2617.6">3.2</a>, <a href="#rfc.xref.RFC2617.7">3.3</a>, <a href="#rfc.xref.RFC2617.8">3.4</a>, <a href="#RFC2617"><b>7.1</b></a></li>
758               </ul>
759            </li>
760            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
761                  <li>Status Codes&nbsp;&nbsp;
762                     <ul>
763                        <li>401 Unauthorized&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>2.1</b></a></li>
764                        <li>407 Proxy Authentication Required&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>2.2</b></a></li>
765                     </ul>
766                  </li>
767               </ul>
768            </li>
769            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
770                  <li>WWW-Authenticate header&nbsp;&nbsp;<a href="#rfc.xref.header.www-authenticate.1">2.1</a>, <a href="#rfc.iref.w.1"><b>3.4</b></a></li>
771               </ul>
772            </li>
773         </ul>
774      </div>
775      <div class="avoidbreak">
776         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
777         <p><b>Roy T. Fielding</b>
778            (editor)
779            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><br>EMail: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
780         <p><b>Jim Gettys</b><br>One Laptop per Child<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>EMail: <a href="mailto:jg@laptop.org">jg@laptop.org</a><br>URI: <a href="http://www.laptop.org/">http://www.laptop.org/</a></p>
781         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>EMail: <a href="mailto:JeffMogul@acm.org">JeffMogul@acm.org</a></p>
782         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>EMail: <a href="mailto:henrikn@microsoft.com">henrikn@microsoft.com</a></p>
783         <p><b>Larry Masinter</b><br>Adobe Systems, Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>EMail: <a href="mailto:LMM@acm.org">LMM@acm.org</a><br>URI: <a href="http://larry.masinter.net/">http://larry.masinter.net/</a></p>
784         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>EMail: <a href="mailto:paulle@microsoft.com">paulle@microsoft.com</a></p>
785         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>EMail: <a href="mailto:timbl@w3.org">timbl@w3.org</a><br>URI: <a href="http://www.w3.org/People/Berners-Lee/">http://www.w3.org/People/Berners-Lee/</a></p>
786         <p><b>Yves Lafon</b>
787            (editor)
788            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>EMail: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
789         <p><b>Julian F. Reschke</b>
790            (editor)
791            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><br>EMail: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
792      </div>
793      <div id="rfc.copyright">
794         <h1><a href="#rfc.copyright">Full Copyright Statement</a></h1>
795         <p>Copyright © The IETF Trust (2008).</p>
796         <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
797            authors retain all their rights.
798         </p>
799         <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
800            HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
801            DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
802            WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
803         </p>
804      </div>
805      <div id="rfc.ipr">
806         <h1><a href="#rfc.ipr">Intellectual Property</a></h1>
807         <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
808            be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
809            license under such rights might or might not be available; nor does it represent that it has made any independent effort to
810            identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
811            BCP 79.
812         </p>
813         <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
814            of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
815            of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
816         </p>
817         <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
818            rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
819            at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
820         </p>
821      </div>
822   </body>
823</html>
Note: See TracBrowser for help on using the repository browser.