source: draft-ietf-httpbis/07/p7-auth.html @ 2082

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

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

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 66.5 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}
32dd {
33  margin-right: 2em;
34}
35dl {
36  margin-left: 2em;
37}
38
39ul.empty {
40  list-style-type: none;
41}
42ul.empty li {
43  margin-top: .5em;
44}
45dl p {
46  margin-left: 0em;
47}
48dt {
49  margin-top: .5em;
50}
51h1 {
52  font-size: 14pt;
53  line-height: 21pt;
54  page-break-after: avoid;
55}
56h1.np {
57  page-break-before: always;
58}
59h1 a {
60  color: #333333;
61}
62h2 {
63  font-size: 12pt;
64  line-height: 15pt;
65  page-break-after: avoid;
66}
67h3, h4, h5, h6 {
68  font-size: 10pt;
69  page-break-after: avoid;
70}
71h2 a, h3 a, h4 a, h5 a, h6 a {
72  color: black;
73}
74img {
75  margin-left: 3em;
76}
77li {
78  margin-left: 2em;
79  margin-right: 2em;
80}
81ol {
82  margin-left: 2em;
83  margin-right: 2em;
84}
85ol p {
86  margin-left: 0em;
87}
88p {
89  margin-left: 2em;
90  margin-right: 2em;
91}
92pre {
93  margin-left: 3em;
94  background-color: lightyellow;
95  padding: .25em;
96}
97pre.text2 {
98  border-style: dotted;
99  border-width: 1px;
100  background-color: #f0f0f0;
101  width: 69em;
102}
103pre.inline {
104  background-color: white;
105  padding: 0em;
106}
107pre.text {
108  border-style: dotted;
109  border-width: 1px;
110  background-color: #f8f8f8;
111  width: 69em;
112}
113pre.drawing {
114  border-style: solid;
115  border-width: 1px;
116  background-color: #f8f8f8;
117  padding: 2em;
118}
119table {
120  margin-left: 2em;
121}
122table.tt {
123  vertical-align: top;
124}
125table.full {
126  border-style: outset;
127  border-width: 1px;
128}
129table.headers {
130  border-style: outset;
131  border-width: 1px;
132}
133table.tt td {
134  vertical-align: top;
135}
136table.full td {
137  border-style: inset;
138  border-width: 1px;
139}
140table.tt th {
141  vertical-align: top;
142}
143table.full th {
144  border-style: inset;
145  border-width: 1px;
146}
147table.headers th {
148  border-style: none none inset none;
149  border-width: 1px;
150}
151table.left {
152  margin-right: auto;
153}
154table.right {
155  margin-left: auto;
156}
157table.center {
158  margin-left: auto;
159  margin-right: auto;
160}
161caption {
162  caption-side: bottom;
163  font-weight: bold;
164  font-size: 9pt;
165  margin-top: .5em;
166}
167
168table.header {
169  border-spacing: 1px;
170  width: 95%;
171  font-size: 10pt;
172  color: white;
173}
174td.top {
175  vertical-align: top;
176}
177td.topnowrap {
178  vertical-align: top;
179  white-space: nowrap; 
180}
181table.header td {
182  background-color: gray;
183  width: 50%;
184}
185table.header a {
186  color: white;
187}
188td.reference {
189  vertical-align: top;
190  white-space: nowrap;
191  padding-right: 1em;
192}
193thead {
194  display:table-header-group;
195}
196ul.toc, ul.toc ul {
197  list-style: none;
198  margin-left: 1.5em;
199  margin-right: 0em;
200  padding-left: 0em;
201}
202ul.toc li {
203  line-height: 150%;
204  font-weight: bold;
205  font-size: 10pt;
206  margin-left: 0em;
207  margin-right: 0em;
208}
209ul.toc li li {
210  line-height: normal;
211  font-weight: normal;
212  font-size: 9pt;
213  margin-left: 0em;
214  margin-right: 0em;
215}
216li.excluded {
217  font-size: 0pt;
218}
219ul p {
220  margin-left: 0em;
221}
222ul.ind, ul.ind ul {
223  list-style: none;
224  margin-left: 1.5em;
225  margin-right: 0em;
226  padding-left: 0em;
227  page-break-before: avoid;
228}
229ul.ind li {
230  font-weight: bold;
231  line-height: 200%;
232  margin-left: 0em;
233  margin-right: 0em;
234}
235ul.ind li li {
236  font-weight: normal;
237  line-height: 150%;
238  margin-left: 0em;
239  margin-right: 0em;
240}
241.avoidbreak {
242  page-break-inside: avoid;
243}
244.bcp14 {
245  font-style: normal;
246  text-transform: lowercase;
247  font-variant: small-caps;
248}
249.comment {
250  background-color: yellow;
251}
252.center {
253  text-align: center;
254}
255.error {
256  color: red;
257  font-style: italic;
258  font-weight: bold;
259}
260.figure {
261  font-weight: bold;
262  text-align: center;
263  font-size: 9pt;
264}
265.filename {
266  color: #333333;
267  font-weight: bold;
268  font-size: 12pt;
269  line-height: 21pt;
270  text-align: center;
271}
272.fn {
273  font-weight: bold;
274}
275.hidden {
276  display: none;
277}
278.left {
279  text-align: left;
280}
281.right {
282  text-align: right;
283}
284.title {
285  color: #990000;
286  font-size: 18pt;
287  line-height: 18pt;
288  font-weight: bold;
289  text-align: center;
290  margin-top: 36pt;
291}
292.vcardline {
293  display: block;
294}
295.warning {
296  font-size: 14pt;
297  background-color: yellow;
298}
299
300
301@media print {
302  .noprint {
303    display: none;
304  }
305 
306  a {
307    color: black;
308    text-decoration: none;
309  }
310
311  table.header {
312    width: 90%;
313  }
314
315  td.header {
316    width: 50%;
317    color: black;
318    background-color: white;
319    vertical-align: top;
320    font-size: 12pt;
321  }
322
323  ul.toc a::after {
324    content: leader('.') target-counter(attr(href), page);
325  }
326 
327  ul.ind li li a {
328    content: target-counter(attr(href), page);
329  }
330 
331  .print2col {
332    column-count: 2;
333    -moz-column-count: 2;
334    column-fill: auto;
335  }
336}
337
338@page {
339  @top-left {
340       content: "Internet-Draft"; 
341  } 
342  @top-right {
343       content: "July 2009"; 
344  } 
345  @top-center {
346       content: "HTTP/1.1, Part 7"; 
347  } 
348  @bottom-left {
349       content: "Fielding, et al."; 
350  } 
351  @bottom-center {
352       content: "Standards Track"; 
353  } 
354  @bottom-right {
355       content: "[Page " counter(page) "]"; 
356  } 
357}
358
359@page:first { 
360    @top-left {
361      content: normal;
362    }
363    @top-right {
364      content: normal;
365    }
366    @top-center {
367      content: normal;
368    }
369}
370</style><link rel="Contents" href="#rfc.toc">
371      <link rel="Author" href="#rfc.authors">
372      <link rel="Copyright" href="#rfc.copyrightnotice">
373      <link rel="Index" href="#rfc.index">
374      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
375      <link rel="Chapter" title="2 Status Code Definitions" href="#rfc.section.2">
376      <link rel="Chapter" title="3 Header Field Definitions" href="#rfc.section.3">
377      <link rel="Chapter" title="4 IANA Considerations" href="#rfc.section.4">
378      <link rel="Chapter" title="5 Security Considerations" href="#rfc.section.5">
379      <link rel="Chapter" title="6 Acknowledgments" href="#rfc.section.6">
380      <link rel="Chapter" href="#rfc.section.7" title="7 References">
381      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
382      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
383      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
384      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.537, 2010-12-30 14:21:59, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
385      <link rel="schema.dct" href="http://purl.org/dc/terms/">
386      <meta name="dct.creator" content="Fielding, R.">
387      <meta name="dct.creator" content="Gettys, J.">
388      <meta name="dct.creator" content="Mogul, J.">
389      <meta name="dct.creator" content="Frystyk, H.">
390      <meta name="dct.creator" content="Masinter, L.">
391      <meta name="dct.creator" content="Leach, P.">
392      <meta name="dct.creator" content="Berners-Lee, T.">
393      <meta name="dct.creator" content="Lafon, Y.">
394      <meta name="dct.creator" content="Reschke, J. F.">
395      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-07">
396      <meta name="dct.issued" scheme="ISO8601" content="2009-07-13">
397      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
398      <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.">
399      <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.">
400   </head>
401   <body>
402      <table class="header">
403         <tbody>
404            <tr>
405               <td class="left">HTTPbis Working Group</td>
406               <td class="right">R. Fielding, Editor</td>
407            </tr>
408            <tr>
409               <td class="left">Internet-Draft</td>
410               <td class="right">Day Software</td>
411            </tr>
412            <tr>
413               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
414               </td>
415               <td class="right">J. Gettys</td>
416            </tr>
417            <tr>
418               <td class="left">Updates: <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)
419               </td>
420               <td class="right">One Laptop per Child</td>
421            </tr>
422            <tr>
423               <td class="left">Intended status: Standards Track</td>
424               <td class="right">J. Mogul</td>
425            </tr>
426            <tr>
427               <td class="left">Expires: January 14, 2010</td>
428               <td class="right">HP</td>
429            </tr>
430            <tr>
431               <td class="left"></td>
432               <td class="right">H. Frystyk</td>
433            </tr>
434            <tr>
435               <td class="left"></td>
436               <td class="right">Microsoft</td>
437            </tr>
438            <tr>
439               <td class="left"></td>
440               <td class="right">L. Masinter</td>
441            </tr>
442            <tr>
443               <td class="left"></td>
444               <td class="right">Adobe Systems</td>
445            </tr>
446            <tr>
447               <td class="left"></td>
448               <td class="right">P. Leach</td>
449            </tr>
450            <tr>
451               <td class="left"></td>
452               <td class="right">Microsoft</td>
453            </tr>
454            <tr>
455               <td class="left"></td>
456               <td class="right">T. Berners-Lee</td>
457            </tr>
458            <tr>
459               <td class="left"></td>
460               <td class="right">W3C/MIT</td>
461            </tr>
462            <tr>
463               <td class="left"></td>
464               <td class="right">Y. Lafon, Editor</td>
465            </tr>
466            <tr>
467               <td class="left"></td>
468               <td class="right">W3C</td>
469            </tr>
470            <tr>
471               <td class="left"></td>
472               <td class="right">J. Reschke, Editor</td>
473            </tr>
474            <tr>
475               <td class="left"></td>
476               <td class="right">greenbytes</td>
477            </tr>
478            <tr>
479               <td class="left"></td>
480               <td class="right">July 13, 2009</td>
481            </tr>
482         </tbody>
483      </table>
484      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-07</span></p>
485      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
486      <p>This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. This document may contain
487         material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s)
488         controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of
489         such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the
490         copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of
491         it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it
492         into languages other than English.
493      </p>
494      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
495         that other groups may also distribute working documents as Internet-Drafts.
496      </p>
497      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
498         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
499         in progress”.
500      </p>
501      <p>The list of current Internet-Drafts can be accessed at <a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>.
502      </p>
503      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>.
504      </p>
505      <p>This Internet-Draft will expire on January 14, 2010.</p>
506      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
507      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
508      <p>This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents in effect on the date
509         of publication of this document (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>). Please review these documents carefully, as they describe your rights and restrictions with respect to this document.
510      </p>
511      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
512      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
513         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
514         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
515         7 defines HTTP Authentication.
516      </p> 
517      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
518      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
519         list is at &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/report/11">http://tools.ietf.org/wg/httpbis/trac/report/11</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;.
520      </p> 
521      <p>The changes in this draft are summarized in <a href="#changes.since.06" title="Since draft-ietf-httpbis-p7-auth-06">Appendix&nbsp;C.8</a>.
522      </p> 
523      <hr class="noprint">
524      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
525      <ul class="toc">
526         <li>1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
527               <li>1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
528               <li>1.2&nbsp;&nbsp;&nbsp;<a href="#notation">Syntax Notation</a><ul>
529                     <li>1.2.1&nbsp;&nbsp;&nbsp;<a href="#core.rules">Core Rules</a></li>
530                     <li>1.2.2&nbsp;&nbsp;&nbsp;<a href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></li>
531                  </ul>
532               </li>
533            </ul>
534         </li>
535         <li>2.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.2">Status Code Definitions</a><ul>
536               <li>2.1&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
537               <li>2.2&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
538            </ul>
539         </li>
540         <li>3.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
541               <li>3.1&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
542               <li>3.2&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
543               <li>3.3&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
544               <li>3.4&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
545            </ul>
546         </li>
547         <li>4.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
548               <li>4.1&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
549            </ul>
550         </li>
551         <li>5.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
552               <li>5.1&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
553            </ul>
554         </li>
555         <li>6.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
556         <li>7.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
557               <li>7.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
558               <li>7.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
559            </ul>
560         </li>
561         <li><a href="#rfc.authors">Authors' Addresses</a></li>
562         <li>A.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
563               <li>A.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
564            </ul>
565         </li>
566         <li>B.&nbsp;&nbsp;&nbsp;<a href="#collected.abnf">Collected ABNF</a></li>
567         <li>C.&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
568               <li>C.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.1">Since RFC2616</a></li>
569               <li>C.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
570               <li>C.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.C.3">Since draft-ietf-httpbis-p7-auth-01</a></li>
571               <li>C.4&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></li>
572               <li>C.5&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></li>
573               <li>C.6&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></li>
574               <li>C.7&nbsp;&nbsp;&nbsp;<a href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></li>
575               <li>C.8&nbsp;&nbsp;&nbsp;<a href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></li>
576            </ul>
577         </li>
578         <li><a href="#rfc.index">Index</a></li>
579      </ul>
580      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
581      <p id="rfc.section.1.p.1">This document defines HTTP/1.1 access control and authentication. Right now it includes the extracted relevant sections of <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">RFC 2616</cite> with only minor changes. The intention is to move the general framework for HTTP authentication here, as currently specified
582         in <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, and allow the individual authentication mechanisms to be defined elsewhere. This introduction will be rewritten when that
583         occurs.
584      </p>
585      <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
586         provide authentication information. The general framework for access authentication, and the specification of "basic" and
587         "digest" authentication, are specified in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.2"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. This specification adopts the definitions of "challenge" and "credentials" from that specification.
588      </p>
589      <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>
590      <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"
591         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>.
592      </p>
593      <p id="rfc.section.1.1.p.2">An implementation is not compliant if it fails to satisfy one or more of the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level requirements for the protocols it implements. An implementation that satisfies all the <em class="bcp14">MUST</em> or <em class="bcp14">REQUIRED</em> level and all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "unconditionally compliant"; one that satisfies all the <em class="bcp14">MUST</em> level requirements but not all the <em class="bcp14">SHOULD</em> level requirements for its protocols is said to be "conditionally compliant."
594      </p>
595      <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>
596      <p id="rfc.section.1.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation" title="Syntax Notation">Section 1.2</a> of <a href="#Part1" id="rfc.xref.Part1.1"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a> (which extends the syntax defined in <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a> with a list rule). <a href="#collected.abnf" title="Collected ABNF">Appendix&nbsp;B</a> shows the collected ABNF, with the list rule expanded.
597      </p>
598      <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
599         (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible USASCII character),
600         and WSP (whitespace).
601      </p>
602      <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>
603      <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>:
604      </p>
605      <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#core.rules" class="smpl">OWS</a>         = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.3"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 1.2.2</a>&gt;
606</pre><h3 id="rfc.section.1.2.2"><a href="#rfc.section.1.2.2">1.2.2</a>&nbsp;<a id="abnf.dependencies" href="#abnf.dependencies">ABNF Rules defined in other Parts of the Specification</a></h3>
607      <p id="rfc.section.1.2.2.p.1">  The ABNF rules below are defined in other specifications:</p>
608      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.1"></span><span id="rfc.iref.g.2"></span>  <a href="#abnf.dependencies" class="smpl">challenge</a>   = &lt;challenge, defined in <a href="#RFC2617" id="rfc.xref.RFC2617.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, <a href="http://tools.ietf.org/html/rfc2617#section-1.2">Section 1.2</a>&gt;
609  <a href="#abnf.dependencies" class="smpl">credentials</a> = &lt;credentials, defined in <a href="#RFC2617" id="rfc.xref.RFC2617.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>, <a href="http://tools.ietf.org/html/rfc2617#section-1.2">Section 1.2</a>&gt;
610</pre><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;Status Code Definitions
611      </h1>
612      <div id="rfc.iref.2"></div>
613      <div id="rfc.iref.s.1"></div>
614      <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h2>
615      <p id="rfc.section.2.1.p.1">The request requires user authentication. The response <em class="bcp14">MUST</em> include a WWW-Authenticate header field (<a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.1" title="WWW-Authenticate">Section&nbsp;3.4</a>) containing a challenge applicable to the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Authorization header field (<a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section&nbsp;3.1</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
616         refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
617         already attempted authentication at least once, then the user <em class="bcp14">SHOULD</em> be presented the entity that was given in the response, since that entity might include relevant diagnostic information. HTTP
618         access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.5"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
619      </p>
620      <div id="rfc.iref.3"></div>
621      <div id="rfc.iref.s.2"></div>
622      <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h2>
623      <p id="rfc.section.2.2.p.1">This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. The
624         proxy <em class="bcp14">MUST</em> return a Proxy-Authenticate header field (<a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.1" title="Proxy-Authenticate">Section&nbsp;3.2</a>) containing a challenge applicable to the proxy for the requested resource. The client <em class="bcp14">MAY</em> repeat the request with a suitable Proxy-Authorization header field (<a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.1" title="Proxy-Authorization">Section&nbsp;3.3</a>). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.6"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>.
625      </p>
626      <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
627      <p id="rfc.section.3.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
628      <div id="rfc.iref.a.1"></div>
629      <div id="rfc.iref.h.1"></div>
630      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="header.authorization" href="#header.authorization">Authorization</a></h2>
631      <p id="rfc.section.3.1.p.1">A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does
632         so by including an Authorization request-header field with the request. The field "Authorization" consists of credentials
633         containing the authentication information of the user agent for the realm of the resource being requested.
634      </p>
635      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span>  <a href="#header.authorization" class="smpl">Authorization</a>   = "Authorization" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.authorization" class="smpl">Authorization-v</a>
636  <a href="#header.authorization" class="smpl">Authorization-v</a> = <a href="#abnf.dependencies" class="smpl">credentials</a>
637</pre><p id="rfc.section.3.1.p.3">HTTP access authentication is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.7"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. If a request is authenticated and a realm specified, the same credentials <em class="bcp14">SHOULD</em> be valid for all other requests within this realm (assuming that the authentication scheme itself does not require otherwise,
638         such as credentials that vary according to a challenge value or using synchronized clocks).
639      </p>
640      <p id="rfc.section.3.1.p.4">When a shared cache (see <a href="p6-cache.html#shared.and.non-shared.caches">Section 1.2</a> of <a href="#Part6" id="rfc.xref.Part6.1"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>) receives a request containing an Authorization field, it <em class="bcp14">MUST NOT</em> return the corresponding response as a reply to any other request, unless one of the following specific exceptions holds:
641      </p>
642      <p id="rfc.section.3.1.p.5"> </p>
643      <ol>
644         <li>If the response includes the "s-maxage" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But (if the specified maximum age has passed) a proxy cache <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
645            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.
646         </li>
647         <li>If the response includes the "must-revalidate" cache-control directive, the cache <em class="bcp14">MAY</em> use that response in replying to a subsequent request. But if the response is stale, all caches <em class="bcp14">MUST</em> first revalidate it with the origin server, using the request-headers from the new request to allow the origin server to authenticate
648            the new request.
649         </li>
650         <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
651         </li>
652      </ol>
653      <div id="rfc.iref.p.1"></div>
654      <div id="rfc.iref.h.2"></div>
655      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="header.proxy-authenticate" href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
656      <p id="rfc.section.3.2.p.1">The response-header field "Proxy-Authenticate" <em class="bcp14">MUST</em> be included as part of a 407 (Proxy Authentication Required) response. The field value consists of a challenge that indicates
657         the authentication scheme and parameters applicable to the proxy for this request-target.
658      </p>
659      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span>  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a>   = "Proxy-Authenticate" ":" <a href="#core.rules" class="smpl">OWS</a>
660                         <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a>
661  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a> = 1#<a href="#abnf.dependencies" class="smpl">challenge</a>
662</pre><p id="rfc.section.3.2.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.8"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to the current connection and <em class="bcp14">SHOULD NOT</em> be passed on to downstream clients. However, an intermediate proxy might need to obtain its own credentials by requesting
663         them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
664         header field.
665      </p>
666      <div id="rfc.iref.p.2"></div>
667      <div id="rfc.iref.h.3"></div>
668      <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a>&nbsp;<a id="header.proxy-authorization" href="#header.proxy-authorization">Proxy-Authorization</a></h2>
669      <p id="rfc.section.3.3.p.1">The request-header field "Proxy-Authorization" allows the client to identify itself (or its user) to a proxy which requires
670         authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the
671         user agent for the proxy and/or realm of the resource being requested.
672      </p>
673      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span>  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a>   = "Proxy-Authorization" ":" <a href="#core.rules" class="smpl">OWS</a>
674                          <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a>
675  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a> = <a href="#abnf.dependencies" class="smpl">credentials</a>
676</pre><p id="rfc.section.3.3.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.9"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. Unlike Authorization, the Proxy-Authorization header field applies only to the next outbound proxy that demanded authentication
677         using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
678         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
679         authenticate a given request.
680      </p>
681      <div id="rfc.iref.w.1"></div>
682      <div id="rfc.iref.h.4"></div>
683      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="header.www-authenticate" href="#header.www-authenticate">WWW-Authenticate</a></h2>
684      <p id="rfc.section.3.4.p.1">The WWW-Authenticate response-header field <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages. The field value consists of at least one challenge that indicates the
685         authentication scheme(s) and parameters applicable to the request-target.
686      </p>
687      <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span>  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a>   = "WWW-Authenticate" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a>
688  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a> = 1#<a href="#abnf.dependencies" class="smpl">challenge</a>
689</pre><p id="rfc.section.3.4.p.3">The HTTP access authentication process is described in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.10"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[RFC2617]</cite></a>. User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one
690         challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
691         comma-separated list of authentication parameters.
692      </p>
693      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
694      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="message.header.registration" href="#message.header.registration">Message Header Registration</a></h2>
695      <p id="rfc.section.4.1.p.1">The Message Header Registry located at &lt;<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>&gt; should be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):
696      </p>
697      <div id="rfc.table.1">
698         <div id="iana.header.registration.table"></div>
699         <table class="tt full left" cellpadding="3" cellspacing="0">
700            <thead>
701               <tr>
702                  <th>Header Field Name</th>
703                  <th>Protocol</th>
704                  <th>Status</th>
705                  <th>Reference</th>
706               </tr>
707            </thead>
708            <tbody>
709               <tr>
710                  <td class="left">Authorization</td>
711                  <td class="left">http</td>
712                  <td class="left">standard</td>
713                  <td class="left"> <a href="#header.authorization" id="rfc.xref.header.authorization.2" title="Authorization">Section&nbsp;3.1</a> 
714                  </td>
715               </tr>
716               <tr>
717                  <td class="left">Proxy-Authenticate</td>
718                  <td class="left">http</td>
719                  <td class="left">standard</td>
720                  <td class="left"> <a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;3.2</a> 
721                  </td>
722               </tr>
723               <tr>
724                  <td class="left">Proxy-Authorization</td>
725                  <td class="left">http</td>
726                  <td class="left">standard</td>
727                  <td class="left"> <a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;3.3</a> 
728                  </td>
729               </tr>
730               <tr>
731                  <td class="left">WWW-Authenticate</td>
732                  <td class="left">http</td>
733                  <td class="left">standard</td>
734                  <td class="left"> <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section&nbsp;3.4</a> 
735                  </td>
736               </tr>
737            </tbody>
738         </table>
739      </div>
740      <p id="rfc.section.4.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
741      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
742      <p id="rfc.section.5.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1
743         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
744         make some suggestions for reducing security risks.
745      </p>
746      <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a id="auth.credentials.and.idle.clients" href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
747      <p id="rfc.section.5.1.p.1">Existing HTTP clients and user agents typically retain authentication information indefinitely. HTTP/1.1 does not provide
748         a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
749         extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
750         but are not limited to:
751      </p>
752      <ul>
753         <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
754            the user for credentials.
755         </li>
756         <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
757            the server side of the application `knows' that there is no further reason for the client to retain the credentials.
758         </li>
759      </ul>
760      <p id="rfc.section.5.1.p.2">This is currently under separate study. There are a number of work-arounds to parts of this problem, and we encourage the
761         use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
762         in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
763         for discarding cached credentials under user control.
764      </p>
765      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
766      <p id="rfc.section.6.p.1"> <span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TBD.]</span> 
767      </p>
768      <h1 id="rfc.references"><a id="rfc.section.7" href="#rfc.section.7">7.</a> References
769      </h1>
770      <h2 id="rfc.references.1"><a href="#rfc.section.7.1" id="rfc.section.7.1">7.1</a> Normative References
771      </h2>
772      <table>         
773         <tr>
774            <td class="reference"><b id="Part1">[Part1]</b></td>
775            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-07">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-07 (work in progress), July&nbsp;2009.
776            </td>
777         </tr>
778         <tr>
779            <td class="reference"><b id="Part6">[Part6]</b></td>
780            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">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-07">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-07 (work in progress), July&nbsp;2009.
781            </td>
782         </tr>
783         <tr>
784            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
785            <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.
786            </td>
787         </tr>
788         <tr>
789            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
790            <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.
791            </td>
792         </tr>
793         <tr>
794            <td class="reference"><b id="RFC5234">[RFC5234]</b></td>
795            <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.
796            </td>
797         </tr>
798      </table>
799      <h2 id="rfc.references.2"><a href="#rfc.section.7.2" id="rfc.section.7.2">7.2</a> Informative References
800      </h2>
801      <table>   
802         <tr>
803            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
804            <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.
805            </td>
806         </tr>
807         <tr>
808            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
809            <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.
810            </td>
811         </tr>
812      </table>
813      <div class="avoidbreak">
814         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
815         <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
816               (editor)
817               <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>
818         <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">One Laptop per Child</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@laptop.org"><span class="email">jg@laptop.org</span></a></span><span class="vcardline">URI: <a href="http://www.laptop.org/" class="url">http://www.laptop.org/</a></span></address>
819         <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>
820         <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>
821         <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>
822         <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>
823         <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>
824         <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
825               (editor)
826               <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>
827         <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
828               (editor)
829               <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>
830      </div>
831      <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
832      <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
833      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
834      <div id="rfc.figure.u.7"></div> <pre class="inline"><a href="#header.authorization" class="smpl">Authorization</a> = "Authorization:" OWS Authorization-v
835<a href="#header.authorization" class="smpl">Authorization-v</a> = credentials
836
837<a href="#core.rules" class="smpl">OWS</a> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
838
839<a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = "Proxy-Authenticate:" OWS Proxy-Authenticate-v
840<a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a> = *( "," OWS ) challenge *( OWS "," [ OWS
841 challenge ] )
842<a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> = "Proxy-Authorization:" OWS
843 Proxy-Authorization-v
844<a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a> = credentials
845
846<a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> = "WWW-Authenticate:" OWS WWW-Authenticate-v
847<a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a> = *( "," OWS ) challenge *( OWS "," [ OWS
848 challenge ] )
849
850<a href="#abnf.dependencies" class="smpl">challenge</a> = &lt;challenge, defined in [RFC2617], Section 1.2&gt;
851<a href="#abnf.dependencies" class="smpl">credentials</a> = &lt;credentials, defined in [RFC2617], Section 1.2&gt;
852
853
854</pre> <div id="rfc.figure.u.8"></div>
855      <p>ABNF diagnostics:</p><pre class="inline">; Authorization defined but not used
856; Proxy-Authenticate defined but not used
857; Proxy-Authorization defined but not used
858; WWW-Authenticate defined but not used
859</pre><h1 id="rfc.section.C"><a href="#rfc.section.C">C.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
860      <h2 id="rfc.section.C.1"><a href="#rfc.section.C.1">C.1</a>&nbsp;Since RFC2616
861      </h2>
862      <p id="rfc.section.C.1.p.1">Extracted relevant partitions from <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>.
863      </p>
864      <h2 id="rfc.section.C.2"><a href="#rfc.section.C.2">C.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
865      </h2>
866      <p id="rfc.section.C.2.p.1">Closed issues: </p>
867      <ul>
868         <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"
869         </li>
870      </ul>
871      <h2 id="rfc.section.C.3"><a href="#rfc.section.C.3">C.3</a>&nbsp;Since draft-ietf-httpbis-p7-auth-01
872      </h2>
873      <p id="rfc.section.C.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
874      </p>
875      <ul>
876         <li>Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.</li>
877         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
878      </ul>
879      <h2 id="rfc.section.C.4"><a href="#rfc.section.C.4">C.4</a>&nbsp;<a id="changes.since.02" href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></h2>
880      <p id="rfc.section.C.4.p.1">Ongoing work on IANA Message Header Registration (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/40">http://tools.ietf.org/wg/httpbis/trac/ticket/40</a>&gt;):
881      </p>
882      <ul>
883         <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
884      </ul>
885      <h2 id="rfc.section.C.5"><a href="#rfc.section.C.5">C.5</a>&nbsp;<a id="changes.since.03" href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></h2>
886      <h2 id="rfc.section.C.6"><a href="#rfc.section.C.6">C.6</a>&nbsp;<a id="changes.since.04" href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></h2>
887      <p id="rfc.section.C.6.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
888      </p>
889      <ul>
890         <li>Use "/" instead of "|" for alternatives.</li>
891         <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
892         <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
893      </ul>
894      <h2 id="rfc.section.C.7"><a href="#rfc.section.C.7">C.7</a>&nbsp;<a id="changes.since.05" href="#changes.since.05">Since draft-ietf-httpbis-p7-auth-05</a></h2>
895      <p id="rfc.section.C.7.p.1">Final work on ABNF conversion (&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
896      </p>
897      <ul>
898         <li>Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.</li>
899      </ul>
900      <h2 id="rfc.section.C.8"><a href="#rfc.section.C.8">C.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p7-auth-06</a></h2>
901      <p id="rfc.section.C.8.p.1">None.</p>
902      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
903      <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.W">W</a> 
904      </p>
905      <div class="print2col">
906         <ul class="ind">
907            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
908                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.2"><b>2.1</b></a></li>
909                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.3"><b>2.2</b></a></li>
910               </ul>
911            </li>
912            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
913                  <li>Authorization header&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">2.1</a>, <a href="#rfc.iref.a.1"><b>3.1</b></a>, <a href="#rfc.xref.header.authorization.2">4.1</a></li>
914               </ul>
915            </li>
916            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
917                  <li><tt>Grammar</tt>&nbsp;&nbsp;
918                     <ul>
919                        <li><tt>Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>3.1</b></a></li>
920                        <li><tt>Authorization-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>3.1</b></a></li>
921                        <li><tt>challenge</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>1.2.2</b></a></li>
922                        <li><tt>credentials</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>1.2.2</b></a></li>
923                        <li><tt>Proxy-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>3.2</b></a></li>
924                        <li><tt>Proxy-Authenticate-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>3.2</b></a></li>
925                        <li><tt>Proxy-Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>3.3</b></a></li>
926                        <li><tt>Proxy-Authorization-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>3.3</b></a></li>
927                        <li><tt>WWW-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>3.4</b></a></li>
928                        <li><tt>WWW-Authenticate-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>3.4</b></a></li>
929                     </ul>
930                  </li>
931               </ul>
932            </li>
933            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
934                  <li>Headers&nbsp;&nbsp;
935                     <ul>
936                        <li>Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">2.1</a>, <a href="#rfc.iref.h.1"><b>3.1</b></a>, <a href="#rfc.xref.header.authorization.2">4.1</a></li>
937                        <li>Proxy-Authenticate&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">2.2</a>, <a href="#rfc.iref.h.2"><b>3.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">4.1</a></li>
938                        <li>Proxy-Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">2.2</a>, <a href="#rfc.iref.h.3"><b>3.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">4.1</a></li>
939                        <li>WWW-Authenticate&nbsp;&nbsp;<a href="#rfc.xref.header.www-authenticate.1">2.1</a>, <a href="#rfc.iref.h.4"><b>3.4</b></a>, <a href="#rfc.xref.header.www-authenticate.2">4.1</a></li>
940                     </ul>
941                  </li>
942               </ul>
943            </li>
944            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
945                  <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="#Part1"><b>7.1</b></a><ul>
946                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">1.2</a></li>
947                        <li><em>Section 1.2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">1.2.1</a>, <a href="#rfc.xref.Part1.3">1.2.1</a></li>
948                     </ul>
949                  </li>
950                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a>, <a href="#Part6"><b>7.1</b></a><ul>
951                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">3.1</a></li>
952                     </ul>
953                  </li>
954                  <li>Proxy-Authenticate header&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">2.2</a>, <a href="#rfc.iref.p.1"><b>3.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">4.1</a></li>
955                  <li>Proxy-Authorization header&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">2.2</a>, <a href="#rfc.iref.p.2"><b>3.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">4.1</a></li>
956               </ul>
957            </li>
958            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
959                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>7.1</b></a></li>
960                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>7.2</b></a>, <a href="#rfc.xref.RFC2616.2">C.1</a></li>
961                  <li><em>RFC2617</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2617.1">1</a>, <a href="#rfc.xref.RFC2617.2">1</a>, <a href="#rfc.xref.RFC2617.3">1.2.2</a>, <a href="#rfc.xref.RFC2617.4">1.2.2</a>, <a href="#rfc.xref.RFC2617.5">2.1</a>, <a href="#rfc.xref.RFC2617.6">2.2</a>, <a href="#rfc.xref.RFC2617.7">3.1</a>, <a href="#rfc.xref.RFC2617.8">3.2</a>, <a href="#rfc.xref.RFC2617.9">3.3</a>, <a href="#rfc.xref.RFC2617.10">3.4</a>, <a href="#RFC2617"><b>7.1</b></a><ul>
962                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2617.3">1.2.2</a>, <a href="#rfc.xref.RFC2617.4">1.2.2</a></li>
963                     </ul>
964                  </li>
965                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">4.1</a>, <a href="#RFC3864"><b>7.2</b></a></li>
966                  <li><em>RFC5234</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.1">1.2</a>, <a href="#rfc.xref.RFC5234.2">1.2</a>, <a href="#RFC5234"><b>7.1</b></a><ul>
967                        <li><em>Appendix B.1</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC5234.2">1.2</a></li>
968                     </ul>
969                  </li>
970               </ul>
971            </li>
972            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
973                  <li>Status Codes&nbsp;&nbsp;
974                     <ul>
975                        <li>401 Unauthorized&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>2.1</b></a></li>
976                        <li>407 Proxy Authentication Required&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>2.2</b></a></li>
977                     </ul>
978                  </li>
979               </ul>
980            </li>
981            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
982                  <li>WWW-Authenticate header&nbsp;&nbsp;<a href="#rfc.xref.header.www-authenticate.1">2.1</a>, <a href="#rfc.iref.w.1"><b>3.4</b></a>, <a href="#rfc.xref.header.www-authenticate.2">4.1</a></li>
983               </ul>
984            </li>
985         </ul>
986      </div>
987   </body>
988</html>
Note: See TracBrowser for help on using the repository browser.