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

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

Source reformat, update Changes section (see #232 and [1032])

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