source: draft-ietf-httpbis/latest/p7-auth.html @ 1586

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

trim the authors list to just the current editors

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 92.4 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="http://www.w3.org/2006/03/hcard http://dublincore.org/documents/2008/08/04/dc-html/">
5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 7: Authentication</title><script>
7var buttonsAdded = false;
8
9function init() {
10  var fb = document.createElement("div");
11  fb.className = "feedback noprint";
12  fb.setAttribute("onclick", "feedback();");
13  fb.appendChild(document.createTextNode("feedback"));
14
15  var bodyl = document.getElementsByTagName("body");
16  bodyl.item(0).appendChild(fb);
17}
18
19function feedback() {
20  toggleButtonsToElementsByName("h1");
21  toggleButtonsToElementsByName("h2");
22  toggleButtonsToElementsByName("h3");
23  toggleButtonsToElementsByName("h4");
24 
25  buttonsAdded = !buttonsAdded;
26}
27
28function toggleButtonsToElementsByName(name) {
29  var list = document.getElementsByTagName(name);
30  for (var i = 0; i < list.length; i++) {
31    toggleButton(list.item(i));
32  }
33}
34
35function toggleButton(node) {
36  if (! buttonsAdded) {
37 
38    // docname
39    var template = "mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&body=<{ref}>:";
40
41    var id = node.getAttribute("id");
42    // better id available?
43    var titlelinks = node.getElementsByTagName("a");
44    for (var i = 0; i < titlelinks.length; i++) {
45      var tl = titlelinks.item(i);
46      if (tl.getAttribute("id")) {
47        id = tl.getAttribute("id");
48      }
49    }
50
51    // ref
52    var ref = window.location.toString();
53    var hash = ref.indexOf("#");
54    if (hash != -1) {
55      ref = ref.substring(0, hash);
56    }
57    if (id != "") {
58      ref += "#" + id;
59    }
60   
61    // docname
62    var docname = "draft-ietf-httpbis-p7-auth-latest";
63
64    // section
65    var section = node.textContent;
66    section = section.replace("\u00a0", " ");
67   
68    // build URI from template
69    var uri = template.replace("{docname}", encodeURIComponent(docname));
70    uri = uri.replace("{section}", encodeURIComponent(section));
71    uri = uri.replace("{ref}", encodeURIComponent(ref));
72 
73    var button = document.createElement("a");
74    button.className = "fbbutton noprint";
75    button.setAttribute("href", uri);
76    button.appendChild(document.createTextNode("send feedback"));
77    node.appendChild(button);
78  }
79  else {
80    var buttons = node.getElementsByTagName("a");
81    for (var i = 0; i < buttons.length; i++) {
82      var b = buttons.item(i);
83      if (b.className == "fbbutton noprint") {
84        node.removeChild(b);
85      }
86    }
87  }
88}</script><style type="text/css" title="Xml2Rfc (sans serif)">
89a {
90  text-decoration: none;
91}
92a.smpl {
93  color: black;
94}
95a:hover {
96  text-decoration: underline;
97}
98a:active {
99  text-decoration: underline;
100}
101address {
102  margin-top: 1em;
103  margin-left: 2em;
104  font-style: normal;
105}
106body {
107  color: black;
108  font-family: verdana, helvetica, arial, sans-serif;
109  font-size: 10pt;
110}
111cite {
112  font-style: normal;
113}
114div.note {
115  margin-left: 2em;
116}
117dd {
118  margin-right: 2em;
119}
120dl {
121  margin-left: 2em;
122}
123
124ul.empty {
125  list-style-type: none;
126}
127ul.empty li {
128  margin-top: .5em;
129}
130dl p {
131  margin-left: 0em;
132}
133dt {
134  margin-top: .5em;
135}
136h1 {
137  font-size: 14pt;
138  line-height: 21pt;
139  page-break-after: avoid;
140}
141h1.np {
142  page-break-before: always;
143}
144h1 a {
145  color: #333333;
146}
147h2 {
148  font-size: 12pt;
149  line-height: 15pt;
150  page-break-after: avoid;
151}
152h3, h4, h5, h6 {
153  font-size: 10pt;
154  page-break-after: avoid;
155}
156h2 a, h3 a, h4 a, h5 a, h6 a {
157  color: black;
158}
159img {
160  margin-left: 3em;
161}
162li {
163  margin-left: 2em;
164  margin-right: 2em;
165}
166ol {
167  margin-left: 2em;
168  margin-right: 2em;
169}
170ol.la {
171  list-style-type: lower-alpha;
172}
173ol.ua {
174  list-style-type: upper-alpha;
175}
176ol p {
177  margin-left: 0em;
178}
179p {
180  margin-left: 2em;
181  margin-right: 2em;
182}
183pre {
184  margin-left: 3em;
185  background-color: lightyellow;
186  padding: .25em;
187}
188pre.text2 {
189  border-style: dotted;
190  border-width: 1px;
191  background-color: #f0f0f0;
192  width: 69em;
193}
194pre.inline {
195  background-color: white;
196  padding: 0em;
197}
198pre.text {
199  border-style: dotted;
200  border-width: 1px;
201  background-color: #f8f8f8;
202  width: 69em;
203}
204pre.drawing {
205  border-style: solid;
206  border-width: 1px;
207  background-color: #f8f8f8;
208  padding: 2em;
209}
210table {
211  margin-left: 2em;
212}
213table.tt {
214  vertical-align: top;
215}
216table.full {
217  border-style: outset;
218  border-width: 1px;
219}
220table.headers {
221  border-style: outset;
222  border-width: 1px;
223}
224table.tt td {
225  vertical-align: top;
226}
227table.full td {
228  border-style: inset;
229  border-width: 1px;
230}
231table.tt th {
232  vertical-align: top;
233}
234table.full th {
235  border-style: inset;
236  border-width: 1px;
237}
238table.headers th {
239  border-style: none none inset none;
240  border-width: 1px;
241}
242table.left {
243  margin-right: auto;
244}
245table.right {
246  margin-left: auto;
247}
248table.center {
249  margin-left: auto;
250  margin-right: auto;
251}
252caption {
253  caption-side: bottom;
254  font-weight: bold;
255  font-size: 9pt;
256  margin-top: .5em;
257}
258
259table.header {
260  border-spacing: 1px;
261  width: 95%;
262  font-size: 10pt;
263  color: white;
264}
265td.top {
266  vertical-align: top;
267}
268td.topnowrap {
269  vertical-align: top;
270  white-space: nowrap; 
271}
272table.header td {
273  background-color: gray;
274  width: 50%;
275}
276table.header a {
277  color: white;
278}
279td.reference {
280  vertical-align: top;
281  white-space: nowrap;
282  padding-right: 1em;
283}
284thead {
285  display:table-header-group;
286}
287ul.toc, ul.toc ul {
288  list-style: none;
289  margin-left: 1.5em;
290  margin-right: 0em;
291  padding-left: 0em;
292}
293ul.toc li {
294  line-height: 150%;
295  font-weight: bold;
296  font-size: 10pt;
297  margin-left: 0em;
298  margin-right: 0em;
299}
300ul.toc li li {
301  line-height: normal;
302  font-weight: normal;
303  font-size: 9pt;
304  margin-left: 0em;
305  margin-right: 0em;
306}
307li.excluded {
308  font-size: 0pt;
309}
310ul p {
311  margin-left: 0em;
312}
313ul.ind, ul.ind ul {
314  list-style: none;
315  margin-left: 1.5em;
316  margin-right: 0em;
317  padding-left: 0em;
318  page-break-before: avoid;
319}
320ul.ind li {
321  font-weight: bold;
322  line-height: 200%;
323  margin-left: 0em;
324  margin-right: 0em;
325}
326ul.ind li li {
327  font-weight: normal;
328  line-height: 150%;
329  margin-left: 0em;
330  margin-right: 0em;
331}
332.avoidbreak {
333  page-break-inside: avoid;
334}
335.bcp14 {
336  font-style: normal;
337  text-transform: lowercase;
338  font-variant: small-caps;
339}
340.comment {
341  background-color: yellow;
342}
343.center {
344  text-align: center;
345}
346.error {
347  color: red;
348  font-style: italic;
349  font-weight: bold;
350}
351.figure {
352  font-weight: bold;
353  text-align: center;
354  font-size: 9pt;
355}
356.filename {
357  color: #333333;
358  font-weight: bold;
359  font-size: 12pt;
360  line-height: 21pt;
361  text-align: center;
362}
363.fn {
364  font-weight: bold;
365}
366.hidden {
367  display: none;
368}
369.left {
370  text-align: left;
371}
372.right {
373  text-align: right;
374}
375.title {
376  color: #990000;
377  font-size: 18pt;
378  line-height: 18pt;
379  font-weight: bold;
380  text-align: center;
381  margin-top: 36pt;
382}
383.vcardline {
384  display: block;
385}
386.warning {
387  font-size: 14pt;
388  background-color: yellow;
389}
390.feedback {
391  position: fixed;
392  bottom: 1%;
393  right: 1%;
394  padding: 3px 5px;
395  color: white;
396  border-radius: 5px;
397  background: #a00000;
398  border: 1px solid silver;
399}
400.fbbutton {
401  margin-left: 1em;
402  color: #303030;
403  font-size: small;
404  font-weight: normal;
405  background: #d0d000;
406  padding: 1px 4px;
407  border: 1px solid silver;
408  border-radius: 5px;
409}
410
411@media print {
412  .noprint {
413    display: none;
414  }
415 
416  a {
417    color: black;
418    text-decoration: none;
419  }
420
421  table.header {
422    width: 90%;
423  }
424
425  td.header {
426    width: 50%;
427    color: black;
428    background-color: white;
429    vertical-align: top;
430    font-size: 12pt;
431  }
432
433  ul.toc a::after {
434    content: leader('.') target-counter(attr(href), page);
435  }
436 
437  ul.ind li li a {
438    content: target-counter(attr(href), page);
439  }
440 
441  .print2col {
442    column-count: 2;
443    -moz-column-count: 2;
444    column-fill: auto;
445  }
446}
447
448@page {
449  @top-left {
450       content: "Internet-Draft"; 
451  } 
452  @top-right {
453       content: "March 2012"; 
454  } 
455  @top-center {
456       content: "HTTP/1.1, Part 7"; 
457  } 
458  @bottom-left {
459       content: "Fielding, et al."; 
460  } 
461  @bottom-center {
462       content: "Expires September 12, 2012"; 
463  } 
464  @bottom-right {
465       content: "[Page " counter(page) "]"; 
466  } 
467}
468
469@page:first { 
470    @top-left {
471      content: normal;
472    }
473    @top-right {
474      content: normal;
475    }
476    @top-center {
477      content: normal;
478    }
479}
480</style><link rel="Contents" href="#rfc.toc">
481      <link rel="Author" href="#rfc.authors">
482      <link rel="Copyright" href="#rfc.copyrightnotice">
483      <link rel="Index" href="#rfc.index">
484      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
485      <link rel="Chapter" title="2 Access Authentication Framework" href="#rfc.section.2">
486      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
487      <link rel="Chapter" title="4 Header Field Definitions" href="#rfc.section.4">
488      <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5">
489      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
490      <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
491      <link rel="Chapter" href="#rfc.section.8" title="8 References">
492      <link rel="Appendix" title="A Changes from RFCs 2616 and 2617" href="#rfc.section.A">
493      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
494      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
495      <link href="p6-cache.html" rel="prev">
496      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.570, 2012-02-13 19:17:35, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
497      <link rel="schema.dct" href="http://purl.org/dc/terms/">
498      <meta name="dct.creator" content="Fielding, R.">
499      <meta name="dct.creator" content="Lafon, Y.">
500      <meta name="dct.creator" content="Reschke, J. F.">
501      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
502      <meta name="dct.issued" scheme="ISO8601" content="2012-03-11">
503      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
504      <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 the HTTP Authentication framework.">
505      <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 the HTTP Authentication framework.">
506   </head>
507   <body onload="init();">
508      <table class="header">
509         <tbody>
510            <tr>
511               <td class="left">HTTPbis Working Group</td>
512               <td class="right">R. Fielding, Editor</td>
513            </tr>
514            <tr>
515               <td class="left">Internet-Draft</td>
516               <td class="right">Adobe</td>
517            </tr>
518            <tr>
519               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
520               </td>
521               <td class="right">Y. Lafon, Editor</td>
522            </tr>
523            <tr>
524               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)
525               </td>
526               <td class="right">W3C</td>
527            </tr>
528            <tr>
529               <td class="left">Intended status: Standards Track</td>
530               <td class="right">J. Reschke, Editor</td>
531            </tr>
532            <tr>
533               <td class="left">Expires: September 12, 2012</td>
534               <td class="right">greenbytes</td>
535            </tr>
536            <tr>
537               <td class="left"></td>
538               <td class="right">March 11, 2012</td>
539            </tr>
540         </tbody>
541      </table>
542      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-latest</span></p>
543      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
544      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
545         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
546         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
547      </p> 
548      <p>Part 7 defines the HTTP Authentication framework.</p> 
549      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
550      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org), which is archived
551         at &lt;<a href="http://lists.w3.org/Archives/Public/ietf-http-wg/">http://lists.w3.org/Archives/Public/ietf-http-wg/</a>&gt;.
552      </p> 
553      <p>The current issues list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/3">http://tools.ietf.org/wg/httpbis/trac/report/3</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://tools.ietf.org/wg/httpbis/">http://tools.ietf.org/wg/httpbis/</a>&gt;.
554      </p> 
555      <p>The changes in this draft are summarized in <a href="#changes.since.18" title="Since draft-ietf-httpbis-p7-auth-18">Appendix&nbsp;C.20</a>.
556      </p> 
557      <h1><a id="rfc.status" href="#rfc.status">Status of This Memo</a></h1>
558      <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
559      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
560         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>.
561      </p>
562      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
563         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
564         in progress”.
565      </p>
566      <p>This Internet-Draft will expire on September 12, 2012.</p>
567      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
568      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
569      <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
570         and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
571         text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
572         BSD License.
573      </p>
574      <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
575         10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
576         allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
577         controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
578         works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
579         it into languages other than English.
580      </p>
581      <hr class="noprint">
582      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
583      <ul class="toc">
584         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
585               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></li>
586               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
587                     <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
588                  </ul>
589               </li>
590            </ul>
591         </li>
592         <li>2.&nbsp;&nbsp;&nbsp;<a href="#access.authentication.framework">Access Authentication Framework</a><ul>
593               <li>2.1&nbsp;&nbsp;&nbsp;<a href="#challenge.and.response">Challenge and Response</a></li>
594               <li>2.2&nbsp;&nbsp;&nbsp;<a href="#protection.space">Protection Space (Realm)</a></li>
595               <li>2.3&nbsp;&nbsp;&nbsp;<a href="#authentication.scheme.registry">Authentication Scheme Registry</a><ul>
596                     <li>2.3.1&nbsp;&nbsp;&nbsp;<a href="#considerations.for.new.authentication.schemes">Considerations for New Authentication Schemes</a></li>
597                  </ul>
598               </li>
599            </ul>
600         </li>
601         <li>3.&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
602               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
603               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
604            </ul>
605         </li>
606         <li>4.&nbsp;&nbsp;&nbsp;<a href="#header.field.definitions">Header Field Definitions</a><ul>
607               <li>4.1&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
608               <li>4.2&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
609               <li>4.3&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
610               <li>4.4&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
611            </ul>
612         </li>
613         <li>5.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
614               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#authentication.scheme.registration">Authenticaton Scheme Registry</a></li>
615               <li>5.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
616               <li>5.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
617            </ul>
618         </li>
619         <li>6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
620               <li>6.1&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
621            </ul>
622         </li>
623         <li>7.&nbsp;&nbsp;&nbsp;<a href="#acks">Acknowledgments</a></li>
624         <li>8.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
625               <li>8.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
626               <li>8.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
627            </ul>
628         </li>
629         <li><a href="#rfc.authors">Authors' Addresses</a></li>
630         <li>A.&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFCs 2616 and 2617</a></li>
631         <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
632         <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
633               <li>C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC 2616</a></li>
634               <li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
635               <li>C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p7-auth-01</a></li>
636               <li>C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></li>
637               <li>C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></li>
638               <li>C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></li>
639               <li>C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></li>
640               <li>C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></li>
641               <li>C.9&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></li>
642               <li>C.10&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></li>
643               <li>C.11&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></li>
644               <li>C.12&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p7-auth-10</a></li>
645               <li>C.13&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p7-auth-11</a></li>
646               <li>C.14&nbsp;&nbsp;&nbsp;<a href="#changes.since.12">Since draft-ietf-httpbis-p7-auth-12</a></li>
647               <li>C.15&nbsp;&nbsp;&nbsp;<a href="#changes.since.13">Since draft-ietf-httpbis-p7-auth-13</a></li>
648               <li>C.16&nbsp;&nbsp;&nbsp;<a href="#changes.since.14">Since draft-ietf-httpbis-p7-auth-14</a></li>
649               <li>C.17&nbsp;&nbsp;&nbsp;<a href="#changes.since.15">Since draft-ietf-httpbis-p7-auth-15</a></li>
650               <li>C.18&nbsp;&nbsp;&nbsp;<a href="#changes.since.16">Since draft-ietf-httpbis-p7-auth-16</a></li>
651               <li>C.19&nbsp;&nbsp;&nbsp;<a href="#changes.since.17">Since draft-ietf-httpbis-p7-auth-17</a></li>
652               <li>C.20&nbsp;&nbsp;&nbsp;<a href="#changes.since.18">Since draft-ietf-httpbis-p7-auth-18</a></li>
653            </ul>
654         </li>
655         <li><a href="#rfc.index">Index</a></li>
656      </ul>
657      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
658      <p id="rfc.section.1.p.1">This document defines HTTP/1.1 access control and authentication. It includes the relevant parts of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> with only minor changes, plus the general framework for HTTP authentication, as previously defined in "HTTP Authentication:
659         Basic and Digest Access Authentication" (<a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>).
660      </p>
661      <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
662         provide authentication information. The "basic" and "digest" authentication schemes continue to be specified in <cite title="HTTP Authentication: Basic and Digest Access Authentication" id="rfc.xref.RFC2617.2">RFC 2617</cite>.
663      </p>
664      <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a id="intro.conformance.and.error.handling" href="#intro.conformance.and.error.handling">Conformance and Error Handling</a></h2>
665      <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"
666         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>.
667      </p>
668      <p id="rfc.section.1.1.p.2">This document defines conformance criteria for several roles in HTTP communication, including Senders, Recipients, Clients,
669         Servers, User-Agents, Origin Servers, Intermediaries, Proxies and Gateways. See <a href="p1-messaging.html#architecture" title="Architecture">Section 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> for definitions of these terms.
670      </p>
671      <p id="rfc.section.1.1.p.3">An implementation is considered conformant if it complies with all of the requirements associated with its role(s). Note that
672         SHOULD-level requirements are relevant here, unless one of the documented exceptions is applicable.
673      </p>
674      <p id="rfc.section.1.1.p.4">This document also uses ABNF to define valid protocol elements (<a href="#notation" title="Syntax Notation">Section&nbsp;1.2</a>). In addition to the prose requirements placed upon them, Senders <em class="bcp14">MUST NOT</em> generate protocol elements that are invalid.
675      </p>
676      <p id="rfc.section.1.1.p.5">Unless noted otherwise, Recipients <em class="bcp14">MAY</em> take steps to recover a usable protocol element from an invalid construct. However, HTTP does not define specific error handling
677         mechanisms, except in cases where it has direct impact on security. This is because different uses of the protocol require
678         different error handling strategies; for example, a Web browser may wish to transparently recover from a response where the
679         Location header field doesn't parse according to the ABNF, whereby in a systems control protocol using HTTP, this type of
680         error recovery could lead to dangerous consequences.
681      </p>
682      <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a id="notation" href="#notation">Syntax Notation</a></h2>
683      <p id="rfc.section.1.2.p.1">This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with the list rule extension defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.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>. <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF with the list rule expanded.
684      </p>
685      <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="http://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
686         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), and VCHAR (any visible US-ASCII
687         character).
688      </p>
689      <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a id="core.rules" href="#core.rules">Core Rules</a></h3>
690      <p id="rfc.section.1.2.1.p.1">The core rules below are 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>:
691      </p>
692      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">BWS</a>           = &lt;BWS, defined in <a href="#Part1" id="rfc.xref.Part1.4"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
693  <a href="#core.rules" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#whitespace" title="Whitespace">Section 3.2.1</a>&gt;
694  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
695  <a href="#core.rules" class="smpl">token</a>         = &lt;token, defined in <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#field.components" title="Field value components">Section 3.2.4</a>&gt;
696</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="access.authentication.framework" href="#access.authentication.framework">Access Authentication Framework</a></h1>
697      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="challenge.and.response" href="#challenge.and.response">Challenge and Response</a></h2>
698      <p id="rfc.section.2.1.p.1">HTTP provides a simple challenge-response authentication mechanism that can be used by a server to challenge a client request
699         and by a client to provide authentication information. It uses an extensible, case-insensitive token to identify the authentication
700         scheme, followed by additional information necessary for achieving authentication via that scheme. The latter can either be
701         a comma-separated list of parameters or a single sequence of characters capable of holding base64-encoded information.
702      </p>
703      <p id="rfc.section.2.1.p.2">Parameters are name-value pairs where the name is matched case-insensitively, and each parameter name <em class="bcp14">MUST</em> only occur once per challenge.
704      </p>
705      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.a.1"></span><span id="rfc.iref.a.2"></span><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span><span id="rfc.iref.b.1"></span><span id="rfc.iref.g.3"></span>  auth-scheme    = <a href="#core.rules" class="smpl">token</a>
706 
707  auth-param     = <a href="#core.rules" class="smpl">token</a> <a href="#core.rules" class="smpl">BWS</a> "=" <a href="#core.rules" class="smpl">BWS</a> ( <a href="#core.rules" class="smpl">token</a> / <a href="#core.rules" class="smpl">quoted-string</a> )
708
709  b64token       = 1*( <a href="#notation" class="smpl">ALPHA</a> / <a href="#notation" class="smpl">DIGIT</a> /
710                       "-" / "." / "_" / "~" / "+" / "/" ) *"="
711</pre><p id="rfc.section.2.1.p.4">The "b64token" syntax allows the 66 unreserved URI characters (<a href="#RFC3986" id="rfc.xref.RFC3986.1"><cite title="Uniform Resource Identifier (URI): Generic Syntax">[RFC3986]</cite></a>), plus a few others, so that it can hold a base64, base64url (URL and filename safe alphabet), base32, or base16 (hex) encoding,
712         with or without padding, but excluding whitespace (<a href="#RFC4648" id="rfc.xref.RFC4648.1"><cite title="The Base16, Base32, and Base64 Data Encodings">[RFC4648]</cite></a>).
713      </p>
714      <p id="rfc.section.2.1.p.5">The 401 (Unauthorized) response message is used by an origin server to challenge the authorization of a user agent. This response <em class="bcp14">MUST</em> include a WWW-Authenticate header field containing at least one challenge applicable to the requested resource.
715      </p>
716      <p id="rfc.section.2.1.p.6">The 407 (Proxy Authentication Required) response message is used by a proxy to challenge the authorization of a client and <em class="bcp14">MUST</em> include a Proxy-Authenticate header field containing at least one challenge applicable to the proxy for the requested resource.
717      </p>
718      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.c.1"></span><span id="rfc.iref.g.4"></span>  <a href="#challenge.and.response" class="smpl">challenge</a>   = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#notation" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">b64token</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ]
719</pre><div class="note" id="rfc.section.2.1.p.8"> 
720         <p> <b>Note:</b> User agents will need to take special care in parsing the WWW-Authenticate and Proxy-Authenticate header field values because
721            they can contain more than one challenge, or if more than one of each is provided, since the contents of a challenge can itself
722            contain a comma-separated list of authentication parameters.
723         </p> 
724      </div>
725      <div class="note" id="rfc.section.2.1.p.9"> 
726         <p> <b>Note:</b> Many browsers fail to parse challenges containing unknown schemes. A workaround for this problem is to list well-supported
727            schemes (such as "basic") first.
728         </p> 
729      </div>
730      <p id="rfc.section.2.1.p.10">A user agent that wishes to authenticate itself with an origin server — usually, but not necessarily, after receiving a 401
731         (Unauthorized) — <em class="bcp14">MAY</em> do so by including an Authorization header field with the request.
732      </p>
733      <p id="rfc.section.2.1.p.11">A client that wishes to authenticate itself with a proxy — usually, but not necessarily, after receiving a 407 (Proxy Authentication
734         Required) — <em class="bcp14">MAY</em> do so by including a Proxy-Authorization header field with the request.
735      </p>
736      <p id="rfc.section.2.1.p.12">Both the Authorization field value and the Proxy-Authorization field value consist of credentials containing the authentication
737         information of the client for the realm of the resource being requested. The user agent <em class="bcp14">MUST</em> choose to use one of the challenges with the strongest auth-scheme it understands and request credentials from the user based
738         upon that challenge.
739      </p>
740      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.c.2"></span><span id="rfc.iref.g.5"></span>  <a href="#challenge.and.response" class="smpl">credentials</a> = <a href="#challenge.and.response" class="smpl">auth-scheme</a> [ 1*<a href="#notation" class="smpl">SP</a> ( <a href="#challenge.and.response" class="smpl">b64token</a> / #<a href="#challenge.and.response" class="smpl">auth-param</a> ) ]
741</pre><p id="rfc.section.2.1.p.14">If the origin server does not wish to accept the credentials sent with a request, it <em class="bcp14">SHOULD</em> return a 401 (Unauthorized) response. The response <em class="bcp14">MUST</em> include a WWW-Authenticate header field containing at least one (possibly new) challenge applicable to the requested resource.
742      </p>
743      <p id="rfc.section.2.1.p.15">If a proxy does not accept the credentials sent with a request, it <em class="bcp14">SHOULD</em> return a 407 (Proxy Authentication Required). The response <em class="bcp14">MUST</em> include a Proxy-Authenticate header field containing a (possibly new) challenge applicable to the proxy for the requested
744         resource.
745      </p>
746      <p id="rfc.section.2.1.p.16">The HTTP protocol does not restrict applications to this simple challenge-response mechanism for access authentication. Additional
747         mechanisms <em class="bcp14">MAY</em> be used, such as encryption at the transport level or via message encapsulation, and with additional header fields specifying
748         authentication information. However, such additional mechanisms are not defined by this specification.
749      </p>
750      <p id="rfc.section.2.1.p.17">Proxies <em class="bcp14">MUST</em> forward the WWW-Authenticate and Authorization headers unmodified and follow the rules found in <a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;4.1</a>.
751      </p>
752      <div id="rfc.iref.p.1"></div>
753      <div id="rfc.iref.r.1"></div>
754      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="protection.space" href="#protection.space">Protection Space (Realm)</a></h2>
755      <p id="rfc.section.2.2.p.1">The authentication parameter realm is reserved for use by authentication schemes that wish to indicate the scope of protection.</p>
756      <p id="rfc.section.2.2.p.2">A <dfn>protection space</dfn> is defined by the canonical root URI (the scheme and authority components of the effective request URI; see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.8"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) of the server being accessed, in combination with the realm value if present. These realms allow the protected resources
757         on a server to be partitioned into a set of protection spaces, each with its own authentication scheme and/or authorization
758         database. The realm value is a string, generally assigned by the origin server, which can have additional semantics specific
759         to the authentication scheme. Note that there can be multiple challenges with the same auth-scheme but different realms.
760      </p>
761      <p id="rfc.section.2.2.p.3">The protection space determines the domain over which credentials can be automatically applied. If a prior request has been
762         authorized, the same credentials <em class="bcp14">MAY</em> be reused for all other requests within that protection space for a period of time determined by the authentication scheme,
763         parameters, and/or user preference. Unless otherwise defined by the authentication scheme, a single protection space cannot
764         extend outside the scope of its server.
765      </p>
766      <p id="rfc.section.2.2.p.4">For historical reasons, senders <em class="bcp14">MUST</em> only use the quoted-string syntax. Recipients might have to support both token and quoted-string syntax for maximum interoperability
767         with existing clients that have been accepting both notations for a long time.
768      </p>
769      <h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a>&nbsp;<a id="authentication.scheme.registry" href="#authentication.scheme.registry">Authentication Scheme Registry</a></h2>
770      <p id="rfc.section.2.3.p.1">The HTTP Authentication Scheme Registry defines the name space for the authentication schemes in challenges and credentials.</p>
771      <p id="rfc.section.2.3.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
772      </p>
773      <ul>
774         <li>Authentication Scheme Name</li>
775         <li>Pointer to specification text</li>
776         <li>Notes (optional)</li>
777      </ul>
778      <p id="rfc.section.2.3.p.3">Values to be added to this name space require IETF Review (see <a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
779      </p>
780      <p id="rfc.section.2.3.p.4">The registry itself is maintained at &lt;<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>&gt;.
781      </p>
782      <h3 id="rfc.section.2.3.1"><a href="#rfc.section.2.3.1">2.3.1</a>&nbsp;<a id="considerations.for.new.authentication.schemes" href="#considerations.for.new.authentication.schemes">Considerations for New Authentication Schemes</a></h3>
783      <p id="rfc.section.2.3.1.p.1">There are certain aspects of the HTTP Authentication Framework that put constraints on how new authentication schemes can
784         work:
785      </p>
786      <p id="rfc.section.2.3.1.p.2"> </p>
787      <ul>
788         <li>
789            <p>HTTP authentication is presumed to be stateless: all of the information necessary to authenticate a request <em class="bcp14">MUST</em> be provided in the request, rather than be dependent on the server remembering prior requests. Authentication based on, or
790               bound to, the underlying connection is outside the scope of this specification and inherently flawed unless steps are taken
791               to ensure that the connection cannot be used by any party other than the authenticated user (see <a href="p1-messaging.html#intermediaries" title="Intermediaries">Section 2.3</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
792            </p>
793         </li>
794         <li>
795            <p>The authentication parameter "realm" is reserved for defining Protection Spaces as defined in <a href="#protection.space" title="Protection Space (Realm)">Section&nbsp;2.2</a>. New schemes <em class="bcp14">MUST NOT</em> use it in a way incompatible with that definition.
796            </p>
797         </li>
798         <li>
799            <p>The "b64token" notation was introduced for compatibility with existing authentication schemes and can only be used once per
800               challenge/credentials. New schemes thus ought to use the "auth-param" syntax instead, because otherwise future extensions
801               will be impossible.
802            </p>
803         </li>
804         <li>
805            <p>The parsing of challenges and credentials is defined by this specification, and cannot be modified by new authentication schemes.
806               When the auth-param syntax is used, all parameters ought to support both token and quoted-string syntax, and syntactical constraints
807               ought to be defined on the field value after parsing (i.e., quoted-string processing). This is necessary so that recipients
808               can use a generic parser that applies to all authentication schemes.
809            </p>
810            <p> <b>Note:</b> the fact that the value syntax for the "realm" parameter is restricted to quoted-string was a bad design choice not to be
811               repeated for new parameters.
812            </p>
813         </li>
814         <li>
815            <p>Definitions of new schemes ought to define the treatment of unknown extension parameters. In general, a "must-ignore" rule
816               is preferable over "must-understand", because otherwise it will be hard to introduce new parameters in the presence of legacy
817               recipients. Furthermore, it's good to describe the policy for defining new parameters (such as "update the specification",
818               or "use this registry").
819            </p>
820         </li>
821         <li>
822            <p>Authentication schemes need to document whether they are usable in origin-server authentication (i.e., using WWW-Authenticate),
823               and/or proxy authentication (i.e., using Proxy-Authenticate).
824            </p>
825         </li>
826         <li>
827            <p>The credentials carried in an Authorization header field are specific to the User Agent, and therefore have the same effect
828               on HTTP caches as the "private" Cache-Control response directive, within the scope of the request they appear in.
829            </p>
830            <p>Therefore, new authentication schemes which choose not to carry credentials in the Authorization header (e.g., using a newly
831               defined header) will need to explicitly disallow caching, by mandating the use of either Cache-Control request directives
832               (e.g., "no-store") or response directives (e.g., "private").
833            </p>
834         </li>
835      </ul>
836      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1>
837      <div id="rfc.iref.12"></div>
838      <div id="rfc.iref.s.1"></div>
839      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h2>
840      <p id="rfc.section.3.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;4.4</a>) containing a challenge applicable to the target 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.2" title="Authorization">Section&nbsp;4.1</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
841         refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
842         already attempted authentication at least once, then the user <em class="bcp14">SHOULD</em> be presented the representation that was given in the response, since that representation might include relevant diagnostic
843         information.
844      </p>
845      <div id="rfc.iref.13"></div>
846      <div id="rfc.iref.s.2"></div>
847      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h2>
848      <p id="rfc.section.3.2.p.1">This code is similar to 401 (Unauthorized), but indicates that the client ought to first authenticate itself with the proxy.
849         The 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;4.2</a>) containing a challenge applicable to the proxy for the target 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;4.3</a>).
850      </p>
851      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="header.field.definitions" href="#header.field.definitions">Header Field Definitions</a></h1>
852      <p id="rfc.section.4.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
853      <div id="rfc.iref.a.3"></div>
854      <div id="rfc.iref.h.1"></div>
855      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="header.authorization" href="#header.authorization">Authorization</a></h2>
856      <p id="rfc.section.4.1.p.1">The "Authorization" header field allows a user agent to authenticate itself with a server — usually, but not necessarily,
857         after receiving a 401 (Unauthorized) response. Its value consists of credentials containing information of the user agent
858         for the realm of the resource being requested.
859      </p>
860      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#header.authorization" class="smpl">Authorization</a> = <a href="#challenge.and.response" class="smpl">credentials</a>
861</pre><p id="rfc.section.4.1.p.3">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,
862         such as credentials that vary according to a challenge value or using synchronized clocks).
863      </p>
864      <p id="rfc.section.4.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:
865      </p>
866      <p id="rfc.section.4.1.p.5"> </p>
867      <ol>
868         <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 header fields from the new request to allow the origin server to authenticate
869            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.
870         </li>
871         <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 header fields from the new request to allow the origin server to authenticate
872            the new request.
873         </li>
874         <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
875         </li>
876      </ol>
877      <div id="rfc.iref.p.2"></div>
878      <div id="rfc.iref.h.2"></div>
879      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="header.proxy-authenticate" href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
880      <p id="rfc.section.4.2.p.1">The "Proxy-Authenticate" header field consists of a challenge that indicates the authentication scheme and parameters applicable
881         to the proxy for this effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.10"><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.
882      </p>
883      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.7"></span>  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = 1#<a href="#challenge.and.response" class="smpl">challenge</a>
884</pre><p id="rfc.section.4.2.p.3">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
885         them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
886         header field.
887      </p>
888      <p id="rfc.section.4.2.p.4">Note that the parsing considerations for WWW-Authenticate apply to this header field as well; see <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section&nbsp;4.4</a> for details.
889      </p>
890      <div id="rfc.iref.p.3"></div>
891      <div id="rfc.iref.h.3"></div>
892      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="header.proxy-authorization" href="#header.proxy-authorization">Proxy-Authorization</a></h2>
893      <p id="rfc.section.4.3.p.1">The "Proxy-Authorization" header field allows the client to identify itself (or its user) to a proxy which requires authentication.
894         Its value consists of credentials containing the authentication information of the user agent for the proxy and/or realm of
895         the resource being requested.
896      </p>
897      <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> = <a href="#challenge.and.response" class="smpl">credentials</a>
898</pre><p id="rfc.section.4.3.p.3">Unlike Authorization, the Proxy-Authorization header field applies only to the next outbound proxy that demanded authentication
899         using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
900         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
901         authenticate a given request.
902      </p>
903      <div id="rfc.iref.w.1"></div>
904      <div id="rfc.iref.h.4"></div>
905      <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="header.www-authenticate" href="#header.www-authenticate">WWW-Authenticate</a></h2>
906      <p id="rfc.section.4.4.p.1">The "WWW-Authenticate" header field consists of at least one challenge that indicates the authentication scheme(s) and parameters
907         applicable to the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 5.5</a> of <a href="#Part1" id="rfc.xref.Part1.11"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
908      </p>
909      <p id="rfc.section.4.4.p.2">It <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages and <em class="bcp14">MAY</em> be included in other response messages to indicate that supplying credentials (or different credentials) might affect the
910         response.
911      </p>
912      <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.9"></span>  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> = 1#<a href="#challenge.and.response" class="smpl">challenge</a>
913</pre><p id="rfc.section.4.4.p.4">User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one
914         challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
915         comma-separated list of authentication parameters.
916      </p>
917      <div id="rfc.figure.u.9"></div> 
918      <p>For instance:</p>  <pre class="text">  WWW-Authenticate: Newauth realm="apps", type=1,
919                    title="Login to \"apps\"", Basic realm="simple"
920</pre>  <p>This header field contains two challenges; one for the "Newauth" scheme with a realm value of "apps", and two additional parameters
921         "type" and "title", and another one for the "Basic" scheme with a realm value of "simple".
922      </p>
923      <div class="note" id="rfc.section.4.4.p.6"> 
924         <p> <b>Note:</b> The challenge grammar production uses the list syntax as well. Therefore, a sequence of comma, whitespace, and comma can be
925            considered both as applying to the preceding challenge, or to be an empty entry in the list of challenges. In practice, this
926            ambiguity does not affect the semantics of the header field value and thus is harmless.
927         </p> 
928      </div>
929      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
930      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="authentication.scheme.registration" href="#authentication.scheme.registration">Authenticaton Scheme Registry</a></h2>
931      <p id="rfc.section.5.1.p.1">The registration procedure for HTTP Authentication Schemes is defined by <a href="#authentication.scheme.registry" title="Authentication Scheme Registry">Section&nbsp;2.3</a> of this document.
932      </p>
933      <p id="rfc.section.5.1.p.2">The HTTP Method Authentication Scheme shall be created at &lt;<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>&gt;.
934      </p>
935      <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2>
936      <p id="rfc.section.5.2.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; shall be updated with the registrations below:
937      </p>
938      <div id="rfc.table.1">
939         <div id="iana.status.code.registration.table"></div>
940         <table class="tt full left" cellpadding="3" cellspacing="0">
941            <thead>
942               <tr>
943                  <th>Value</th>
944                  <th>Description</th>
945                  <th>Reference</th>
946               </tr>
947            </thead>
948            <tbody>
949               <tr>
950                  <td class="left">401</td>
951                  <td class="left">Unauthorized</td>
952                  <td class="left"> <a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;3.1</a> 
953                  </td>
954               </tr>
955               <tr>
956                  <td class="left">407</td>
957                  <td class="left">Proxy Authentication Required</td>
958                  <td class="left"> <a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;3.2</a> 
959                  </td>
960               </tr>
961            </tbody>
962         </table>
963      </div>
964      <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>
965      <p id="rfc.section.5.3.p.1">The Message Header Field 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; shall 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>):
966      </p>
967      <div id="rfc.table.2">
968         <div id="iana.header.registration.table"></div>
969         <table class="tt full left" cellpadding="3" cellspacing="0">
970            <thead>
971               <tr>
972                  <th>Header Field Name</th>
973                  <th>Protocol</th>
974                  <th>Status</th>
975                  <th>Reference</th>
976               </tr>
977            </thead>
978            <tbody>
979               <tr>
980                  <td class="left">Authorization</td>
981                  <td class="left">http</td>
982                  <td class="left">standard</td>
983                  <td class="left"> <a href="#header.authorization" id="rfc.xref.header.authorization.3" title="Authorization">Section&nbsp;4.1</a> 
984                  </td>
985               </tr>
986               <tr>
987                  <td class="left">Proxy-Authenticate</td>
988                  <td class="left">http</td>
989                  <td class="left">standard</td>
990                  <td class="left"> <a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;4.2</a> 
991                  </td>
992               </tr>
993               <tr>
994                  <td class="left">Proxy-Authorization</td>
995                  <td class="left">http</td>
996                  <td class="left">standard</td>
997                  <td class="left"> <a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;4.3</a> 
998                  </td>
999               </tr>
1000               <tr>
1001                  <td class="left">WWW-Authenticate</td>
1002                  <td class="left">http</td>
1003                  <td class="left">standard</td>
1004                  <td class="left"> <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.3" title="WWW-Authenticate">Section&nbsp;4.4</a> 
1005                  </td>
1006               </tr>
1007            </tbody>
1008         </table>
1009      </div>
1010      <p id="rfc.section.5.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
1011      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
1012      <p id="rfc.section.6.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
1013         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
1014         make some suggestions for reducing security risks.
1015      </p>
1016      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="auth.credentials.and.idle.clients" href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
1017      <p id="rfc.section.6.1.p.1">Existing HTTP clients and user agents typically retain authentication information indefinitely. HTTP/1.1 does not provide
1018         a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
1019         extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
1020         but are not limited to:
1021      </p>
1022      <ul>
1023         <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
1024            the user for credentials.
1025         </li>
1026         <li>Applications which include a session termination indication (such as a "logout" or "commit" button on a page) after which
1027            the server side of the application "knows" that there is no further reason for the client to retain the credentials.
1028         </li>
1029      </ul>
1030      <p id="rfc.section.6.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
1031         use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
1032         in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
1033         for discarding cached credentials under user control.
1034      </p>
1035      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="acks" href="#acks">Acknowledgments</a></h1>
1036      <p id="rfc.section.7.p.1">This specification takes over the definition of the HTTP Authentication Framework, previously defined in <cite title="HTTP Authentication: Basic and Digest Access Authentication" id="rfc.xref.RFC2617.3">RFC 2617</cite>. We thank John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D. Lawrence, Paul J. Leach, Ari Luotonen, and
1037         Lawrence C. Stewart for their work on that specification. See <a href="http://tools.ietf.org/html/rfc2617#section-6">Section 6</a> of <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a> for further acknowledgements.
1038      </p>
1039      <p id="rfc.section.7.p.2">See <a href="p1-messaging.html#acks" title="Acknowledgments">Section 9</a> of <a href="#Part1" id="rfc.xref.Part1.12"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> for the Acknowledgments related to this document revision.
1040      </p>
1041      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
1042      </h1>
1043      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
1044      </h2>
1045      <table>       
1046         <tr>
1047            <td class="reference"><b id="Part1">[Part1]</b></td>
1048            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), March&nbsp;2012.
1049            </td>
1050         </tr>
1051         <tr>
1052            <td class="reference"><b id="Part6">[Part6]</b></td>
1053            <td class="top"><a href="mailto:fielding@gbiv.com" title="Adobe Systems Incorporated">Fielding, R., Ed.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net" title="Rackspace">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), March&nbsp;2012.
1054            </td>
1055         </tr>
1056         <tr>
1057            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
1058            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="http://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.
1059            </td>
1060         </tr>
1061         <tr>
1062            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
1063            <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="http://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
1064            </td>
1065         </tr>
1066      </table>
1067      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
1068      </h2>
1069      <table>           
1070         <tr>
1071            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
1072            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
1073            </td>
1074         </tr>
1075         <tr>
1076            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
1077            <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="http://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
1078            </td>
1079         </tr>
1080         <tr>
1081            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
1082            <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="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
1083            </td>
1084         </tr>
1085         <tr>
1086            <td class="reference"><b id="RFC3986">[RFC3986]</b></td>
1087            <td class="top"><a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R.</a>, and <a href="mailto:LMM@acm.org" title="Adobe Systems Incorporated">L. Masinter</a>, “<a href="http://tools.ietf.org/html/rfc3986">Uniform Resource Identifier (URI): Generic Syntax</a>”, STD&nbsp;66, RFC&nbsp;3986, January&nbsp;2005.
1088            </td>
1089         </tr>
1090         <tr>
1091            <td class="reference"><b id="RFC4648">[RFC4648]</b></td>
1092            <td class="top">Josefsson, S., “<a href="http://tools.ietf.org/html/rfc4648">The Base16, Base32, and Base64 Data Encodings</a>”, RFC&nbsp;4648, October&nbsp;2006.
1093            </td>
1094         </tr>
1095         <tr>
1096            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
1097            <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
1098            </td>
1099         </tr>
1100      </table>
1101      <div class="avoidbreak">
1102         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1103         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
1104               (editor)
1105               <span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Adobe Systems Incorporated</span><span class="adr"><span class="street-address vcardline">345 Park Ave</span><span class="vcardline"><span class="locality">San Jose</span>, <span class="region">CA</span>&nbsp;<span class="postal-code">95110</span></span><span class="country-name vcardline">USA</span></span><span class="vcardline">Email: <a href="mailto:fielding@gbiv.com"><span class="email">fielding@gbiv.com</span></a></span><span class="vcardline">URI: <a href="http://roy.gbiv.com/" class="url">http://roy.gbiv.com/</a></span></address>
1106         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
1107               (editor)
1108               <span class="n hidden"><span class="family-name">Lafon</span><span class="given-name">Yves</span></span></span><span class="org vcardline">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">W3C / ERCIM</span><span class="street-address vcardline">2004, rte des Lucioles</span><span class="vcardline"><span class="locality">Sophia-Antipolis</span>, <span class="region">AM</span>&nbsp;<span class="postal-code">06902</span></span><span class="country-name vcardline">France</span></span><span class="vcardline">Email: <a href="mailto:ylafon@w3.org"><span class="email">ylafon@w3.org</span></a></span><span class="vcardline">URI: <a href="http://www.raubacapeu.net/people/yves/" class="url">http://www.raubacapeu.net/people/yves/</a></span></address>
1109         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
1110               (editor)
1111               <span class="n hidden"><span class="family-name">Reschke</span><span class="given-name">Julian F.</span></span></span><span class="org vcardline">greenbytes GmbH</span><span class="adr"><span class="street-address vcardline">Hafenweg 16</span><span class="vcardline"><span class="locality">Muenster</span>, <span class="region">NW</span>&nbsp;<span class="postal-code">48155</span></span><span class="country-name vcardline">Germany</span></span><span class="vcardline tel">Phone: <a href="tel:+492512807760"><span class="value">+49 251 2807760</span></a></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+492512807761"><span class="value">+49 251 2807761</span></a></span><span class="vcardline">Email: <a href="mailto:julian.reschke@greenbytes.de"><span class="email">julian.reschke@greenbytes.de</span></a></span><span class="vcardline">URI: <a href="http://greenbytes.de/tech/webdav/" class="url">http://greenbytes.de/tech/webdav/</a></span></address>
1112      </div>
1113      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFCs 2616 and 2617</a></h1>
1114      <p id="rfc.section.A.p.1">The "realm" parameter isn't required anymore in general; consequently, the ABNF allows challenges without any auth parameters.
1115         (<a href="#access.authentication.framework" title="Access Authentication Framework">Section&nbsp;2</a>)
1116      </p>
1117      <p id="rfc.section.A.p.2">The "b64token" alternative to auth-param lists has been added for consistency with legacy authentication schemes such as "Basic".
1118         (<a href="#access.authentication.framework" title="Access Authentication Framework">Section&nbsp;2</a>)
1119      </p>
1120      <p id="rfc.section.A.p.3">Change ABNF productions for header fields to only define the field value. (<a href="#header.field.definitions" title="Header Field Definitions">Section&nbsp;4</a>)
1121      </p>
1122      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
1123      <div id="rfc.figure.u.10"></div> <pre class="inline"><a href="#header.authorization" class="smpl">Authorization</a> = credentials
1124
1125<a href="#core.rules" class="smpl">BWS</a> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
1126
1127<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
1128
1129<a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = *( "," OWS ) challenge *( OWS "," [ OWS
1130 challenge ] )
1131<a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> = credentials
1132
1133<a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> = *( "," OWS ) challenge *( OWS "," [ OWS challenge
1134 ] )
1135
1136<a href="#challenge.and.response" class="smpl">auth-param</a> = token BWS "=" BWS ( token / quoted-string )
1137<a href="#challenge.and.response" class="smpl">auth-scheme</a> = token
1138
1139<a href="#challenge.and.response" class="smpl">b64token</a> = 1*( ALPHA / DIGIT / "-" / "." / "_" / "~" / "+" / "/" )
1140 *"="
1141
1142<a href="#challenge.and.response" class="smpl">challenge</a> = auth-scheme [ 1*SP ( b64token / [ ( "," / auth-param ) *(
1143 OWS "," [ OWS auth-param ] ) ] ) ]
1144<a href="#challenge.and.response" class="smpl">credentials</a> = auth-scheme [ 1*SP ( b64token / [ ( "," / auth-param )
1145 *( OWS "," [ OWS auth-param ] ) ] ) ]
1146
1147<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
1148
1149<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 3.2.4&gt;
1150</pre> <div id="rfc.figure.u.11"></div>
1151      <p>ABNF diagnostics:</p><pre class="inline">; Authorization defined but not used
1152; Proxy-Authenticate defined but not used
1153; Proxy-Authorization defined but not used
1154; WWW-Authenticate defined but not used
1155</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1156      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC 2616
1157      </h2>
1158      <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>.
1159      </p>
1160      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
1161      </h2>
1162      <p id="rfc.section.C.2.p.1">Closed issues: </p>
1163      <ul>
1164         <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"
1165         </li>
1166      </ul>
1167      <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p7-auth-01
1168      </h2>
1169      <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;):
1170      </p>
1171      <ul>
1172         <li>Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.</li>
1173         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1174      </ul>
1175      <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></h2>
1176      <p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Field Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
1177      </p>
1178      <ul>
1179         <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
1180      </ul>
1181      <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></h2>
1182      <p id="rfc.section.C.5.p.1">None.</p>
1183      <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></h2>
1184      <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;):
1185      </p>
1186      <ul>
1187         <li>Use "/" instead of "|" for alternatives.</li>
1188         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1189         <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
1190      </ul>
1191      <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></h2>
1192      <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;):
1193      </p>
1194      <ul>
1195         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1196      </ul>
1197      <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></h2>
1198      <p id="rfc.section.C.8.p.1">None.</p>
1199      <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></h2>
1200      <p id="rfc.section.C.9.p.1">Closed issues: </p>
1201      <ul>
1202         <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"
1203         </li>
1204      </ul>
1205      <h2 id="rfc.section.C.10"><a href="#rfc.section.C.10">C.10</a>&nbsp;<a id="changes.since.08" href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></h2>
1206      <p id="rfc.section.C.10.p.1">No significant changes.</p>
1207      <h2 id="rfc.section.C.11"><a href="#rfc.section.C.11">C.11</a>&nbsp;<a id="changes.since.09" href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></h2>
1208      <p id="rfc.section.C.11.p.1">Partly resolved issues: </p>
1209      <ul>
1210         <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"
1211         </li>
1212      </ul>
1213      <h2 id="rfc.section.C.12"><a href="#rfc.section.C.12">C.12</a>&nbsp;<a id="changes.since.10" href="#changes.since.10">Since draft-ietf-httpbis-p7-auth-10</a></h2>
1214      <p id="rfc.section.C.12.p.1">None.</p>
1215      <h2 id="rfc.section.C.13"><a href="#rfc.section.C.13">C.13</a>&nbsp;<a id="changes.since.11" href="#changes.since.11">Since draft-ietf-httpbis-p7-auth-11</a></h2>
1216      <p id="rfc.section.C.13.p.1">Closed issues: </p>
1217      <ul>
1218         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/130">http://tools.ietf.org/wg/httpbis/trac/ticket/130</a>&gt;: "introduction to part 7 is work-in-progress"
1219         </li>
1220         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/195">http://tools.ietf.org/wg/httpbis/trac/ticket/195</a>&gt;: "auth-param syntax"
1221         </li>
1222         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/224">http://tools.ietf.org/wg/httpbis/trac/ticket/224</a>&gt;: "Header Classification"
1223         </li>
1224         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/237">http://tools.ietf.org/wg/httpbis/trac/ticket/237</a>&gt;: "absorbing the auth framework from 2617"
1225         </li>
1226      </ul>
1227      <p id="rfc.section.C.13.p.2">Partly resolved issues: </p>
1228      <ul>
1229         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/141">http://tools.ietf.org/wg/httpbis/trac/ticket/141</a>&gt;: "should we have an auth scheme registry"
1230         </li>
1231      </ul>
1232      <h2 id="rfc.section.C.14"><a href="#rfc.section.C.14">C.14</a>&nbsp;<a id="changes.since.12" href="#changes.since.12">Since draft-ietf-httpbis-p7-auth-12</a></h2>
1233      <p id="rfc.section.C.14.p.1">None.</p>
1234      <h2 id="rfc.section.C.15"><a href="#rfc.section.C.15">C.15</a>&nbsp;<a id="changes.since.13" href="#changes.since.13">Since draft-ietf-httpbis-p7-auth-13</a></h2>
1235      <p id="rfc.section.C.15.p.1">Closed issues: </p>
1236      <ul>
1237         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/276">http://tools.ietf.org/wg/httpbis/trac/ticket/276</a>&gt;: "untangle ABNFs for header fields"
1238         </li>
1239      </ul>
1240      <h2 id="rfc.section.C.16"><a href="#rfc.section.C.16">C.16</a>&nbsp;<a id="changes.since.14" href="#changes.since.14">Since draft-ietf-httpbis-p7-auth-14</a></h2>
1241      <p id="rfc.section.C.16.p.1">None.</p>
1242      <h2 id="rfc.section.C.17"><a href="#rfc.section.C.17">C.17</a>&nbsp;<a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p7-auth-15</a></h2>
1243      <p id="rfc.section.C.17.p.1">Closed issues: </p>
1244      <ul>
1245         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/78">http://tools.ietf.org/wg/httpbis/trac/ticket/78</a>&gt;: "Relationship between 401, Authorization and WWW-Authenticate"
1246         </li>
1247         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/177">http://tools.ietf.org/wg/httpbis/trac/ticket/177</a>&gt;: "Realm required on challenges"
1248         </li>
1249         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/195">http://tools.ietf.org/wg/httpbis/trac/ticket/195</a>&gt;: "auth-param syntax"
1250         </li>
1251         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/257">http://tools.ietf.org/wg/httpbis/trac/ticket/257</a>&gt;: "Considerations for new authentications schemes"
1252         </li>
1253         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/287">http://tools.ietf.org/wg/httpbis/trac/ticket/287</a>&gt;: "LWS in auth-param ABNF"
1254         </li>
1255         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/309">http://tools.ietf.org/wg/httpbis/trac/ticket/309</a>&gt;: "credentials ABNF missing SP (still using implied LWS?)"
1256         </li>
1257      </ul>
1258      <h2 id="rfc.section.C.18"><a href="#rfc.section.C.18">C.18</a>&nbsp;<a id="changes.since.16" href="#changes.since.16">Since draft-ietf-httpbis-p7-auth-16</a></h2>
1259      <p id="rfc.section.C.18.p.1">Closed issues: </p>
1260      <ul>
1261         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/186">http://tools.ietf.org/wg/httpbis/trac/ticket/186</a>&gt;: "Document HTTP's error-handling philosophy"
1262         </li>
1263         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/320">http://tools.ietf.org/wg/httpbis/trac/ticket/320</a>&gt;: "add advice on defining auth scheme parameters"
1264         </li>
1265      </ul>
1266      <h2 id="rfc.section.C.19"><a href="#rfc.section.C.19">C.19</a>&nbsp;<a id="changes.since.17" href="#changes.since.17">Since draft-ietf-httpbis-p7-auth-17</a></h2>
1267      <p id="rfc.section.C.19.p.1">Closed issues: </p>
1268      <ul>
1269         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/314">http://tools.ietf.org/wg/httpbis/trac/ticket/314</a>&gt;: "allow unquoted realm parameters"
1270         </li>
1271         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/321">http://tools.ietf.org/wg/httpbis/trac/ticket/321</a>&gt;: "Repeating auth-params"
1272         </li>
1273      </ul>
1274      <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p7-auth-18</a></h2>
1275      <p id="rfc.section.C.20.p.1">Closed issues: </p>
1276      <ul>
1277         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/334">http://tools.ietf.org/wg/httpbis/trac/ticket/334</a>&gt;: "recipient behavior for new auth parameters"
1278         </li>
1279         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/342">http://tools.ietf.org/wg/httpbis/trac/ticket/342</a>&gt;: "WWW-Authenticate ABNF slightly ambiguous"
1280         </li>
1281      </ul>
1282      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
1283      <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</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> 
1284      </p>
1285      <div class="print2col">
1286         <ul class="ind">
1287            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1288                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.12"><b>3.1</b></a>, <a href="#rfc.xref.status.401.1">5.2</a></li>
1289                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.13"><b>3.2</b></a>, <a href="#rfc.xref.status.407.1">5.2</a></li>
1290               </ul>
1291            </li>
1292            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1293                  <li><tt>auth-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.a.2"><b>2.1</b></a></li>
1294                  <li><tt>auth-scheme</tt>&nbsp;&nbsp;<a href="#rfc.iref.a.1"><b>2.1</b></a></li>
1295                  <li>Authorization header field&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">2.1</a>, <a href="#rfc.xref.header.authorization.2">3.1</a>, <a href="#rfc.iref.a.3"><b>4.1</b></a>, <a href="#rfc.xref.header.authorization.3">5.3</a></li>
1296               </ul>
1297            </li>
1298            <li><a id="rfc.index.B" href="#rfc.index.B"><b>B</b></a><ul>
1299                  <li><tt>b64token</tt>&nbsp;&nbsp;<a href="#rfc.iref.b.1"><b>2.1</b></a></li>
1300               </ul>
1301            </li>
1302            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1303                  <li><tt>challenge</tt>&nbsp;&nbsp;<a href="#rfc.iref.c.1"><b>2.1</b></a></li>
1304                  <li><tt>credentials</tt>&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>2.1</b></a></li>
1305               </ul>
1306            </li>
1307            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1308                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1309                     <ul>
1310                        <li><tt>auth-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2.1</b></a></li>
1311                        <li><tt>auth-scheme</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2.1</b></a></li>
1312                        <li><tt>Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>4.1</b></a></li>
1313                        <li><tt>b64token</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>2.1</b></a></li>
1314                        <li><tt>challenge</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>2.1</b></a></li>
1315                        <li><tt>credentials</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>2.1</b></a></li>
1316                        <li><tt>Proxy-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>4.2</b></a></li>
1317                        <li><tt>Proxy-Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>4.3</b></a></li>
1318                        <li><tt>WWW-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>4.4</b></a></li>
1319                     </ul>
1320                  </li>
1321               </ul>
1322            </li>
1323            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1324                  <li>Header Fields&nbsp;&nbsp;
1325                     <ul>
1326                        <li>Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">2.1</a>, <a href="#rfc.xref.header.authorization.2">3.1</a>, <a href="#rfc.iref.h.1"><b>4.1</b></a>, <a href="#rfc.xref.header.authorization.3">5.3</a></li>
1327                        <li>Proxy-Authenticate&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a href="#rfc.iref.h.2"><b>4.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">5.3</a></li>
1328                        <li>Proxy-Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a href="#rfc.iref.h.3"><b>4.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">5.3</a></li>
1329                        <li>WWW-Authenticate&nbsp;&nbsp;<a href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a href="#rfc.xref.header.www-authenticate.2">4.2</a>, <a href="#rfc.iref.h.4"><b>4.4</b></a>, <a href="#rfc.xref.header.www-authenticate.3">5.3</a></li>
1330                     </ul>
1331                  </li>
1332               </ul>
1333            </li>
1334            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1335                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a>, <a href="#rfc.xref.Part1.2">1.2</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a>, <a href="#rfc.xref.Part1.8">2.2</a>, <a href="#rfc.xref.Part1.9">2.3.1</a>, <a href="#rfc.xref.Part1.10">4.2</a>, <a href="#rfc.xref.Part1.11">4.4</a>, <a href="#rfc.xref.Part1.12">7</a>, <a href="#Part1"><b>8.1</b></a><ul>
1336                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2</a></li>
1337                        <li><em>Section 2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.1</a></li>
1338                        <li><em>Section 2.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.9">2.3.1</a></li>
1339                        <li><em>Section 3.2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a></li>
1340                        <li><em>Section 3.2.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">1.2.1</a>, <a href="#rfc.xref.Part1.7">1.2.1</a></li>
1341                        <li><em>Section 5.5</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.8">2.2</a>, <a href="#rfc.xref.Part1.10">4.2</a>, <a href="#rfc.xref.Part1.11">4.4</a></li>
1342                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.12">7</a></li>
1343                     </ul>
1344                  </li>
1345                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a>, <a href="#Part6"><b>8.1</b></a><ul>
1346                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a></li>
1347                     </ul>
1348                  </li>
1349                  <li>Protection Space&nbsp;&nbsp;<a href="#rfc.iref.p.1">2.2</a></li>
1350                  <li>Proxy-Authenticate header field&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a href="#rfc.iref.p.2"><b>4.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">5.3</a></li>
1351                  <li>Proxy-Authorization header field&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a href="#rfc.iref.p.3"><b>4.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">5.3</a></li>
1352               </ul>
1353            </li>
1354            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1355                  <li>Realm&nbsp;&nbsp;<a href="#rfc.iref.r.1">2.2</a></li>
1356                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li>
1357                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>8.2</b></a>, <a href="#rfc.xref.RFC2616.2">C.1</a></li>
1358                  <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">7</a>, <a href="#rfc.xref.RFC2617.4">7</a>, <a href="#RFC2617"><b>8.2</b></a><ul>
1359                        <li><em>Section 6</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2617.4">7</a></li>
1360                     </ul>
1361                  </li>
1362                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">5.3</a>, <a href="#RFC3864"><b>8.2</b></a></li>
1363                  <li><em>RFC3986</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3986.1">2.1</a>, <a href="#RFC3986"><b>8.2</b></a></li>
1364                  <li><em>RFC4648</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC4648.1">2.1</a>, <a href="#RFC4648"><b>8.2</b></a></li>
1365                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.3</a>, <a href="#RFC5226"><b>8.2</b></a><ul>
1366                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.3</a></li>
1367                     </ul>
1368                  </li>
1369                  <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>8.1</b></a><ul>
1370                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
1371                     </ul>
1372                  </li>
1373               </ul>
1374            </li>
1375            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1376                  <li>Status Codes&nbsp;&nbsp;
1377                     <ul>
1378                        <li>401 Unauthorized&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>3.1</b></a>, <a href="#rfc.xref.status.401.1">5.2</a></li>
1379                        <li>407 Proxy Authentication Required&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>3.2</b></a>, <a href="#rfc.xref.status.407.1">5.2</a></li>
1380                     </ul>
1381                  </li>
1382               </ul>
1383            </li>
1384            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
1385                  <li>WWW-Authenticate header field&nbsp;&nbsp;<a href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a href="#rfc.xref.header.www-authenticate.2">4.2</a>, <a href="#rfc.iref.w.1"><b>4.4</b></a>, <a href="#rfc.xref.header.www-authenticate.3">5.3</a></li>
1386               </ul>
1387            </li>
1388         </ul>
1389      </div>
1390   </body>
1391</html>
Note: See TracBrowser for help on using the repository browser.