source: draft-ietf-httpbis/10/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: 69.2 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.tt {
124  vertical-align: top;
125  border-color: gray;
126}
127table.tt th {
128  border-color: gray;
129}
130table.tt td {
131  border-color: gray;
132}
133table.all {
134  border-style: solid;
135  border-width: 2px;
136}
137table.full {
138  border-style: solid;
139  border-width: 2px;
140}
141table.tt td {
142  vertical-align: top;
143}
144table.all td {
145  border-style: solid;
146  border-width: 1px;
147}
148table.full td {
149  border-style: none solid;
150  border-width: 1px;
151}
152table.tt th {
153  vertical-align: top;
154}
155table.all th {
156  border-style: solid;
157  border-width: 1px;
158}
159table.full th {
160  border-style: solid;
161  border-width: 1px 1px 2px 1px;
162}
163table.headers th {
164  border-style: none none solid none;
165  border-width: 2px;
166}
167table.left {
168  margin-right: auto;
169}
170table.right {
171  margin-left: auto;
172}
173table.center {
174  margin-left: auto;
175  margin-right: auto;
176}
177caption {
178  caption-side: bottom;
179  font-weight: bold;
180  font-size: 10pt;
181  margin-top: .5em;
182}
183
184table.header {
185  border-spacing: 1px;
186  width: 95%;
187  font-size: 11pt;
188  color: white;
189}
190td.top {
191  vertical-align: top;
192}
193td.topnowrap {
194  vertical-align: top;
195  white-space: nowrap;
196}
197table.header td {
198  background-color: gray;
199  width: 50%;
200}
201table.header a {
202  color: white;
203}
204td.reference {
205  vertical-align: top;
206  white-space: nowrap;
207  padding-right: 1em;
208}
209thead {
210  display:table-header-group;
211}
212ul.toc, ul.toc ul {
213  list-style: none;
214  margin-left: 1.5em;
215  padding-left: 0em;
216}
217ul.toc li {
218  line-height: 150%;
219  font-weight: bold;
220  margin-left: 0em;
221}
222ul.toc li li {
223  line-height: normal;
224  font-weight: normal;
225  font-size: 10pt;
226  margin-left: 0em;
227}
228li.excluded {
229  font-size: 0pt;
230}
231ul p {
232  margin-left: 0em;
233}
234.title, .filename, h1, h2, h3, h4 {
235  font-family: candara, helvetica, arial, sans-serif;
236}
237samp, tt, code, pre {
238  font: consolas, monospace;
239}
240ul.ind, ul.ind ul {
241  list-style: none;
242  margin-left: 1.5em;
243  padding-left: 0em;
244  page-break-before: avoid;
245}
246ul.ind li {
247  font-weight: bold;
248  line-height: 200%;
249  margin-left: 0em;
250}
251ul.ind li li {
252  font-weight: normal;
253  line-height: 150%;
254  margin-left: 0em;
255}
256.avoidbreak {
257  page-break-inside: avoid;
258}
259.bcp14 {
260  font-style: normal;
261  text-transform: lowercase;
262  font-variant: small-caps;
263}
264.comment {
265  background-color: yellow;
266}
267.center {
268  text-align: center;
269}
270.error {
271  color: red;
272  font-style: italic;
273  font-weight: bold;
274}
275.figure {
276  font-weight: bold;
277  text-align: center;
278  font-size: 10pt;
279}
280.filename {
281  color: #333333;
282  font-size: 75%;
283  font-weight: bold;
284  line-height: 21pt;
285  text-align: center;
286}
287.fn {
288  font-weight: bold;
289}
290.left {
291  text-align: left;
292}
293.right {
294  text-align: right;
295}
296.title {
297  color: green;
298  font-size: 150%;
299  line-height: 18pt;
300  font-weight: bold;
301  text-align: center;
302  margin-top: 36pt;
303}
304.warning {
305  font-size: 130%;
306  background-color: yellow;
307}
308
309
310@media print {
311  .noprint {
312    display: none;
313  }
314
315  a {
316    color: black;
317    text-decoration: none;
318  }
319
320  table.header {
321    width: 90%;
322  }
323
324  td.header {
325    width: 50%;
326    color: black;
327    background-color: white;
328    vertical-align: top;
329    font-size: 110%;
330  }
331
332  ul.toc a:nth-child(2)::after {
333    content: leader('.') target-counter(attr(href), page);
334  }
335
336  ul.ind li li a {
337    content: target-counter(attr(href), page);
338  }
339
340  .print2col {
341    column-count: 2;
342    -moz-column-count: 2;
343    column-fill: auto;
344  }
345}
346
347@page {
348  @top-left {
349       content: "Internet-Draft";
350  }
351  @top-right {
352       content: "July 2010";
353  }
354  @top-center {
355       content: "HTTP/1.1, Part 7";
356  }
357  @bottom-left {
358       content: "Fielding, et al.";
359  }
360  @bottom-center {
361       content: "Expires January 13, 2011";
362  }
363  @bottom-right {
364       content: "[Page " counter(page) "]";
365  }
366}
367
368@page:first {
369    @top-left {
370      content: normal;
371    }
372    @top-right {
373      content: normal;
374    }
375    @top-center {
376      content: normal;
377    }
378}
379</style><link rel="Contents" href="#rfc.toc">
380      <link rel="Author" href="#rfc.authors">
381      <link rel="Copyright" href="#rfc.copyrightnotice">
382      <link rel="Index" href="#rfc.index">
383      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
384      <link rel="Chapter" title="2 Status Code Definitions" href="#rfc.section.2">
385      <link rel="Chapter" title="3 Header Field Definitions" href="#rfc.section.3">
386      <link rel="Chapter" title="4 IANA Considerations" href="#rfc.section.4">
387      <link rel="Chapter" title="5 Security Considerations" href="#rfc.section.5">
388      <link rel="Chapter" title="6 Acknowledgments" href="#rfc.section.6">
389      <link rel="Chapter" href="#rfc.section.7" title="7 References">
390      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
391      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
392      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
393      <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/">
394      <link rel="schema.dct" href="http://purl.org/dc/terms/">
395      <meta name="dct.creator" content="Fielding, R.">
396      <meta name="dct.creator" content="Gettys, J.">
397      <meta name="dct.creator" content="Mogul, J.">
398      <meta name="dct.creator" content="Frystyk, H.">
399      <meta name="dct.creator" content="Masinter, L.">
400      <meta name="dct.creator" content="Leach, P.">
401      <meta name="dct.creator" content="Berners-Lee, T.">
402      <meta name="dct.creator" content="Lafon, Y.">
403      <meta name="dct.creator" content="Reschke, J. F.">
404      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-10">
405      <meta name="dct.issued" scheme="ISO8601" content="2010-07-12">
406      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
407      <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.">
408      <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.">
409   </head>
410   <body>
411      <table class="header">
412         <tbody>
413            <tr>
414               <td class="left">HTTPbis Working Group</td>
415               <td class="right">R. Fielding, Editor</td>
416            </tr>
417            <tr>
418               <td class="left">Internet-Draft</td>
419               <td class="right">Day Software</td>
420            </tr>
421            <tr>
422               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
423               </td>
424               <td class="right">J. Gettys</td>
425            </tr>
426            <tr>
427               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2617">2617</a> (if approved)
428               </td>
429               <td class="right">Alcatel-Lucent</td>
430            </tr>
431            <tr>
432               <td class="left">Intended status: Standards Track</td>
433               <td class="right">J. Mogul</td>
434            </tr>
435            <tr>
436               <td class="left">Expires: January 13, 2011</td>
437               <td class="right">HP</td>
438            </tr>
439            <tr>
440               <td class="left"></td>
441               <td class="right">H. Frystyk</td>
442            </tr>
443            <tr>
444               <td class="left"></td>
445               <td class="right">Microsoft</td>
446            </tr>
447            <tr>
448               <td class="left"></td>
449               <td class="right">L. Masinter</td>
450            </tr>
451            <tr>
452               <td class="left"></td>
453               <td class="right">Adobe Systems</td>
454            </tr>
455            <tr>
456               <td class="left"></td>
457               <td class="right">P. Leach</td>
458            </tr>
459            <tr>
460               <td class="left"></td>
461               <td class="right">Microsoft</td>
462            </tr>
463            <tr>
464               <td class="left"></td>
465               <td class="right">T. Berners-Lee</td>
466            </tr>
467            <tr>
468               <td class="left"></td>
469               <td class="right">W3C/MIT</td>
470            </tr>
471            <tr>
472               <td class="left"></td>
473               <td class="right">Y. Lafon, Editor</td>
474            </tr>
475            <tr>
476               <td class="left"></td>
477               <td class="right">W3C</td>
478            </tr>
479            <tr>
480               <td class="left"></td>
481               <td class="right">J. Reschke, Editor</td>
482            </tr>
483            <tr>
484               <td class="left"></td>
485               <td class="right">greenbytes</td>
486            </tr>
487            <tr>
488               <td class="left"></td>
489               <td class="right">July 12, 2010</td>
490            </tr>
491         </tbody>
492      </table>
493      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-10</span></p>
494      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
495      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
496         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
497         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
498         7 defines HTTP Authentication.
499      </p>
500      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
501      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
502         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;.
503      </p>
504      <p>The changes in this draft are summarized in <a href="#changes.since.09" title="Since draft-ietf-httpbis-p7-auth-09">Appendix&nbsp;C.11</a>.
505      </p>
506      <div id="rfc.status">
507         <h1><a href="#rfc.status">Status of This Memo</a></h1>
508         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
509         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
510            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>.
511         </p>
512         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
513            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
514            in progress”.
515         </p>
516         <p>This Internet-Draft will expire on January 13, 2011.</p>
517      </div>
518      <div id="rfc.copyrightnotice">
519         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
520         <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
521         <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
522            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
523            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
524            BSD License.
525         </p>
526         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
527            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
528            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
529            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
530            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
531            it into languages other than English.
532         </p>
533      </div>
534      <hr class="noprint">
535      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
536      <ul class="toc">
537         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
538               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
539               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
540                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
541                     <li><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
542                  </ul>
543               </li>
544            </ul>
545         </li>
546         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
547               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
548               <li><a href="#rfc.section.2.2">2.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
549            </ul>
550         </li>
551         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
552               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
553               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
554               <li><a href="#rfc.section.3.3">3.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
555               <li><a href="#rfc.section.3.4">3.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
556            </ul>
557         </li>
558         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
559               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
560               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
561            </ul>
562         </li>
563         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
564               <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>
565            </ul>
566         </li>
567         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
568         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
569               <li><a href="#rfc.section.7.1">7.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
570               <li><a href="#rfc.section.7.2">7.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
571            </ul>
572         </li>
573         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
574               <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>
575            </ul>
576         </li>
577         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
578         <li><a href="#rfc.section.C">C.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
579               <li><a href="#rfc.section.C.1">C.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
580               <li><a href="#rfc.section.C.2">C.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
581               <li><a href="#rfc.section.C.3">C.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p7-auth-01</a></li>
582               <li><a href="#rfc.section.C.4">C.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></li>
583               <li><a href="#rfc.section.C.5">C.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></li>
584               <li><a href="#rfc.section.C.6">C.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></li>
585               <li><a href="#rfc.section.C.7">C.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></li>
586               <li><a href="#rfc.section.C.8">C.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></li>
587               <li><a href="#rfc.section.C.9">C.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></li>
588               <li><a href="#rfc.section.C.10">C.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></li>
589               <li><a href="#rfc.section.C.11">C.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></li>
590            </ul>
591         </li>
592         <li><a href="#rfc.index">Index</a></li>
593         <li><a href="#rfc.authors">Authors' Addresses</a></li>
594      </ul>
595      <div id="introduction">
596         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
597         <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
598            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
599            occurs.
600         </p>
601         <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
602            provide authentication information. The general framework for access authentication, and the specification of "basic" and
603            "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.
604         </p>
605         <div id="intro.requirements">
606            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
607            <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"
608               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>.
609            </p>
610            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
611               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
612               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
613               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
614            </p>
615         </div>
616         <div id="notation">
617            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
618            <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF, with the list rule expanded.
619            </p>
620            <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
621               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
622               and WSP (whitespace).
623            </p>
624            <div id="core.rules">
625               <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a href="#core.rules">Core Rules</a></h3>
626               <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
627               </p>
628               <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>         = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
629</pre></div>
630            <div id="abnf.dependencies">
631               <h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
632               <p id="rfc.section.1.2.2.p.1"> The ABNF rules below are defined in other specifications:</p>
633               <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#abnf.dependencies" class="smpl">challenge</a>   = &lt;challenge, defined in <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, <a href="https://tools.ietf.org/html/rfc2617#section-1.2">Section 1.2</a>&gt;
634  <a href="#abnf.dependencies" class="smpl">credentials</a> = &lt;credentials, defined in <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, <a href="https://tools.ietf.org/html/rfc2617#section-1.2">Section 1.2</a>&gt;
635</pre></div>
636         </div>
637      </div>
638      <div id="status.code.definitions">
639         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
640         <div id="status.401">
641            <div id="rfc.iref.4.1"></div>
642            <div id="rfc.iref.s.1"></div>
643            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#status.401">401 Unauthorized</a></h2>
644            <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
645               refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
646               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
647               access authentication is explained 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>.
648            </p>
649         </div>
650         <div id="status.407">
651            <div id="rfc.iref.4.2"></div>
652            <div id="rfc.iref.s.2"></div>
653            <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>
654            <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
655               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.6"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
656            </p>
657         </div>
658      </div>
659      <div id="header.fields">
660         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
661         <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
662         <div id="header.authorization">
663            <div id="rfc.iref.a.1"></div>
664            <div id="rfc.iref.h.1"></div>
665            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#header.authorization">Authorization</a></h2>
666            <p id="rfc.section.3.1.p.1">The "Authorization" request-header field allows a user agent to authenticate itself with a server -- usually, but not necessarily,
667               after receiving a 401 (Unauthorized) response. Its value consists of credentials containing information of the user agent
668               for the realm of the resource being requested.
669            </p>
670            <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.authorization" class="smpl">Authorization</a>   = "Authorization" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.authorization" class="smpl">Authorization-v</a>
671  <a href="#header.authorization" class="smpl">Authorization-v</a> = <a href="#abnf.dependencies" class="smpl">credentials</a>
672</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.7"><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,
673               such as credentials that vary according to a challenge value or using synchronized clocks).
674            </p>
675            <p id="rfc.section.3.1.p.4">When a shared cache (see <a href="p6-cache.html#shared.and.non-shared.caches">Section 1.2</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:
676            </p>
677            <p id="rfc.section.3.1.p.5"></p>
678            <ol>
679               <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
680                  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.
681               </li>
682               <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
683                  the new request.
684               </li>
685               <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
686               </li>
687            </ol>
688         </div>
689         <div id="header.proxy-authenticate">
690            <div id="rfc.iref.p.1"></div>
691            <div id="rfc.iref.h.2"></div>
692            <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>
693            <p id="rfc.section.3.2.p.1">The "Proxy-Authenticate" response-header field consists of a challenge that indicates the authentication scheme and parameters
694               applicable to the proxy for this Effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It <em class="bcp14">MUST</em> be included as part of a 407 (Proxy Authentication Required) response.
695            </p>
696            <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a>   = "Proxy-Authenticate" ":" <a href="#core.rules" class="smpl">OWS</a>
697                         <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a>
698  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a> = 1#<a href="#abnf.dependencies" class="smpl">challenge</a>
699</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.8"><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
700               them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
701               header field.
702            </p>
703         </div>
704         <div id="header.proxy-authorization">
705            <div id="rfc.iref.p.2"></div>
706            <div id="rfc.iref.h.3"></div>
707            <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>
708            <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
709               authentication. Its value consists of credentials containing the authentication information of the user agent for the proxy
710               and/or realm of the resource being requested.
711            </p>
712            <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span>  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a>   = "Proxy-Authorization" ":" <a href="#core.rules" class="smpl">OWS</a>
713                          <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a>
714  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a> = <a href="#abnf.dependencies" class="smpl">credentials</a>
715</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.9"><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
716               using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
717               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
718               authenticate a given request.
719            </p>
720         </div>
721         <div id="header.www-authenticate">
722            <div id="rfc.iref.w.1"></div>
723            <div id="rfc.iref.h.4"></div>
724            <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>
725            <p id="rfc.section.3.4.p.1">The "WWW-Authenticate" response-header field consists of at least one challenge that indicates the authentication scheme(s)
726               and parameters applicable to the Effective Request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages.
727            </p>
728            <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a>   = "WWW-Authenticate" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a>
729  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a> = 1#<a href="#abnf.dependencies" class="smpl">challenge</a>
730</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.10"><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
731               challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
732               comma-separated list of authentication parameters.
733            </p>
734         </div>
735      </div>
736      <div id="IANA.considerations">
737         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
738         <div id="status.code.registration">
739            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
740            <p id="rfc.section.4.1.p.1">The HTTP Status Code Registry located at &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; should be updated with the registrations below:
741            </p>
742            <div id="rfc.table.1">
743               <div id="iana.status.code.registration.table"></div>
744               <table class="tt full left" cellpadding="3" cellspacing="0">
745                  <thead>
746                     <tr>
747                        <th>Value</th>
748                        <th>Description</th>
749                        <th>Reference</th>
750                     </tr>
751                  </thead>
752                  <tbody>
753                     <tr>
754                        <td class="left">401</td>
755                        <td class="left">Unauthorized</td>
756                        <td class="left"><a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;2.1</a> 
757                        </td>
758                     </tr>
759                     <tr>
760                        <td class="left">407</td>
761                        <td class="left">Proxy Authentication Required</td>
762                        <td class="left"><a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;2.2</a> 
763                        </td>
764                     </tr>
765                  </tbody>
766               </table>
767            </div>
768         </div>
769         <div id="message.header.registration">
770            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#message.header.registration">Message Header Registration</a></h2>
771            <p id="rfc.section.4.2.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
772            </p>
773            <div id="rfc.table.2">
774               <div id="iana.header.registration.table"></div>
775               <table class="tt full left" cellpadding="3" cellspacing="0">
776                  <thead>
777                     <tr>
778                        <th>Header Field Name</th>
779                        <th>Protocol</th>
780                        <th>Status</th>
781                        <th>Reference</th>
782                     </tr>
783                  </thead>
784                  <tbody>
785                     <tr>
786                        <td class="left">Authorization</td>
787                        <td class="left">http</td>
788                        <td class="left">standard</td>
789                        <td class="left"><a href="#header.authorization" id="rfc.xref.header.authorization.2" title="Authorization">Section&nbsp;3.1</a> 
790                        </td>
791                     </tr>
792                     <tr>
793                        <td class="left">Proxy-Authenticate</td>
794                        <td class="left">http</td>
795                        <td class="left">standard</td>
796                        <td class="left"><a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;3.2</a> 
797                        </td>
798                     </tr>
799                     <tr>
800                        <td class="left">Proxy-Authorization</td>
801                        <td class="left">http</td>
802                        <td class="left">standard</td>
803                        <td class="left"><a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;3.3</a> 
804                        </td>
805                     </tr>
806                     <tr>
807                        <td class="left">WWW-Authenticate</td>
808                        <td class="left">http</td>
809                        <td class="left">standard</td>
810                        <td class="left"><a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section&nbsp;3.4</a> 
811                        </td>
812                     </tr>
813                  </tbody>
814               </table>
815            </div>
816            <p id="rfc.section.4.2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
817         </div>
818      </div>
819      <div id="security.considerations">
820         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
821         <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
822            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
823            make some suggestions for reducing security risks.
824         </p>
825         <div id="auth.credentials.and.idle.clients">
826            <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>
827            <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
828               a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
829               extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
830               but are not limited to:
831            </p>
832            <ul>
833               <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
834                  the user for credentials.
835               </li>
836               <li>Applications which include a session termination indication (such as a "logout" or "commit" button on a page) after which
837                  the server side of the application "knows" that there is no further reason for the client to retain the credentials.
838               </li>
839            </ul>
840            <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
841               use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
842               in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
843               for discarding cached credentials under user control.
844            </p>
845         </div>
846      </div>
847      <div id="ack">
848         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
849         <p id="rfc.section.6.p.1"><span class="comment" id="acks">[<a href="#acks" class="smpl">acks</a>: TBD.]</span> 
850         </p>
851      </div>
852      <h1 id="rfc.references"><a id="rfc.section.7" href="#rfc.section.7">7.</a> References
853      </h1>
854      <h2 id="rfc.references.1"><a href="#rfc.section.7.1" id="rfc.section.7.1">7.1</a> Normative References
855      </h2>
856      <table>
857         <tr>
858            <td class="reference"><b id="Part1">[Part1]</b></td>
859            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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-p1-messaging-10">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-10 (work in progress), July&nbsp;2010.
860            </td>
861         </tr>
862         <tr>
863            <td class="reference"><b id="Part6">[Part6]</b></td>
864            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">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>, <a href="mailto:mnot@mnot.net">Nottingham, M., 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-10">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-10 (work in progress), July&nbsp;2010.
865            </td>
866         </tr>
867         <tr>
868            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
869            <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.
870            </td>
871         </tr>
872         <tr>
873            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
874            <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.
875            </td>
876         </tr>
877         <tr>
878            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
879            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
880            </td>
881         </tr>
882      </table>
883      <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References
884      </h2>
885      <table>
886         <tr>
887            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
888            <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.
889            </td>
890         </tr>
891         <tr>
892            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
893            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
894            </td>
895         </tr>
896      </table>
897      <div id="compatibility">
898         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
899         <div id="changes.from.rfc.2616">
900            <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>
901         </div>
902      </div>
903      <div id="collected.abnf">
904         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
905         <div id="rfc.figure.u.7"></div><pre class="inline"><a href="#header.authorization" class="smpl">Authorization</a> = "Authorization:" OWS Authorization-v
906<a href="#header.authorization" class="smpl">Authorization-v</a> = credentials
907
908<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
909
910<a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = "Proxy-Authenticate:" OWS Proxy-Authenticate-v
911<a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a> = *( "," OWS ) challenge *( OWS "," [ OWS
912 challenge ] )
913<a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> = "Proxy-Authorization:" OWS
914 Proxy-Authorization-v
915<a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a> = credentials
916
917<a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> = "WWW-Authenticate:" OWS WWW-Authenticate-v
918<a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a> = *( "," OWS ) challenge *( OWS "," [ OWS
919 challenge ] )
920
921<a href="#abnf.dependencies" class="smpl">challenge</a> = &lt;challenge, defined in [RFC2617], Section 1.2&gt;
922<a href="#abnf.dependencies" class="smpl">credentials</a> = &lt;credentials, defined in [RFC2617], Section 1.2&gt;
923</pre><div id="rfc.figure.u.8"></div>
924         <p>ABNF diagnostics:</p><pre class="inline">; Authorization defined but not used
925; Proxy-Authenticate defined but not used
926; Proxy-Authorization defined but not used
927; WWW-Authenticate defined but not used
928</pre></div>
929      <div id="change.log">
930         <h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
931         <div>
932            <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
933            </h2>
934            <p id="rfc.section.C.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>.
935            </p>
936         </div>
937         <div>
938            <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
939            </h2>
940            <p id="rfc.section.C.2.p.1">Closed issues: </p>
941            <ul>
942               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/35">http://tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
943               </li>
944            </ul>
945         </div>
946         <div>
947            <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p7-auth-01
948            </h2>
949            <p id="rfc.section.C.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
950            </p>
951            <ul>
952               <li>Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.</li>
953               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
954            </ul>
955         </div>
956         <div id="changes.since.02">
957            <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></h2>
958            <p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
959            </p>
960            <ul>
961               <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
962            </ul>
963         </div>
964         <div id="changes.since.03">
965            <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></h2>
966         </div>
967         <div id="changes.since.04">
968            <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></h2>
969            <p id="rfc.section.C.6.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
970            </p>
971            <ul>
972               <li>Use "/" instead of "|" for alternatives.</li>
973               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
974               <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
975            </ul>
976         </div>
977         <div id="changes.since.05">
978            <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></h2>
979            <p id="rfc.section.C.7.p.1">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
980            </p>
981            <ul>
982               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
983            </ul>
984         </div>
985         <div id="changes.since.06">
986            <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></h2>
987            <p id="rfc.section.C.8.p.1">None.</p>
988         </div>
989         <div id="changes.since.07">
990            <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></h2>
991            <p id="rfc.section.C.9.p.1">Closed issues: </p>
992            <ul>
993               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/198">http://tools.ietf.org/wg/httpbis/trac/ticket/198</a>&gt;: "move IANA registrations for optional status codes"
994               </li>
995            </ul>
996         </div>
997         <div id="changes.since.08">
998            <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></h2>
999            <p id="rfc.section.C.10.p.1">No significant changes.</p>
1000         </div>
1001         <div id="changes.since.09">
1002            <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></h2>
1003            <p id="rfc.section.C.11.p.1">Partly resolved issues: </p>
1004            <ul>
1005               <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/196">http://tools.ietf.org/wg/httpbis/trac/ticket/196</a>&gt;: "Term for the requested resource's URI"
1006               </li>
1007            </ul>
1008         </div>
1009      </div>
1010      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1011      <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> 
1012      </p>
1013      <div class="print2col">
1014         <ul class="ind">
1015            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1016                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>2.1</b></a>, <a href="#rfc.xref.status.401.1">4.1</a></li>
1017                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.2"><b>2.2</b></a>, <a href="#rfc.xref.status.407.1">4.1</a></li>
1018               </ul>
1019            </li>
1020            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1021                  <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>, <a href="#rfc.xref.header.authorization.2">4.2</a></li>
1022               </ul>
1023            </li>
1024            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1025                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1026                     <ul>
1027                        <li><tt>Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.1</b></a></li>
1028                        <li><tt>Authorization-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.1</b></a></li>
1029                        <li><tt>challenge</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.2.2</b></a></li>
1030                        <li><tt>credentials</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>1.2.2</b></a></li>
1031                        <li><tt>Proxy-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>3.2</b></a></li>
1032                        <li><tt>Proxy-Authenticate-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>3.2</b></a></li>
1033                        <li><tt>Proxy-Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.3</b></a></li>
1034                        <li><tt>Proxy-Authorization-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.3</b></a></li>
1035                        <li><tt>WWW-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.4</b></a></li>
1036                        <li><tt>WWW-Authenticate-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.4</b></a></li>
1037                     </ul>
1038                  </li>
1039               </ul>
1040            </li>
1041            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1042                  <li>Headers&nbsp;&nbsp;
1043                     <ul>
1044                        <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>, <a href="#rfc.xref.header.authorization.2">4.2</a></li>
1045                        <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>, <a href="#rfc.xref.header.proxy-authenticate.2">4.2</a></li>
1046                        <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>, <a href="#rfc.xref.header.proxy-authorization.2">4.2</a></li>
1047                        <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>, <a href="#rfc.xref.header.www-authenticate.2">4.2</a></li>
1048                     </ul>
1049                  </li>
1050               </ul>
1051            </li>
1052            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1053                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">3.2</a>, <a href="#rfc.xref.Part1.5">3.4</a>, <a href="#Part1"><b>7.1</b></a><ul>
1054                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
1055                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a></li>
1056                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">3.2</a>, <a href="#rfc.xref.Part1.5">3.4</a></li>
1057                     </ul>
1058                  </li>
1059                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a>, <a href="#Part6"><b>7.1</b></a><ul>
1060                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a></li>
1061                     </ul>
1062                  </li>
1063                  <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>, <a href="#rfc.xref.header.proxy-authenticate.2">4.2</a></li>
1064                  <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>, <a href="#rfc.xref.header.proxy-authorization.2">4.2</a></li>
1065               </ul>
1066            </li>
1067            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1068                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>7.1</b></a></li>
1069                  <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">C.1</a></li>
1070                  <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">1.2.2</a>, <a href="#rfc.xref.RFC2617.4">1.2.2</a>, <a href="#rfc.xref.RFC2617.5">2.1</a>, <a href="#rfc.xref.RFC2617.6">2.2</a>, <a href="#rfc.xref.RFC2617.7">3.1</a>, <a href="#rfc.xref.RFC2617.8">3.2</a>, <a href="#rfc.xref.RFC2617.9">3.3</a>, <a href="#rfc.xref.RFC2617.10">3.4</a>, <a href="#RFC2617"><b>7.1</b></a><ul>
1071                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2617.3">1.2.2</a>, <a href="#rfc.xref.RFC2617.4">1.2.2</a></li>
1072                     </ul>
1073                  </li>
1074                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">4.2</a>, <a href="#RFC3864"><b>7.2</b></a></li>
1075                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b>7.1</b></a><ul>
1076                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
1077                     </ul>
1078                  </li>
1079               </ul>
1080            </li>
1081            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1082                  <li>Status Codes&nbsp;&nbsp;
1083                     <ul>
1084                        <li>401 Unauthorized&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>2.1</b></a>, <a href="#rfc.xref.status.401.1">4.1</a></li>
1085                        <li>407 Proxy Authentication Required&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>2.2</b></a>, <a href="#rfc.xref.status.407.1">4.1</a></li>
1086                     </ul>
1087                  </li>
1088               </ul>
1089            </li>
1090            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
1091                  <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>, <a href="#rfc.xref.header.www-authenticate.2">4.2</a></li>
1092               </ul>
1093            </li>
1094         </ul>
1095      </div>
1096      <div class="avoidbreak">
1097         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1098         <p><b>Roy T. Fielding</b>
1099            (editor)
1100            <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>
1101         <p><b>Jim Gettys</b><br>Alcatel-Lucent Bell Labs<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>Email: <a href="mailto:jg@freedesktop.org">jg@freedesktop.org</a><br>URI: <a href="http://gettys.wordpress.com/">http://gettys.wordpress.com/</a></p>
1102         <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>
1103         <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>
1104         <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>
1105         <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>
1106         <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>
1107         <p><b>Yves Lafon</b>
1108            (editor)
1109            <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>
1110         <p><b>Julian F. Reschke</b>
1111            (editor)
1112            <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>
1113      </div>
1114   </body>
1115</html>
Note: See TracBrowser for help on using the repository browser.