source: draft-ietf-httpbis/12/p7-auth.html @ 2726

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

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

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 80.2 KB
RevLine 
[52]1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
[2726]4   <head profile="http://dublincore.org/documents/2008/08/04/dc-html/">
[52]5      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
6      <title>HTTP/1.1, part 7: Authentication</title><style type="text/css" title="Xml2Rfc (sans serif)">
7a {
8  text-decoration: none;
9}
10a.smpl {
11  color: black;
12}
13a:hover {
14  text-decoration: underline;
15}
16a:active {
17  text-decoration: underline;
18}
19address {
20  margin-top: 1em;
21  margin-left: 2em;
22  font-style: normal;
23}
24body {
25  color: black;
[2726]26  font-family: cambria, helvetica, arial, sans-serif;
27  font-size: 11pt;
28  margin-right: 2em;
[52]29}
30cite {
31  font-style: normal;
32}
[998]33div.note {
34  margin-left: 2em;
35}
[52]36dl {
37  margin-left: 2em;
38}
[729]39ul.empty {
40  list-style-type: none;
41}
42ul.empty li {
[52]43  margin-top: .5em;
44}
45dl p {
46  margin-left: 0em;
47}
48dt {
49  margin-top: .5em;
50}
51h1 {
[2726]52  font-size: 130%;
[52]53  line-height: 21pt;
54  page-break-after: avoid;
55}
56h1.np {
57  page-break-before: always;
58}
59h2 {
[2726]60  font-size: 120%;
[52]61  line-height: 15pt;
62  page-break-after: avoid;
63}
[2726]64h3 {
65  font-size: 110%;
[52]66  page-break-after: avoid;
67}
[2726]68h4, h5, h6 {
69  page-break-after: avoid;
70}
71h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
[52]72  color: black;
73}
74img {
75  margin-left: 3em;
76}
77li {
78  margin-left: 2em;
79}
80ol {
81  margin-left: 2em;
82}
[2726]83ol.la {
84  list-style-type: lower-alpha;
85}
86ol.ua {
87  list-style-type: upper-alpha;
88}
[52]89ol p {
90  margin-left: 0em;
91}
92p {
93  margin-left: 2em;
94}
95pre {
96  margin-left: 3em;
97  background-color: lightyellow;
98  padding: .25em;
[2726]99  page-break-inside: avoid;
[52]100}
101pre.text2 {
102  border-style: dotted;
103  border-width: 1px;
104  background-color: #f0f0f0;
105  width: 69em;
106}
107pre.inline {
108  background-color: white;
109  padding: 0em;
110}
111pre.text {
112  border-style: dotted;
113  border-width: 1px;
114  background-color: #f8f8f8;
115  width: 69em;
116}
117pre.drawing {
118  border-style: solid;
119  border-width: 1px;
120  background-color: #f8f8f8;
121  padding: 2em;
122}
123table {
124  margin-left: 2em;
125}
[253]126table.tt {
127  vertical-align: top;
[2726]128  border-color: gray;
[253]129}
[2726]130table.tt th {
131  border-color: gray;
132}
133table.tt td {
134  border-color: gray;
135}
136table.all {
137  border-style: solid;
138  border-width: 2px;
139}
[253]140table.full {
[2726]141  border-style: solid;
142  border-width: 2px;
[253]143}
144table.tt td {
145  vertical-align: top;
146}
[2726]147table.all td {
148  border-style: solid;
149  border-width: 1px;
150}
[253]151table.full td {
[2726]152  border-style: none solid;
[253]153  border-width: 1px;
154}
155table.tt th {
156  vertical-align: top;
157}
[2726]158table.all th {
159  border-style: solid;
[253]160  border-width: 1px;
161}
[2726]162table.full th {
163  border-style: solid;
164  border-width: 1px 1px 2px 1px;
165}
[253]166table.headers th {
[2726]167  border-style: none none solid none;
168  border-width: 2px;
[253]169}
[675]170table.left {
171  margin-right: auto;
172}
173table.right {
174  margin-left: auto;
175}
176table.center {
177  margin-left: auto;
178  margin-right: auto;
179}
[454]180caption {
181  caption-side: bottom;
182  font-weight: bold;
[2726]183  font-size: 10pt;
[454]184  margin-top: .5em;
185}
186
[52]187table.header {
[729]188  border-spacing: 1px;
[52]189  width: 95%;
[2726]190  font-size: 11pt;
[52]191  color: white;
192}
193td.top {
194  vertical-align: top;
195}
196td.topnowrap {
197  vertical-align: top;
[2726]198  white-space: nowrap;
[52]199}
[729]200table.header td {
[52]201  background-color: gray;
202  width: 50%;
203}
[729]204table.header a {
[227]205  color: white;
206}
[52]207td.reference {
208  vertical-align: top;
209  white-space: nowrap;
210  padding-right: 1em;
211}
212thead {
213  display:table-header-group;
214}
[2726]215ul.toc, ul.toc ul {
[52]216  list-style: none;
217  margin-left: 1.5em;
218  padding-left: 0em;
219}
[2726]220ul.toc li {
[52]221  line-height: 150%;
222  font-weight: bold;
223  margin-left: 0em;
224}
[2726]225ul.toc li li {
[52]226  line-height: normal;
227  font-weight: normal;
[2726]228  font-size: 10pt;
[52]229  margin-left: 0em;
230}
[2726]231li.excluded {
[52]232  font-size: 0pt;
233}
234ul p {
235  margin-left: 0em;
236}
[2726]237.title, .filename, h1, h2, h3, h4 {
238  font-family: candara, helvetica, arial, sans-serif;
239}
240samp, tt, code, pre {
241  font: consolas, monospace;
242}
243ul.ind, ul.ind ul {
[52]244  list-style: none;
245  margin-left: 1.5em;
246  padding-left: 0em;
[440]247  page-break-before: avoid;
[52]248}
[2726]249ul.ind li {
[52]250  font-weight: bold;
251  line-height: 200%;
252  margin-left: 0em;
253}
[2726]254ul.ind li li {
[52]255  font-weight: normal;
256  line-height: 150%;
257  margin-left: 0em;
258}
[662]259.avoidbreak {
260  page-break-inside: avoid;
261}
[52]262.bcp14 {
263  font-style: normal;
264  text-transform: lowercase;
265  font-variant: small-caps;
266}
267.comment {
268  background-color: yellow;
269}
270.center {
271  text-align: center;
272}
273.error {
274  color: red;
275  font-style: italic;
276  font-weight: bold;
277}
278.figure {
279  font-weight: bold;
280  text-align: center;
[2726]281  font-size: 10pt;
[52]282}
283.filename {
284  color: #333333;
[2726]285  font-size: 75%;
[52]286  font-weight: bold;
287  line-height: 21pt;
288  text-align: center;
289}
290.fn {
291  font-weight: bold;
292}
293.left {
294  text-align: left;
295}
296.right {
297  text-align: right;
298}
299.title {
[2726]300  color: green;
301  font-size: 150%;
[52]302  line-height: 18pt;
303  font-weight: bold;
304  text-align: center;
305  margin-top: 36pt;
306}
307.warning {
[2726]308  font-size: 130%;
[52]309  background-color: yellow;
310}
311
312
313@media print {
314  .noprint {
315    display: none;
316  }
[2726]317
[52]318  a {
319    color: black;
320    text-decoration: none;
321  }
322
323  table.header {
324    width: 90%;
325  }
326
327  td.header {
328    width: 50%;
329    color: black;
330    background-color: white;
331    vertical-align: top;
[2726]332    font-size: 110%;
[52]333  }
334
[2726]335  ul.toc a:nth-child(2)::after {
[52]336    content: leader('.') target-counter(attr(href), page);
337  }
[2726]338
339  ul.ind li li a {
[52]340    content: target-counter(attr(href), page);
341  }
[2726]342
[52]343  .print2col {
344    column-count: 2;
345    -moz-column-count: 2;
346    column-fill: auto;
347  }
348}
349
350@page {
351  @top-left {
[2726]352       content: "Internet-Draft";
353  }
[52]354  @top-right {
[2726]355       content: "October 2010";
356  }
[52]357  @top-center {
[2726]358       content: "HTTP/1.1, Part 7";
359  }
[52]360  @bottom-left {
[2726]361       content: "Fielding, et al.";
362  }
[52]363  @bottom-center {
[2726]364       content: "Expires April 28, 2011";
365  }
[52]366  @bottom-right {
[2726]367       content: "[Page " counter(page) "]";
368  }
[52]369}
370
[2726]371@page:first {
[52]372    @top-left {
373      content: normal;
374    }
375    @top-right {
376      content: normal;
377    }
378    @top-center {
379      content: normal;
380    }
381}
382</style><link rel="Contents" href="#rfc.toc">
383      <link rel="Author" href="#rfc.authors">
[754]384      <link rel="Copyright" href="#rfc.copyrightnotice">
[52]385      <link rel="Index" href="#rfc.index">
386      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
[998]387      <link rel="Chapter" title="2 Access Authentication Framework" href="#rfc.section.2">
388      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
389      <link rel="Chapter" title="4 Header Field Definitions" href="#rfc.section.4">
390      <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5">
391      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
392      <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
393      <link rel="Chapter" href="#rfc.section.8" title="8 References">
[912]394      <link rel="Appendix" title="A Collected ABNF" href="#rfc.section.A">
395      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
[2726]396      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
[754]397      <link rel="schema.dct" href="http://purl.org/dc/terms/">
398      <meta name="dct.creator" content="Fielding, R.">
399      <meta name="dct.creator" content="Gettys, J.">
400      <meta name="dct.creator" content="Mogul, J.">
401      <meta name="dct.creator" content="Frystyk, H.">
402      <meta name="dct.creator" content="Masinter, L.">
403      <meta name="dct.creator" content="Leach, P.">
404      <meta name="dct.creator" content="Berners-Lee, T.">
405      <meta name="dct.creator" content="Lafon, Y.">
406      <meta name="dct.creator" content="Reschke, J. F.">
[1051]407      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-12">
408      <meta name="dct.issued" scheme="ISO8601" content="2010-10-25">
[754]409      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
410      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">
[689]411      <meta name="description" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication.">
[52]412   </head>
413   <body>
[729]414      <table class="header">
415         <tbody>
416            <tr>
417               <td class="left">HTTPbis Working Group</td>
418               <td class="right">R. Fielding, Editor</td>
419            </tr>
420            <tr>
[754]421               <td class="left">Internet-Draft</td>
[729]422               <td class="right">Day Software</td>
423            </tr>
424            <tr>
[2726]425               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
[729]426               </td>
427               <td class="right">J. Gettys</td>
428            </tr>
429            <tr>
[2726]430               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2617">2617</a> (if approved)
[729]431               </td>
[844]432               <td class="right">Alcatel-Lucent</td>
[729]433            </tr>
434            <tr>
[741]435               <td class="left">Intended status: Standards Track</td>
[729]436               <td class="right">J. Mogul</td>
437            </tr>
438            <tr>
[1051]439               <td class="left">Expires: April 28, 2011</td>
[729]440               <td class="right">HP</td>
441            </tr>
442            <tr>
[741]443               <td class="left"></td>
[729]444               <td class="right">H. Frystyk</td>
445            </tr>
446            <tr>
447               <td class="left"></td>
448               <td class="right">Microsoft</td>
449            </tr>
450            <tr>
451               <td class="left"></td>
452               <td class="right">L. Masinter</td>
453            </tr>
454            <tr>
455               <td class="left"></td>
456               <td class="right">Adobe Systems</td>
457            </tr>
458            <tr>
459               <td class="left"></td>
460               <td class="right">P. Leach</td>
461            </tr>
462            <tr>
463               <td class="left"></td>
464               <td class="right">Microsoft</td>
465            </tr>
466            <tr>
467               <td class="left"></td>
468               <td class="right">T. Berners-Lee</td>
469            </tr>
470            <tr>
471               <td class="left"></td>
472               <td class="right">W3C/MIT</td>
473            </tr>
474            <tr>
475               <td class="left"></td>
476               <td class="right">Y. Lafon, Editor</td>
477            </tr>
478            <tr>
479               <td class="left"></td>
480               <td class="right">W3C</td>
481            </tr>
482            <tr>
483               <td class="left"></td>
[832]484               <td class="right">J. Reschke, Editor</td>
[729]485            </tr>
486            <tr>
487               <td class="left"></td>
488               <td class="right">greenbytes</td>
489            </tr>
490            <tr>
491               <td class="left"></td>
[1051]492               <td class="right">October 25, 2010</td>
[729]493            </tr>
494         </tbody>
[52]495      </table>
[1051]496      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-12</span></p>
[2726]497      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
[723]498      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
499         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
500         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
501         7 defines HTTP Authentication.
[2726]502      </p>
503      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
[723]504      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
[848]505         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;.
[2726]506      </p>
[973]507      <p>The changes in this draft are summarized in <a href="#changes.since.11" title="Since draft-ietf-httpbis-p7-auth-11">Appendix&nbsp;B.13</a>.
[52]508      </p>
[2726]509      <div id="rfc.status">
510         <h1><a href="#rfc.status">Status of This Memo</a></h1>
511         <p>This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.</p>
512         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute
513            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>.
514         </p>
515         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
516            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
517            in progress”.
518         </p>
519         <p>This Internet-Draft will expire on April 28, 2011.</p>
520      </div>
521      <div id="rfc.copyrightnotice">
522         <h1><a href="#rfc.copyrightnotice">Copyright Notice</a></h1>
523         <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
524         <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
525            and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License
526            text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified
527            BSD License.
528         </p>
529         <p>This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November
530            10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to
531            allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s)
532            controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative
533            works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate
534            it into languages other than English.
535         </p>
536      </div>
[52]537      <hr class="noprint">
538      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
539      <ul class="toc">
[2726]540         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
541               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
542               <li><a href="#rfc.section.1.2">1.2</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
543                     <li><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
[424]544                  </ul>
545               </li>
[96]546            </ul>
547         </li>
[2726]548         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#access.authentication.framework">Access Authentication Framework</a><ul>
549               <li><a href="#rfc.section.2.1">2.1</a>&nbsp;&nbsp;&nbsp;<a href="#authentication.scheme.registry">Authentication Scheme Registry</a></li>
[1026]550            </ul>
551         </li>
[2726]552         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul>
553               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
554               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
[52]555            </ul>
556         </li>
[2726]557         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
558               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
559               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
560               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
561               <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
[52]562            </ul>
563         </li>
[2726]564         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
565               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#authentication.scheme.registration">Authenticaton Scheme Registry</a></li>
566               <li><a href="#rfc.section.5.2">5.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li>
567               <li><a href="#rfc.section.5.3">5.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li>
[253]568            </ul>
569         </li>
[2726]570         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
571               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
[52]572            </ul>
573         </li>
[2726]574         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
575         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
576               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
577               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
[119]578            </ul>
579         </li>
[2726]580         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
581         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
582               <li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC 2616</a></li>
583               <li><a href="#rfc.section.B.2">B.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
584               <li><a href="#rfc.section.B.3">B.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.3">Since draft-ietf-httpbis-p7-auth-01</a></li>
585               <li><a href="#rfc.section.B.4">B.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></li>
586               <li><a href="#rfc.section.B.5">B.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></li>
587               <li><a href="#rfc.section.B.6">B.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></li>
588               <li><a href="#rfc.section.B.7">B.7</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></li>
589               <li><a href="#rfc.section.B.8">B.8</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></li>
590               <li><a href="#rfc.section.B.9">B.9</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></li>
591               <li><a href="#rfc.section.B.10">B.10</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></li>
592               <li><a href="#rfc.section.B.11">B.11</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></li>
593               <li><a href="#rfc.section.B.12">B.12</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p7-auth-10</a></li>
594               <li><a href="#rfc.section.B.13">B.13</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p7-auth-11</a></li>
[99]595            </ul>
596         </li>
[2726]597         <li><a href="#rfc.index">Index</a></li>
598         <li><a href="#rfc.authors">Authors' Addresses</a></li>
[52]599      </ul>
[2726]600      <div id="introduction">
601         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
602         <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:
603            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>).
604         </p>
605         <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
606            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>.
607         </p>
608         <div id="intro.requirements">
609            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
610            <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"
611               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>.
612            </p>
613            <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the "MUST" or "REQUIRED" level requirements for the
614               protocols it implements. An implementation that satisfies all the "MUST" or "REQUIRED" level and all the "SHOULD" level requirements
615               for its protocols is said to be "unconditionally compliant"; one that satisfies all the "MUST" level requirements but not
616               all the "SHOULD" level requirements for its protocols is said to be "conditionally compliant".
617            </p>
618         </div>
619         <div id="notation">
620            <h2 id="rfc.section.1.2"><a href="#rfc.section.1.2">1.2</a>&nbsp;<a href="#notation">Syntax Notation</a></h2>
621            <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;A</a> shows the collected ABNF, with the list rule expanded.
622            </p>
623            <p id="rfc.section.1.2.p.2">The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="https://tools.ietf.org/html/rfc5234#appendix-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
624               (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
625               and WSP (whitespace).
626            </p>
627            <div id="core.rules">
628               <h3 id="rfc.section.1.2.1"><a href="#rfc.section.1.2.1">1.2.1</a>&nbsp;<a href="#core.rules">Core Rules</a></h3>
629               <p id="rfc.section.1.2.1.p.1">The core rules below are defined in <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a> of <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>:
630               </p>
631               <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
[998]632  <a href="#core.rules" class="smpl">token</a>         = &lt;token, 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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
633  <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#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
[2726]634</pre></div>
635         </div>
636      </div>
637      <div id="access.authentication.framework">
638         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#access.authentication.framework">Access Authentication Framework</a></h1>
639         <p id="rfc.section.2.p.1">HTTP provides a simple challenge-response authentication mechanism that can be used by a server to challenge a client request
640            and by a client to provide authentication information. It uses an extensible, case-insensitive token to identify the authentication
641            scheme, followed by a comma-separated list of attribute-value pairs which carry the parameters necessary for achieving authentication
642            via that scheme.
643         </p>
644         <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.a.1"></span><span id="rfc.iref.a.2"></span>  auth-scheme    = token
[998]645  auth-param     = token "=" ( token / quoted-string )
646</pre><p id="rfc.section.2.p.3">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. The 407 (Proxy
[2726]647            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.
648         </p>
649         <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.c.1"></span>  <a href="#access.authentication.framework" class="smpl">challenge</a>   = <a href="#access.authentication.framework" class="smpl">auth-scheme</a> 1*<a href="#notation" class="smpl">SP</a> 1#<a href="#access.authentication.framework" class="smpl">auth-param</a>
650</pre><div class="note" id="rfc.section.2.p.5">
651            <p><b>Note:</b> User agents will need to take special care in parsing the WWW-Authenticate or Proxy-Authenticate header field value if it
652               contains more than one challenge, or if more than one WWW-Authenticate header field is provided, since the contents of a challenge
653               can itself contain a comma-separated list of authentication parameters.
654            </p>
655         </div>
656         <div class="note" id="rfc.section.2.p.6">
657            <p><b>Note:</b> Many browsers fail to parse challenges containing unknown schemes. A workaround for this problem is to list well-supported
658               schemes (such as "basic") first.
659            </p>
660         </div>
661         <p id="rfc.section.2.p.7">The authentication parameter realm is defined for all authentication schemes:</p>
662         <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.r.1"></span><span id="rfc.iref.r.2"></span>  realm       = "realm" "=" realm-value
[998]663  realm-value = quoted-string
[1018]664</pre><p id="rfc.section.2.p.9">The realm directive (case-insensitive) is required for all authentication schemes that issue a challenge. The realm value
[2726]665            (case-sensitive), in combination with the canonical root URI (the scheme and authority components of the effective request
666            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.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) of the server being accessed, defines the protection space. These realms allow the protected resources on a server to be
667            partitioned into a set of protection spaces, each with its own authentication scheme and/or authorization database. The realm
668            value is a string, generally assigned by the origin server, which can have additional semantics specific to the authentication
669            scheme. Note that there can be multiple challenges with the same auth-scheme but different realms.
670         </p>
671         <p id="rfc.section.2.p.10">A user agent that wishes to authenticate itself with an origin server -- usually, but not necessarily, after receiving a 401
672            (Unauthorized) -- <em class="bcp14">MAY</em> do so by including an Authorization header field with the request. A client that wishes to authenticate itself with a proxy
673            -- usually, but not necessarily, after receiving a 407 (Proxy Authentication Required) -- <em class="bcp14">MAY</em> do so by including a Proxy-Authorization header field with the request. Both the Authorization field value and the Proxy-Authorization
674            field value consist of credentials containing the authentication information of the client for the realm of the resource being
675            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
676            upon that challenge.
677         </p>
678         <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.c.2"></span>  <a href="#access.authentication.framework" class="smpl">credentials</a> = <a href="#access.authentication.framework" class="smpl">auth-scheme</a> ( <a href="#core.rules" class="smpl">token</a>
[998]679                            / <a href="#core.rules" class="smpl">quoted-string</a>
680                            / #<a href="#access.authentication.framework" class="smpl">auth-param</a> )
[1018]681</pre><p id="rfc.section.2.p.12">The protection space determines the domain over which credentials can be automatically applied. If a prior request has been
[2726]682            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,
683            parameters, and/or user preference. Unless otherwise defined by the authentication scheme, a single protection space cannot
684            extend outside the scope of its server.
685         </p>
686         <p id="rfc.section.2.p.13">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.
687            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
688            resource.
689         </p>
690         <p id="rfc.section.2.p.14">The HTTP protocol does not restrict applications to this simple challenge-response mechanism for access authentication. Additional
691            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
692            authentication information. However, these additional mechanisms are not defined by this specification.
693         </p>
694         <p id="rfc.section.2.p.15">Proxies <em class="bcp14">MUST</em> be completely transparent regarding user agent authentication by origin servers. That is, they <em class="bcp14">MUST</em> forward the WWW-Authenticate and Authorization headers untouched, and follow the rules found in <a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;4.1</a>. Both the Proxy-Authenticate and the Proxy-Authorization header fields are hop-by-hop headers (see <a href="p1-messaging.html#end-to-end.and.hop-by-hop.header-fields" title="End-to-end and Hop-by-hop Header Fields">Section 7.1.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>).
695         </p>
696         <div id="authentication.scheme.registry">
697            <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a href="#authentication.scheme.registry">Authentication Scheme Registry</a></h2>
698            <p id="rfc.section.2.1.p.1">The HTTP Authentication Scheme Registry defines the name space for the authentication schemes in challenges and credentials.</p>
699            <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields:
700            </p>
701            <ul>
702               <li>Authentication Scheme Name</li>
703               <li>Pointer to specification text</li>
704            </ul>
705            <p id="rfc.section.2.1.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="https://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>).
706            </p>
707            <p id="rfc.section.2.1.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;.
708            </p>
709         </div>
710      </div>
711      <div id="status.code.definitions">
712         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a href="#status.code.definitions">Status Code Definitions</a></h1>
713         <div id="status.401">
714            <div id="rfc.iref.4.1"></div>
715            <div id="rfc.iref.s.1"></div>
716            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#status.401">401 Unauthorized</a></h2>
717            <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
718               refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
719               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
720               information.
721            </p>
722         </div>
723         <div id="status.407">
724            <div id="rfc.iref.4.2"></div>
725            <div id="rfc.iref.s.2"></div>
726            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></h2>
727            <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.
728               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>).
729            </p>
730         </div>
731      </div>
732      <div id="header.fields">
733         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
734         <p id="rfc.section.4.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
735         <div id="header.authorization">
736            <div id="rfc.iref.a.3"></div>
737            <div id="rfc.iref.h.1"></div>
738            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#header.authorization">Authorization</a></h2>
739            <p id="rfc.section.4.1.p.1">The "Authorization" request-header field allows a user agent to authenticate itself with a server -- usually, but not necessarily,
740               after receiving a 401 (Unauthorized) response. Its value consists of credentials containing information of the user agent
741               for the realm of the resource being requested.
742            </p>
743            <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#header.authorization" class="smpl">Authorization</a>   = "Authorization" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.authorization" class="smpl">Authorization-v</a>
[998]744  <a href="#header.authorization" class="smpl">Authorization-v</a> = <a href="#access.authentication.framework" class="smpl">credentials</a>
745</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,
[2726]746               such as credentials that vary according to a challenge value or using synchronized clocks).
747            </p>
748            <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:
749            </p>
750            <p id="rfc.section.4.1.p.5"></p>
751            <ol>
752               <li>If the response includes the "s-maxage" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But (if the specified maximum age has passed) a proxy cache <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-header fields from the new request to allow the origin server
753                  to authenticate 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.
754               </li>
755               <li>If the response includes the "must-revalidate" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But if the response is stale, all caches <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-header fields from the new request to allow the origin server
756                  to authenticate the new request.
757               </li>
758               <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
759               </li>
760            </ol>
761         </div>
762         <div id="header.proxy-authenticate">
763            <div id="rfc.iref.p.1"></div>
764            <div id="rfc.iref.h.2"></div>
765            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
766            <p id="rfc.section.4.2.p.1">The "Proxy-Authenticate" response-header field consists of a challenge that indicates the authentication scheme and parameters
767               applicable to the proxy for this effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.8"><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.
768            </p>
769            <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a>   = "Proxy-Authenticate" ":" <a href="#core.rules" class="smpl">OWS</a>
[376]770                         <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a>
[998]771  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a> = 1#<a href="#access.authentication.framework" class="smpl">challenge</a>
772</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
[2726]773               them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
774               header field.
775            </p>
776         </div>
777         <div id="header.proxy-authorization">
778            <div id="rfc.iref.p.2"></div>
779            <div id="rfc.iref.h.3"></div>
780            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></h2>
781            <p id="rfc.section.4.3.p.1">The "Proxy-Authorization" request-header field allows the client to identify itself (or its user) to a proxy which requires
782               authentication. Its value consists of credentials containing the authentication information of the user agent for the proxy
783               and/or realm of the resource being requested.
784            </p>
785            <div id="rfc.figure.u.8"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a>   = "Proxy-Authorization" ":" <a href="#core.rules" class="smpl">OWS</a>
[376]786                          <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a>
[998]787  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a> = <a href="#access.authentication.framework" class="smpl">credentials</a>
788</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
[2726]789               using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
790               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
791               authenticate a given request.
792            </p>
793         </div>
794         <div id="header.www-authenticate">
795            <div id="rfc.iref.w.1"></div>
796            <div id="rfc.iref.h.4"></div>
797            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></h2>
798            <p id="rfc.section.4.4.p.1">The "WWW-Authenticate" response-header field consists of at least one challenge that indicates the authentication scheme(s)
799               and parameters applicable to the effective request URI (<a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.9"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). It <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages.
800            </p>
801            <div id="rfc.figure.u.9"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span>  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a>   = "WWW-Authenticate" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a>
[998]802  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a> = 1#<a href="#access.authentication.framework" class="smpl">challenge</a>
803</pre><p id="rfc.section.4.4.p.3">User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one
[2726]804               challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
805               comma-separated list of authentication parameters.
806            </p>
807         </div>
[700]808      </div>
[2726]809      <div id="IANA.considerations">
810         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
811         <div id="authentication.scheme.registration">
812            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#authentication.scheme.registration">Authenticaton Scheme Registry</a></h2>
813            <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.1</a> of this document.
814            </p>
815            <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;.
816            </p>
817         </div>
818         <div id="status.code.registration">
819            <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<a href="#status.code.registration">Status Code Registration</a></h2>
820            <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:
821            </p>
822            <div id="rfc.table.1">
823               <div id="iana.status.code.registration.table"></div>
824               <table class="tt full left" cellpadding="3" cellspacing="0">
825                  <thead>
826                     <tr>
827                        <th>Value</th>
828                        <th>Description</th>
829                        <th>Reference</th>
830                     </tr>
831                  </thead>
832                  <tbody>
833                     <tr>
834                        <td class="left">401</td>
835                        <td class="left">Unauthorized</td>
836                        <td class="left"><a href="#status.401" id="rfc.xref.status.401.1" title="401 Unauthorized">Section&nbsp;3.1</a>
837                        </td>
838                     </tr>
839                     <tr>
840                        <td class="left">407</td>
841                        <td class="left">Proxy Authentication Required</td>
842                        <td class="left"><a href="#status.407" id="rfc.xref.status.407.1" title="407 Proxy Authentication Required">Section&nbsp;3.2</a>
843                        </td>
844                     </tr>
845                  </tbody>
846               </table>
847            </div>
848         </div>
849         <div id="header.field.registration">
850            <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a>&nbsp;<a href="#header.field.registration">Header Field Registration</a></h2>
851            <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>):
852            </p>
853            <div id="rfc.table.2">
854               <div id="iana.header.registration.table"></div>
855               <table class="tt full left" cellpadding="3" cellspacing="0">
856                  <thead>
857                     <tr>
858                        <th>Header Field Name</th>
859                        <th>Protocol</th>
860                        <th>Status</th>
861                        <th>Reference</th>
862                     </tr>
863                  </thead>
864                  <tbody>
865                     <tr>
866                        <td class="left">Authorization</td>
867                        <td class="left">http</td>
868                        <td class="left">standard</td>
869                        <td class="left"><a href="#header.authorization" id="rfc.xref.header.authorization.3" title="Authorization">Section&nbsp;4.1</a>
870                        </td>
871                     </tr>
872                     <tr>
873                        <td class="left">Proxy-Authenticate</td>
874                        <td class="left">http</td>
875                        <td class="left">standard</td>
876                        <td class="left"><a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;4.2</a>
877                        </td>
878                     </tr>
879                     <tr>
880                        <td class="left">Proxy-Authorization</td>
881                        <td class="left">http</td>
882                        <td class="left">standard</td>
883                        <td class="left"><a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;4.3</a>
884                        </td>
885                     </tr>
886                     <tr>
887                        <td class="left">WWW-Authenticate</td>
888                        <td class="left">http</td>
889                        <td class="left">standard</td>
890                        <td class="left"><a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section&nbsp;4.4</a>
891                        </td>
892                     </tr>
893                  </tbody>
894               </table>
895            </div>
896            <p id="rfc.section.5.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
897         </div>
[253]898      </div>
[2726]899      <div id="security.considerations">
900         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
901         <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
902            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
903            make some suggestions for reducing security risks.
904         </p>
905         <div id="auth.credentials.and.idle.clients">
906            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
907            <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
908               a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
909               extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
910               but are not limited to:
911            </p>
912            <ul>
913               <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
914                  the user for credentials.
915               </li>
916               <li>Applications which include a session termination indication (such as a "logout" or "commit" button on a page) after which
917                  the server side of the application "knows" that there is no further reason for the client to retain the credentials.
918               </li>
919            </ul>
920            <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
921               use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
922               in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
923               for discarding cached credentials under user control.
924            </p>
925         </div>
926      </div>
927      <div id="ack">
928         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
929         <p id="rfc.section.7.p.1">This specification takes over the definition of the HTTP Authentication Framework, previously defined in <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.2">RFC 2617</cite>. We thank to John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D. Lawrence, Paul J. Leach, Ari Luotonen,
930            and Lawrence C. Stewart for their work on that specification.
931         </p>
932         <p id="rfc.section.7.p.2"><span class="comment" id="acks">[<a href="#acks" class="smpl">acks</a>: HTTPbis acknowledgements.]</span>
933         </p>
934      </div>
[998]935      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
[52]936      </h1>
[998]937      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
[119]938      </h2>
[2726]939      <table>
[52]940         <tr>
[205]941            <td class="reference"><b id="Part1">[Part1]</b></td>
[2726]942            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-12">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-12 (work in progress), October&nbsp;2010.
[205]943            </td>
944         </tr>
945         <tr>
[52]946            <td class="reference"><b id="Part6">[Part6]</b></td>
[2726]947            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@freedesktop.org" title="Alcatel-Lucent Bell Labs">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, <a href="mailto:mnot@mnot.net">Nottingham, M., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. Reschke, Ed.</a>, “<a href="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-12">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-12 (work in progress), October&nbsp;2010.
[52]948            </td>
949         </tr>
950         <tr>
[96]951            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
[2726]952            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
[96]953            </td>
954         </tr>
955         <tr>
[425]956            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
[2726]957            <td class="top"><a href="mailto:dcrocker@bbiw.net" title="Brandenburg InternetWorking">Crocker, D., Ed.</a> and <a href="mailto:paul.overell@thus.net" title="THUS plc.">P. Overell</a>, “<a href="https://tools.ietf.org/html/rfc5234">Augmented BNF for Syntax Specifications: ABNF</a>”, STD&nbsp;68, RFC&nbsp;5234, January&nbsp;2008.
[425]958            </td>
959         </tr>
[119]960      </table>
[998]961      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
[119]962      </h2>
[2726]963      <table>
[52]964         <tr>
[119]965            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
[2726]966            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
[52]967            </td>
968         </tr>
[253]969         <tr>
[998]970            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
[2726]971            <td class="top"><a href="mailto:john@math.nwu.edu" title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a href="mailto:pbaker@verisign.com" title="Verisign Inc.">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com" title="AbiSource, Inc.">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com" title="Open Market, Inc.">L. Stewart</a>, “<a href="https://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
[998]972            </td>
973         </tr>
974         <tr>
[253]975            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
[2726]976            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
[253]977            </td>
978         </tr>
[1026]979         <tr>
980            <td class="reference"><b id="RFC5226">[RFC5226]</b></td>
[2726]981            <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="https://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP&nbsp;26, RFC&nbsp;5226, May&nbsp;2008.
[1026]982            </td>
983         </tr>
[52]984      </table>
[2726]985      <div id="collected.abnf">
986         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#collected.abnf">Collected ABNF</a></h1>
987         <div id="rfc.figure.u.10"></div><pre class="inline"><a href="#header.authorization" class="smpl">Authorization</a> = "Authorization:" OWS Authorization-v
[427]988<a href="#header.authorization" class="smpl">Authorization-v</a> = credentials
989
990<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
991
992<a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = "Proxy-Authenticate:" OWS Proxy-Authenticate-v
993<a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a> = *( "," OWS ) challenge *( OWS "," [ OWS
[421]994 challenge ] )
[427]995<a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> = "Proxy-Authorization:" OWS
[421]996 Proxy-Authorization-v
[427]997<a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a> = credentials
998
999<a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> = "WWW-Authenticate:" OWS WWW-Authenticate-v
1000<a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a> = *( "," OWS ) challenge *( OWS "," [ OWS
[421]1001 challenge ] )
[428]1002
[998]1003<a href="#access.authentication.framework" class="smpl">auth-param</a> = token "=" ( token / quoted-string )
1004<a href="#access.authentication.framework" class="smpl">auth-scheme</a> = token
1005
1006<a href="#access.authentication.framework" class="smpl">challenge</a> = auth-scheme 1*SP *( "," OWS ) auth-param *( OWS "," [ OWS
1007 auth-param ] )
1008<a href="#access.authentication.framework" class="smpl">credentials</a> = auth-scheme ( token / quoted-string / [ ( "," /
1009 auth-param ) *( OWS "," [ OWS auth-param ] ) ] )
1010
1011<a href="#core.rules" class="smpl">quoted-string</a> = &lt;quoted-string, defined in [Part1], Section 1.2.2&gt;
1012
1013realm = "realm=" realm-value
1014realm-value = quoted-string
1015
1016<a href="#core.rules" class="smpl">token</a> = &lt;token, defined in [Part1], Section 1.2.2&gt;
[2726]1017</pre><div id="rfc.figure.u.11"></div>
1018         <p>ABNF diagnostics:</p><pre class="inline">; Authorization defined but not used
[421]1019; Proxy-Authenticate defined but not used
1020; Proxy-Authorization defined but not used
1021; WWW-Authenticate defined but not used
[998]1022; realm defined but not used
[2726]1023</pre></div>
1024      <div id="change.log">
1025         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
1026         <div>
1027            <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC 2616
1028            </h2>
1029            <p id="rfc.section.B.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
1030            </p>
1031         </div>
1032         <div>
1033            <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
1034            </h2>
1035            <p id="rfc.section.B.2.p.1">Closed issues: </p>
1036            <ul>
1037               <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"
1038               </li>
1039            </ul>
1040         </div>
1041         <div>
1042            <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a>&nbsp;Since draft-ietf-httpbis-p7-auth-01
1043            </h2>
1044            <p id="rfc.section.B.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;):
1045            </p>
1046            <ul>
1047               <li>Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.</li>
1048               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
1049            </ul>
1050         </div>
1051         <div id="changes.since.02">
1052            <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></h2>
1053            <p id="rfc.section.B.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;):
1054            </p>
1055            <ul>
1056               <li>Reference RFC 3984, and update header field registrations for header fields defined in this document.</li>
1057            </ul>
1058         </div>
1059         <div id="changes.since.03">
1060            <h2 id="rfc.section.B.5"><a href="#rfc.section.B.5">B.5</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></h2>
1061         </div>
1062         <div id="changes.since.04">
1063            <h2 id="rfc.section.B.6"><a href="#rfc.section.B.6">B.6</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></h2>
1064            <p id="rfc.section.B.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;):
1065            </p>
1066            <ul>
1067               <li>Use "/" instead of "|" for alternatives.</li>
1068               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
1069               <li>Rewrite ABNFs to spell out whitespace rules, factor out header field value format definitions.</li>
1070            </ul>
1071         </div>
1072         <div id="changes.since.05">
1073            <h2 id="rfc.section.B.7"><a href="#rfc.section.B.7">B.7</a>&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></h2>
1074            <p id="rfc.section.B.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;):
1075            </p>
1076            <ul>
1077               <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
1078            </ul>
1079         </div>
1080         <div id="changes.since.06">
1081            <h2 id="rfc.section.B.8"><a href="#rfc.section.B.8">B.8</a>&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></h2>
1082            <p id="rfc.section.B.8.p.1">None.</p>
1083         </div>
1084         <div id="changes.since.07">
1085            <h2 id="rfc.section.B.9"><a href="#rfc.section.B.9">B.9</a>&nbsp;<a href="#changes.since.07">Since draft-ietf-httpbis-p7-auth-07</a></h2>
1086            <p id="rfc.section.B.9.p.1">Closed issues: </p>
1087            <ul>
1088               <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"
1089               </li>
1090            </ul>
1091         </div>
1092         <div id="changes.since.08">
1093            <h2 id="rfc.section.B.10"><a href="#rfc.section.B.10">B.10</a>&nbsp;<a href="#changes.since.08">Since draft-ietf-httpbis-p7-auth-08</a></h2>
1094            <p id="rfc.section.B.10.p.1">No significant changes.</p>
1095         </div>
1096         <div id="changes.since.09">
1097            <h2 id="rfc.section.B.11"><a href="#rfc.section.B.11">B.11</a>&nbsp;<a href="#changes.since.09">Since draft-ietf-httpbis-p7-auth-09</a></h2>
1098            <p id="rfc.section.B.11.p.1">Partly resolved issues: </p>
1099            <ul>
1100               <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"
1101               </li>
1102            </ul>
1103         </div>
1104         <div id="changes.since.10">
1105            <h2 id="rfc.section.B.12"><a href="#rfc.section.B.12">B.12</a>&nbsp;<a href="#changes.since.10">Since draft-ietf-httpbis-p7-auth-10</a></h2>
1106            <p id="rfc.section.B.12.p.1">None yet.</p>
1107         </div>
1108         <div id="changes.since.11">
1109            <h2 id="rfc.section.B.13"><a href="#rfc.section.B.13">B.13</a>&nbsp;<a href="#changes.since.11">Since draft-ietf-httpbis-p7-auth-11</a></h2>
1110            <p id="rfc.section.B.13.p.1">Closed issues: </p>
1111            <ul>
1112               <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"
1113               </li>
1114               <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"
1115               </li>
1116               <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"
1117               </li>
1118            </ul>
1119            <p id="rfc.section.B.13.p.2">Partly resolved issues: </p>
1120            <ul>
1121               <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"
1122               </li>
1123            </ul>
1124         </div>
1125      </div>
[52]1126      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
[998]1127      <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</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>
[52]1128      </p>
1129      <div class="print2col">
1130         <ul class="ind">
[2726]1131            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
1132                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>3.1</b></a>, <a href="#rfc.xref.status.401.1">5.2</a></li>
1133                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.2"><b>3.2</b></a>, <a href="#rfc.xref.status.407.1">5.2</a></li>
[52]1134               </ul>
1135            </li>
[2726]1136            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
1137                  <li><tt>auth-param</tt>&nbsp;&nbsp;<a href="#rfc.iref.a.2"><b>2</b></a></li>
1138                  <li><tt>auth-scheme</tt>&nbsp;&nbsp;<a href="#rfc.iref.a.1"><b>2</b></a></li>
1139                  <li>Authorization header&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">2</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>
[52]1140               </ul>
1141            </li>
[2726]1142            <li><a id="rfc.index.C" href="#rfc.index.C"><b>C</b></a><ul>
1143                  <li><tt>challenge</tt>&nbsp;&nbsp;<a href="#rfc.iref.c.1"><b>2</b></a></li>
1144                  <li><tt>credentials</tt>&nbsp;&nbsp;<a href="#rfc.iref.c.2"><b>2</b></a></li>
[998]1145               </ul>
1146            </li>
[2726]1147            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
1148                  <li><tt>Grammar</tt>&nbsp;&nbsp;
1149                     <ul>
1150                        <li><tt>Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>4.1</b></a></li>
1151                        <li><tt>Authorization-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>4.1</b></a></li>
1152                        <li><tt>Proxy-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>4.2</b></a></li>
1153                        <li><tt>Proxy-Authenticate-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>4.2</b></a></li>
1154                        <li><tt>Proxy-Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>4.3</b></a></li>
1155                        <li><tt>Proxy-Authorization-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>4.3</b></a></li>
1156                        <li><tt>WWW-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>4.4</b></a></li>
1157                        <li><tt>WWW-Authenticate-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>4.4</b></a></li>
[52]1158                     </ul>
1159                  </li>
1160               </ul>
1161            </li>
[2726]1162            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
1163                  <li>Headers&nbsp;&nbsp;
1164                     <ul>
1165                        <li>Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">2</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>
1166                        <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>
1167                        <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>
1168                        <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>
[52]1169                     </ul>
1170                  </li>
1171               </ul>
1172            </li>
[2726]1173            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
1174                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a>, <a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a>, <a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.7">2</a>, <a href="#rfc.xref.Part1.8">4.2</a>, <a href="#rfc.xref.Part1.9">4.4</a>, <a href="#Part1"><b>8.1</b></a><ul>
1175                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
1176                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a>, <a href="#rfc.xref.Part1.4">1.2.1</a>, <a href="#rfc.xref.Part1.5">1.2.1</a></li>
1177                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.6">2</a>, <a href="#rfc.xref.Part1.8">4.2</a>, <a href="#rfc.xref.Part1.9">4.4</a></li>
1178                        <li><em>Section 7.1.3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.7">2</a></li>
[52]1179                     </ul>
1180                  </li>
[2726]1181                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a>, <a href="#Part6"><b>8.1</b></a><ul>
1182                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a></li>
[205]1183                     </ul>
1184                  </li>
[2726]1185                  <li>Proxy-Authenticate header&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a href="#rfc.iref.p.1"><b>4.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">5.3</a></li>
1186                  <li>Proxy-Authorization header&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a href="#rfc.iref.p.2"><b>4.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">5.3</a></li>
[52]1187               </ul>
1188            </li>
[2726]1189            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
1190                  <li><tt>realm</tt>&nbsp;&nbsp;<a href="#rfc.iref.r.1"><b>2</b></a></li>
1191                  <li><tt>realm-value</tt>&nbsp;&nbsp;<a href="#rfc.iref.r.2"><b>2</b></a></li>
1192                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li>
1193                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">7</a>, <a href="#RFC2616"><b>8.2</b></a>, <a href="#rfc.xref.RFC2616.3">B.1</a></li>
1194                  <li><em>RFC2617</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2617.1">1</a>, <a href="#rfc.xref.RFC2617.2">1</a>, <a href="#RFC2617"><b>8.2</b></a></li>
1195                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">5.3</a>, <a href="#RFC3864"><b>8.2</b></a></li>
1196                  <li><em>RFC5226</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a>, <a href="#RFC5226"><b>8.2</b></a><ul>
1197                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5226.1">2.1</a></li>
[1026]1198                     </ul>
1199                  </li>
[2726]1200                  <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>
1201                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
[425]1202                     </ul>
1203                  </li>
[52]1204               </ul>
1205            </li>
[2726]1206            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
1207                  <li>Status Codes&nbsp;&nbsp;
1208                     <ul>
1209                        <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>
1210                        <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>
[52]1211                     </ul>
1212                  </li>
1213               </ul>
1214            </li>
[2726]1215            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
1216                  <li>WWW-Authenticate header&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>
[52]1217               </ul>
1218            </li>
1219         </ul>
1220      </div>
[2726]1221      <div class="avoidbreak">
1222         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
1223         <p><b>Roy T. Fielding</b>
1224            (editor)
1225            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><br>Email: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
1226         <p><b>Jim Gettys</b><br>Alcatel-Lucent Bell Labs<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>Email: <a href="mailto:jg@freedesktop.org">jg@freedesktop.org</a><br>URI: <a href="http://gettys.wordpress.com/">http://gettys.wordpress.com/</a></p>
1227         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>Email: <a href="mailto:JeffMogul@acm.org">JeffMogul@acm.org</a></p>
1228         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>Email: <a href="mailto:henrikn@microsoft.com">henrikn@microsoft.com</a></p>
1229         <p><b>Larry Masinter</b><br>Adobe Systems, Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>Email: <a href="mailto:LMM@acm.org">LMM@acm.org</a><br>URI: <a href="http://larry.masinter.net/">http://larry.masinter.net/</a></p>
1230         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>Email: <a href="mailto:paulle@microsoft.com">paulle@microsoft.com</a></p>
1231         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>Email: <a href="mailto:timbl@w3.org">timbl@w3.org</a><br>URI: <a href="http://www.w3.org/People/Berners-Lee/">http://www.w3.org/People/Berners-Lee/</a></p>
1232         <p><b>Yves Lafon</b>
1233            (editor)
1234            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>Email: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
1235         <p><b>Julian F. Reschke</b>
1236            (editor)
1237            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><br>Email: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
1238      </div>
[52]1239   </body>
1240</html>
Note: See TracBrowser for help on using the repository browser.