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

Last change on this file since 1522 was 1522, checked in by julian.reschke@…, 8 years ago

bump up document dates, update to latest version of rfc2629.xslt, add feedback links

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