source: draft-ietf-httpbis/05/p7-auth.html

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

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

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 60.7 KB
Line 
1<!DOCTYPE html
2  PUBLIC "-//W3C//DTD HTML 4.01//EN">
3<html lang="en">
4   <head profile="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: cambria, helvetica, arial, sans-serif;
27  font-size: 11pt;
28  margin-right: 2em;
29}
30cite {
31  font-style: normal;
32}
33dl {
34  margin-left: 2em;
35}
36ul.empty {
37  list-style-type: none;
38}
39ul.empty li {
40  margin-top: .5em;
41}
42dl p {
43  margin-left: 0em;
44}
45dt {
46  margin-top: .5em;
47}
48h1 {
49  font-size: 130%;
50  line-height: 21pt;
51  page-break-after: avoid;
52}
53h1.np {
54  page-break-before: always;
55}
56h2 {
57  font-size: 120%;
58  line-height: 15pt;
59  page-break-after: avoid;
60}
61h3 {
62  font-size: 110%;
63  page-break-after: avoid;
64}
65h4, h5, h6 {
66  page-break-after: avoid;
67}
68h1 a, h2 a, h3 a, h4 a, h5 a, h6 a {
69  color: black;
70}
71img {
72  margin-left: 3em;
73}
74li {
75  margin-left: 2em;
76}
77ol {
78  margin-left: 2em;
79}
80ol.la {
81  list-style-type: lower-alpha;
82}
83ol.ua {
84  list-style-type: upper-alpha;
85}
86ol p {
87  margin-left: 0em;
88}
89p {
90  margin-left: 2em;
91}
92pre {
93  margin-left: 3em;
94  background-color: lightyellow;
95  padding: .25em;
96  page-break-inside: avoid;
97}
98pre.text2 {
99  border-style: dotted;
100  border-width: 1px;
101  background-color: #f0f0f0;
102  width: 69em;
103}
104pre.inline {
105  background-color: white;
106  padding: 0em;
107}
108pre.text {
109  border-style: dotted;
110  border-width: 1px;
111  background-color: #f8f8f8;
112  width: 69em;
113}
114pre.drawing {
115  border-style: solid;
116  border-width: 1px;
117  background-color: #f8f8f8;
118  padding: 2em;
119}
120table {
121  margin-left: 2em;
122}
123table.tt {
124  vertical-align: top;
125  border-color: gray;
126}
127table.tt th {
128  border-color: gray;
129}
130table.tt td {
131  border-color: gray;
132}
133table.all {
134  border-style: solid;
135  border-width: 2px;
136}
137table.full {
138  border-style: solid;
139  border-width: 2px;
140}
141table.tt td {
142  vertical-align: top;
143}
144table.all td {
145  border-style: solid;
146  border-width: 1px;
147}
148table.full td {
149  border-style: none solid;
150  border-width: 1px;
151}
152table.tt th {
153  vertical-align: top;
154}
155table.all th {
156  border-style: solid;
157  border-width: 1px;
158}
159table.full th {
160  border-style: solid;
161  border-width: 1px 1px 2px 1px;
162}
163table.headers th {
164  border-style: none none solid none;
165  border-width: 2px;
166}
167table.left {
168  margin-right: auto;
169}
170table.right {
171  margin-left: auto;
172}
173table.center {
174  margin-left: auto;
175  margin-right: auto;
176}
177caption {
178  caption-side: bottom;
179  font-weight: bold;
180  font-size: 10pt;
181  margin-top: .5em;
182}
183
184table.header {
185  border-spacing: 1px;
186  width: 95%;
187  font-size: 11pt;
188  color: white;
189}
190td.top {
191  vertical-align: top;
192}
193td.topnowrap {
194  vertical-align: top;
195  white-space: nowrap;
196}
197table.header td {
198  background-color: gray;
199  width: 50%;
200}
201table.header a {
202  color: white;
203}
204td.reference {
205  vertical-align: top;
206  white-space: nowrap;
207  padding-right: 1em;
208}
209thead {
210  display:table-header-group;
211}
212ul.toc, ul.toc ul {
213  list-style: none;
214  margin-left: 1.5em;
215  padding-left: 0em;
216}
217ul.toc li {
218  line-height: 150%;
219  font-weight: bold;
220  margin-left: 0em;
221}
222ul.toc li li {
223  line-height: normal;
224  font-weight: normal;
225  font-size: 10pt;
226  margin-left: 0em;
227}
228li.excluded {
229  font-size: 0pt;
230}
231ul p {
232  margin-left: 0em;
233}
234.title, .filename, h1, h2, h3, h4 {
235  font-family: candara, helvetica, arial, sans-serif;
236}
237samp, tt, code, pre {
238  font: consolas, monospace;
239}
240ul.ind, ul.ind ul {
241  list-style: none;
242  margin-left: 1.5em;
243  padding-left: 0em;
244  page-break-before: avoid;
245}
246ul.ind li {
247  font-weight: bold;
248  line-height: 200%;
249  margin-left: 0em;
250}
251ul.ind li li {
252  font-weight: normal;
253  line-height: 150%;
254  margin-left: 0em;
255}
256.avoidbreak {
257  page-break-inside: avoid;
258}
259.bcp14 {
260  font-style: normal;
261  text-transform: lowercase;
262  font-variant: small-caps;
263}
264.comment {
265  background-color: yellow;
266}
267.center {
268  text-align: center;
269}
270.error {
271  color: red;
272  font-style: italic;
273  font-weight: bold;
274}
275.figure {
276  font-weight: bold;
277  text-align: center;
278  font-size: 10pt;
279}
280.filename {
281  color: #333333;
282  font-size: 75%;
283  font-weight: bold;
284  line-height: 21pt;
285  text-align: center;
286}
287.fn {
288  font-weight: bold;
289}
290.left {
291  text-align: left;
292}
293.right {
294  text-align: right;
295}
296.title {
297  color: green;
298  font-size: 150%;
299  line-height: 18pt;
300  font-weight: bold;
301  text-align: center;
302  margin-top: 36pt;
303}
304.warning {
305  font-size: 130%;
306  background-color: yellow;
307}
308
309
310@media print {
311  .noprint {
312    display: none;
313  }
314
315  a {
316    color: black;
317    text-decoration: none;
318  }
319
320  table.header {
321    width: 90%;
322  }
323
324  td.header {
325    width: 50%;
326    color: black;
327    background-color: white;
328    vertical-align: top;
329    font-size: 110%;
330  }
331
332  ul.toc a:nth-child(2)::after {
333    content: leader('.') target-counter(attr(href), page);
334  }
335
336  ul.ind li li a {
337    content: target-counter(attr(href), page);
338  }
339
340  .print2col {
341    column-count: 2;
342    -moz-column-count: 2;
343    column-fill: auto;
344  }
345}
346
347@page {
348  @top-left {
349       content: "Internet-Draft";
350  }
351  @top-right {
352       content: "November 2008";
353  }
354  @top-center {
355       content: "HTTP/1.1, Part 7";
356  }
357  @bottom-left {
358       content: "Fielding, et al.";
359  }
360  @bottom-center {
361       content: "Expires May 20, 2009";
362  }
363  @bottom-right {
364       content: "[Page " counter(page) "]";
365  }
366}
367
368@page:first {
369    @top-left {
370      content: normal;
371    }
372    @top-right {
373      content: normal;
374    }
375    @top-center {
376      content: normal;
377    }
378}
379</style><link rel="Contents" href="#rfc.toc">
380      <link rel="Author" href="#rfc.authors">
381      <link rel="Copyright" href="#rfc.copyright">
382      <link rel="Index" href="#rfc.index">
383      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
384      <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2">
385      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
386      <link rel="Chapter" title="4 Header Field Definitions" href="#rfc.section.4">
387      <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5">
388      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
389      <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
390      <link rel="Chapter" href="#rfc.section.8" title="8 References">
391      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
392      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
393      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.640, 2014/06/13 12:42:58, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
394      <link rel="schema.dct" href="http://purl.org/dc/terms/">
395      <meta name="dct.creator" content="Fielding, R.">
396      <meta name="dct.creator" content="Gettys, J.">
397      <meta name="dct.creator" content="Mogul, J.">
398      <meta name="dct.creator" content="Frystyk, H.">
399      <meta name="dct.creator" content="Masinter, L.">
400      <meta name="dct.creator" content="Leach, P.">
401      <meta name="dct.creator" content="Berners-Lee, T.">
402      <meta name="dct.creator" content="Lafon, Y.">
403      <meta name="dct.creator" content="Reschke, J. F.">
404      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-05">
405      <meta name="dct.issued" scheme="ISO8601" content="2008-11-16">
406      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
407      <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.">
408      <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.">
409   </head>
410   <body>
411      <table class="header">
412         <tbody>
413            <tr>
414               <td class="left">Network Working Group</td>
415               <td class="right">R. Fielding, Editor</td>
416            </tr>
417            <tr>
418               <td class="left">Internet-Draft</td>
419               <td class="right">Day Software</td>
420            </tr>
421            <tr>
422               <td class="left">Obsoletes: <a href="https://tools.ietf.org/html/rfc2616">2616</a> (if approved)
423               </td>
424               <td class="right">J. Gettys</td>
425            </tr>
426            <tr>
427               <td class="left">Updates: <a href="https://tools.ietf.org/html/rfc2617">2617</a> (if approved)
428               </td>
429               <td class="right">One Laptop per Child</td>
430            </tr>
431            <tr>
432               <td class="left">Intended status: Standards Track</td>
433               <td class="right">J. Mogul</td>
434            </tr>
435            <tr>
436               <td class="left">Expires: May 20, 2009</td>
437               <td class="right">HP</td>
438            </tr>
439            <tr>
440               <td class="left"></td>
441               <td class="right">H. Frystyk</td>
442            </tr>
443            <tr>
444               <td class="left"></td>
445               <td class="right">Microsoft</td>
446            </tr>
447            <tr>
448               <td class="left"></td>
449               <td class="right">L. Masinter</td>
450            </tr>
451            <tr>
452               <td class="left"></td>
453               <td class="right">Adobe Systems</td>
454            </tr>
455            <tr>
456               <td class="left"></td>
457               <td class="right">P. Leach</td>
458            </tr>
459            <tr>
460               <td class="left"></td>
461               <td class="right">Microsoft</td>
462            </tr>
463            <tr>
464               <td class="left"></td>
465               <td class="right">T. Berners-Lee</td>
466            </tr>
467            <tr>
468               <td class="left"></td>
469               <td class="right">W3C/MIT</td>
470            </tr>
471            <tr>
472               <td class="left"></td>
473               <td class="right">Y. Lafon, Editor</td>
474            </tr>
475            <tr>
476               <td class="left"></td>
477               <td class="right">W3C</td>
478            </tr>
479            <tr>
480               <td class="left"></td>
481               <td class="right">J. Reschke, Editor</td>
482            </tr>
483            <tr>
484               <td class="left"></td>
485               <td class="right">greenbytes</td>
486            </tr>
487            <tr>
488               <td class="left"></td>
489               <td class="right">November 16, 2008</td>
490            </tr>
491         </tbody>
492      </table>
493      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-05</span></p>
494      <div id="rfc.status">
495         <h1><a href="#rfc.status">Status of this Memo</a></h1>
496         <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
497            is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
498            6 of BCP 79.
499         </p>
500         <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
501            that other groups may also distribute working documents as Internet-Drafts.
502         </p>
503         <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
504            documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
505            in progress”.
506         </p>
507         <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>.
508         </p>
509         <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>.
510         </p>
511         <p>This Internet-Draft will expire on May 20, 2009.</p>
512      </div>
513      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1>
514      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
515         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
516         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
517         7 defines HTTP Authentication.
518      </p>
519      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1>
520      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
521         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;.
522      </p>
523      <p>The changes in this draft are summarized in <a href="#changes.since.04" title="Since draft-ietf-httpbis-p7-auth-04">Appendix&nbsp;B.6</a>.
524      </p>
525      <hr class="noprint">
526      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
527      <ul class="toc">
528         <li><a href="#rfc.section.1">1.</a>&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul>
529               <li><a href="#rfc.section.1.1">1.1</a>&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
530            </ul>
531         </li>
532         <li><a href="#rfc.section.2">2.</a>&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></li>
533         <li><a href="#rfc.section.3">3.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul>
534               <li><a href="#rfc.section.3.1">3.1</a>&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
535               <li><a href="#rfc.section.3.2">3.2</a>&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
536            </ul>
537         </li>
538         <li><a href="#rfc.section.4">4.</a>&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul>
539               <li><a href="#rfc.section.4.1">4.1</a>&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
540               <li><a href="#rfc.section.4.2">4.2</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
541               <li><a href="#rfc.section.4.3">4.3</a>&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
542               <li><a href="#rfc.section.4.4">4.4</a>&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
543            </ul>
544         </li>
545         <li><a href="#rfc.section.5">5.</a>&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul>
546               <li><a href="#rfc.section.5.1">5.1</a>&nbsp;&nbsp;&nbsp;<a href="#message.header.registration">Message Header Registration</a></li>
547            </ul>
548         </li>
549         <li><a href="#rfc.section.6">6.</a>&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul>
550               <li><a href="#rfc.section.6.1">6.1</a>&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
551            </ul>
552         </li>
553         <li><a href="#rfc.section.7">7.</a>&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
554         <li><a href="#rfc.section.8">8.</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul>
555               <li><a href="#rfc.section.8.1">8.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
556               <li><a href="#rfc.section.8.2">8.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
557            </ul>
558         </li>
559         <li><a href="#rfc.section.A">A.</a>&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul>
560               <li><a href="#rfc.section.A.1">A.1</a>&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
561            </ul>
562         </li>
563         <li><a href="#rfc.section.B">B.</a>&nbsp;&nbsp;&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a><ul>
564               <li><a href="#rfc.section.B.1">B.1</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
565               <li><a href="#rfc.section.B.2">B.2</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
566               <li><a href="#rfc.section.B.3">B.3</a>&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.3">Since draft-ietf-httpbis-p7-auth-01</a></li>
567               <li><a href="#rfc.section.B.4">B.4</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></li>
568               <li><a href="#rfc.section.B.5">B.5</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></li>
569               <li><a href="#rfc.section.B.6">B.6</a>&nbsp;&nbsp;&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></li>
570            </ul>
571         </li>
572         <li><a href="#rfc.index">Index</a></li>
573         <li><a href="#rfc.authors">Authors' Addresses</a></li>
574         <li><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
575      </ul>
576      <div id="introduction">
577         <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a href="#introduction">Introduction</a></h1>
578         <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
579            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
580            occurs.
581         </p>
582         <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
583            provide authentication information. The general framework for access authentication, and the specification of "basic" and
584            "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.
585         </p>
586         <div id="intro.requirements">
587            <h2 id="rfc.section.1.1"><a href="#rfc.section.1.1">1.1</a>&nbsp;<a href="#intro.requirements">Requirements</a></h2>
588            <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"
589               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>.
590            </p>
591            <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."
592            </p>
593         </div>
594      </div>
595      <div id="notation">
596         <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></h1>
597         <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="ABNF Extension: #rule">Section 2.1</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>.
598         </p>
599         <div id="abnf.dependencies">
600            <p id="rfc.section.2.p.2">   The ABNF rules below are defined in other specifications:</p>
601         </div>
602         <div id="rfc.figure.u.1"></div><pre class="inline">  <a href="#abnf.dependencies" class="smpl">OWS</a>           = &lt;OWS, defined in <a href="#Part1" id="rfc.xref.Part1.2"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, <a href="p1-messaging.html#basic.rules" title="Basic Rules">Section 2.2</a>&gt;
603</pre><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="https://tools.ietf.org/html/rfc2617#section-1.2">Section 1.2</a>&gt;
604  <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="https://tools.ietf.org/html/rfc2617#section-1.2">Section 1.2</a>&gt;
605</pre></div>
606      <div>
607         <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
608         </h1>
609         <div id="status.401">
610            <div id="rfc.iref.4.1"></div>
611            <div id="rfc.iref.s.1"></div>
612            <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a href="#status.401">401 Unauthorized</a></h2>
613            <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 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;4.1</a>). If the request already included Authorization credentials, then the 401 response indicates that authorization has been
614               refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
615               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
616               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>.
617            </p>
618         </div>
619         <div id="status.407">
620            <div id="rfc.iref.4.2"></div>
621            <div id="rfc.iref.s.2"></div>
622            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></h2>
623            <p id="rfc.section.3.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;4.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;4.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         </div>
627      </div>
628      <div id="header.fields">
629         <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a href="#header.fields">Header Field Definitions</a></h1>
630         <p id="rfc.section.4.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
631         <div id="header.authorization">
632            <div id="rfc.iref.a.1"></div>
633            <div id="rfc.iref.h.1"></div>
634            <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a href="#header.authorization">Authorization</a></h2>
635            <p id="rfc.section.4.1.p.1">A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does
636               so by including an Authorization request-header field with the request. The field "Authorization" consists of credentials
637               containing the authentication information of the user agent for the realm of the resource being requested.
638            </p>
639            <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="#abnf.dependencies" class="smpl">OWS</a> <a href="#header.authorization" class="smpl">Authorization-v</a>
640  <a href="#header.authorization" class="smpl">Authorization-v</a> = <a href="#abnf.dependencies" class="smpl">credentials</a>
641</pre><p id="rfc.section.4.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,
642               such as credentials that vary according to a challenge value or using synchronized clocks).
643            </p>
644            <p id="rfc.section.4.1.p.4">When a shared cache (see <a href="p6-cache.html#shared.and.non-shared.caches" title="Shared and Non-Shared Caches">Section 9</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:
645            </p>
646            <p id="rfc.section.4.1.p.5"></p>
647            <ol>
648               <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
649                  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.
650               </li>
651               <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
652                  the new request.
653               </li>
654               <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
655               </li>
656            </ol>
657         </div>
658         <div id="header.proxy-authenticate">
659            <div id="rfc.iref.p.1"></div>
660            <div id="rfc.iref.h.2"></div>
661            <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
662            <p id="rfc.section.4.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
663               the authentication scheme and parameters applicable to the proxy for this Request-URI.
664            </p>
665            <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="#abnf.dependencies" class="smpl">OWS</a>
666                         <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a>
667  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate-v</a> = 1#<a href="#abnf.dependencies" class="smpl">challenge</a>
668</pre><p id="rfc.section.4.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
669               them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
670               header field.
671            </p>
672         </div>
673         <div id="header.proxy-authorization">
674            <div id="rfc.iref.p.2"></div>
675            <div id="rfc.iref.h.3"></div>
676            <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></h2>
677            <p id="rfc.section.4.3.p.1">The request-header field "Proxy-Authorization" allows the client to identify itself (or its user) to a proxy which requires
678               authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the
679               user agent for the proxy and/or realm of the resource being requested.
680            </p>
681            <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="#abnf.dependencies" class="smpl">OWS</a>
682                          <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a>
683  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization-v</a> = <a href="#abnf.dependencies" class="smpl">credentials</a>
684</pre><p id="rfc.section.4.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
685               using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
686               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
687               authenticate a given request.
688            </p>
689         </div>
690         <div id="header.www-authenticate">
691            <div id="rfc.iref.w.1"></div>
692            <div id="rfc.iref.h.4"></div>
693            <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></h2>
694            <p id="rfc.section.4.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
695               authentication scheme(s) and parameters applicable to the Request-URI.
696            </p>
697            <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="#abnf.dependencies" class="smpl">OWS</a> <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a>
698  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a> = 1#<a href="#abnf.dependencies" class="smpl">challenge</a>
699</pre><p id="rfc.section.4.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
700               challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
701               comma-separated list of authentication parameters.
702            </p>
703         </div>
704      </div>
705      <div id="IANA.considerations">
706         <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a href="#IANA.considerations">IANA Considerations</a></h1>
707         <div id="message.header.registration">
708            <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<a href="#message.header.registration">Message Header Registration</a></h2>
709            <p id="rfc.section.5.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>):
710            </p>
711            <div id="rfc.table.1">
712               <div id="iana.header.registration.table"></div>
713               <table class="tt full left" cellpadding="3" cellspacing="0">
714                  <thead>
715                     <tr>
716                        <th>Header Field Name</th>
717                        <th>Protocol</th>
718                        <th>Status</th>
719                        <th>Reference</th>
720                     </tr>
721                  </thead>
722                  <tbody>
723                     <tr>
724                        <td class="left">Authorization</td>
725                        <td class="left">http</td>
726                        <td class="left">standard</td>
727                        <td class="left"><a href="#header.authorization" id="rfc.xref.header.authorization.2" title="Authorization">Section&nbsp;4.1</a> 
728                        </td>
729                     </tr>
730                     <tr>
731                        <td class="left">Proxy-Authenticate</td>
732                        <td class="left">http</td>
733                        <td class="left">standard</td>
734                        <td class="left"><a href="#header.proxy-authenticate" id="rfc.xref.header.proxy-authenticate.2" title="Proxy-Authenticate">Section&nbsp;4.2</a> 
735                        </td>
736                     </tr>
737                     <tr>
738                        <td class="left">Proxy-Authorization</td>
739                        <td class="left">http</td>
740                        <td class="left">standard</td>
741                        <td class="left"><a href="#header.proxy-authorization" id="rfc.xref.header.proxy-authorization.2" title="Proxy-Authorization">Section&nbsp;4.3</a> 
742                        </td>
743                     </tr>
744                     <tr>
745                        <td class="left">WWW-Authenticate</td>
746                        <td class="left">http</td>
747                        <td class="left">standard</td>
748                        <td class="left"><a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section&nbsp;4.4</a> 
749                        </td>
750                     </tr>
751                  </tbody>
752               </table>
753            </div>
754            <p id="rfc.section.5.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
755         </div>
756      </div>
757      <div id="security.considerations">
758         <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a href="#security.considerations">Security Considerations</a></h1>
759         <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
760            as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
761            make some suggestions for reducing security risks.
762         </p>
763         <div id="auth.credentials.and.idle.clients">
764            <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
765            <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
766               a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
767               extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
768               but are not limited to:
769            </p>
770            <ul>
771               <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
772                  the user for credentials.
773               </li>
774               <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
775                  the server side of the application `knows' that there is no further reason for the client to retain the credentials.
776               </li>
777            </ul>
778            <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
779               use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
780               in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
781               for discarding cached credentials under user control.
782            </p>
783         </div>
784      </div>
785      <div id="ack">
786         <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a href="#ack">Acknowledgments</a></h1>
787         <p id="rfc.section.7.p.1"><span class="comment" id="rfc.comment.1">[<a href="#rfc.comment.1" class="smpl">rfc.comment.1</a>: TBD.]</span> 
788         </p>
789      </div>
790      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
791      </h1>
792      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
793      </h2>
794      <table>
795         <tr>
796            <td class="reference"><b id="Part1">[Part1]</b></td>
797            <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="https://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-05">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-05 (work in progress), November&nbsp;2008.
798            </td>
799         </tr>
800         <tr>
801            <td class="reference"><b id="Part6">[Part6]</b></td>
802            <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="https://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-05">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-05 (work in progress), November&nbsp;2008.
803            </td>
804         </tr>
805         <tr>
806            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
807            <td class="top"><a href="mailto:sob@harvard.edu" title="Harvard University">Bradner, S.</a>, “<a href="https://tools.ietf.org/html/rfc2119">Key words for use in RFCs to Indicate Requirement Levels</a>”, BCP&nbsp;14, RFC&nbsp;2119, March&nbsp;1997.
808            </td>
809         </tr>
810         <tr>
811            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
812            <td class="top"><a href="mailto:john@math.nwu.edu" title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a href="mailto:pbaker@verisign.com" title="Verisign Inc.">Hallam-Baker, P.</a>, <a href="mailto:jeff@AbiSource.com" title="AbiSource, Inc.">Hostetler, J.</a>, <a href="mailto:lawrence@agranat.com" title="Agranat Systems, Inc.">Lawrence, S.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, Luotonen, A., and <a href="mailto:stewart@OpenMarket.com" title="Open Market, Inc.">L. Stewart</a>, “<a href="https://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC&nbsp;2617, June&nbsp;1999.
813            </td>
814         </tr>
815      </table>
816      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
817      </h2>
818      <table>
819         <tr>
820            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
821            <td class="top"><a href="mailto:fielding@ics.uci.edu" title="University of California, Irvine">Fielding, R.</a>, <a href="mailto:jg@w3.org" title="W3C">Gettys, J.</a>, <a href="mailto:mogul@wrl.dec.com" title="Compaq Computer Corporation">Mogul, J.</a>, <a href="mailto:frystyk@w3.org" title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a href="mailto:masinter@parc.xerox.com" title="Xerox Corporation">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, and <a href="mailto:timbl@w3.org" title="W3C">T. Berners-Lee</a>, “<a href="https://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2616, June&nbsp;1999.
822            </td>
823         </tr>
824         <tr>
825            <td class="reference"><b id="RFC3864">[RFC3864]</b></td>
826            <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="https://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP&nbsp;90, RFC&nbsp;3864, September&nbsp;2004.
827            </td>
828         </tr>
829      </table>
830      <div id="compatibility">
831         <h1 id="rfc.section.A" class="np"><a href="#rfc.section.A">A.</a>&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a></h1>
832         <div id="changes.from.rfc.2616">
833            <h2 id="rfc.section.A.1"><a href="#rfc.section.A.1">A.1</a>&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2>
834         </div>
835      </div>
836      <div id="change.log">
837         <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
838         <div>
839            <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
840            </h2>
841            <p id="rfc.section.B.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>.
842            </p>
843         </div>
844         <div>
845            <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
846            </h2>
847            <p id="rfc.section.B.2.p.1">Closed issues: </p>
848            <ul>
849               <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"
850               </li>
851            </ul>
852         </div>
853         <div>
854            <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a>&nbsp;Since draft-ietf-httpbis-p7-auth-01
855            </h2>
856            <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;):
857            </p>
858            <ul>
859               <li>Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.</li>
860               <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
861            </ul>
862         </div>
863         <div id="changes.since.02">
864            <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a>&nbsp;<a href="#changes.since.02">Since draft-ietf-httpbis-p7-auth-02</a></h2>
865            <p id="rfc.section.B.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;):
866            </p>
867            <ul>
868               <li>Reference RFC 3984, and update header registrations for headers defined in this document.</li>
869            </ul>
870         </div>
871         <div id="changes.since.03">
872            <h2 id="rfc.section.B.5"><a href="#rfc.section.B.5">B.5</a>&nbsp;<a href="#changes.since.03">Since draft-ietf-httpbis-p7-auth-03</a></h2>
873         </div>
874         <div id="changes.since.04">
875            <h2 id="rfc.section.B.6"><a href="#rfc.section.B.6">B.6</a>&nbsp;<a href="#changes.since.04">Since draft-ietf-httpbis-p7-auth-04</a></h2>
876            <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;):
877            </p>
878            <ul>
879               <li>Use "/" instead of "|" for alternatives.</li>
880               <li>Introduce new ABNF rules for "bad" whitespace ("BWS"), optional whitespace ("OWS") and required whitespace ("RWS").</li>
881               <li>Rewrite ABNFs to spell out whitespace rules, factor out header value format definitions.</li>
882            </ul>
883         </div>
884      </div>
885      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
886      <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> 
887      </p>
888      <div class="print2col">
889         <ul class="ind">
890            <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul>
891                  <li>401 Unauthorized (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.1"><b>3.1</b></a></li>
892                  <li>407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a href="#rfc.iref.4.2"><b>3.2</b></a></li>
893               </ul>
894            </li>
895            <li><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul>
896                  <li>Authorization header&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">3.1</a>, <a href="#rfc.iref.a.1"><b>4.1</b></a>, <a href="#rfc.xref.header.authorization.2">5.1</a></li>
897               </ul>
898            </li>
899            <li><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul>
900                  <li><tt>Grammar</tt>&nbsp;&nbsp;
901                     <ul>
902                        <li><tt>Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.3"><b>4.1</b></a></li>
903                        <li><tt>Authorization-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.4"><b>4.1</b></a></li>
904                        <li><tt>challenge</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.1"><b>2</b></a></li>
905                        <li><tt>credentials</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.2"><b>2</b></a></li>
906                        <li><tt>Proxy-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.5"><b>4.2</b></a></li>
907                        <li><tt>Proxy-Authenticate-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.6"><b>4.2</b></a></li>
908                        <li><tt>Proxy-Authorization</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.7"><b>4.3</b></a></li>
909                        <li><tt>Proxy-Authorization-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.8"><b>4.3</b></a></li>
910                        <li><tt>WWW-Authenticate</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.9"><b>4.4</b></a></li>
911                        <li><tt>WWW-Authenticate-v</tt>&nbsp;&nbsp;<a href="#rfc.iref.g.10"><b>4.4</b></a></li>
912                     </ul>
913                  </li>
914               </ul>
915            </li>
916            <li><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul>
917                  <li>Headers&nbsp;&nbsp;
918                     <ul>
919                        <li>Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.authorization.1">3.1</a>, <a href="#rfc.iref.h.1"><b>4.1</b></a>, <a href="#rfc.xref.header.authorization.2">5.1</a></li>
920                        <li>Proxy-Authenticate&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a href="#rfc.iref.h.2"><b>4.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">5.1</a></li>
921                        <li>Proxy-Authorization&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a href="#rfc.iref.h.3"><b>4.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">5.1</a></li>
922                        <li>WWW-Authenticate&nbsp;&nbsp;<a href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a href="#rfc.iref.h.4"><b>4.4</b></a>, <a href="#rfc.xref.header.www-authenticate.2">5.1</a></li>
923                     </ul>
924                  </li>
925               </ul>
926            </li>
927            <li><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul>
928                  <li><em>Part1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">2</a>, <a href="#rfc.xref.Part1.2">2</a>, <a href="#Part1"><b>8.1</b></a><ul>
929                        <li><em>Section 2.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.1">2</a></li>
930                        <li><em>Section 2.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part1.2">2</a></li>
931                     </ul>
932                  </li>
933                  <li><em>Part6</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a>, <a href="#Part6"><b>8.1</b></a><ul>
934                        <li><em>Section 9</em>&nbsp;&nbsp;<a href="#rfc.xref.Part6.1">4.1</a></li>
935                     </ul>
936                  </li>
937                  <li>Proxy-Authenticate header&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a href="#rfc.iref.p.1"><b>4.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">5.1</a></li>
938                  <li>Proxy-Authorization header&nbsp;&nbsp;<a href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a href="#rfc.iref.p.2"><b>4.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">5.1</a></li>
939               </ul>
940            </li>
941            <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul>
942                  <li><em>RFC2119</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li>
943                  <li><em>RFC2616</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2616.1">1</a>, <a href="#RFC2616"><b>8.2</b></a>, <a href="#rfc.xref.RFC2616.2">B.1</a></li>
944                  <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">2</a>, <a href="#rfc.xref.RFC2617.4">2</a>, <a href="#rfc.xref.RFC2617.5">3.1</a>, <a href="#rfc.xref.RFC2617.6">3.2</a>, <a href="#rfc.xref.RFC2617.7">4.1</a>, <a href="#rfc.xref.RFC2617.8">4.2</a>, <a href="#rfc.xref.RFC2617.9">4.3</a>, <a href="#rfc.xref.RFC2617.10">4.4</a>, <a href="#RFC2617"><b>8.1</b></a><ul>
945                        <li><em>Section 1.2</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC2617.3">2</a>, <a href="#rfc.xref.RFC2617.4">2</a></li>
946                     </ul>
947                  </li>
948                  <li><em>RFC3864</em>&nbsp;&nbsp;<a href="#rfc.xref.RFC3864.1">5.1</a>, <a href="#RFC3864"><b>8.2</b></a></li>
949               </ul>
950            </li>
951            <li><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul>
952                  <li>Status Codes&nbsp;&nbsp;
953                     <ul>
954                        <li>401 Unauthorized&nbsp;&nbsp;<a href="#rfc.iref.s.1"><b>3.1</b></a></li>
955                        <li>407 Proxy Authentication Required&nbsp;&nbsp;<a href="#rfc.iref.s.2"><b>3.2</b></a></li>
956                     </ul>
957                  </li>
958               </ul>
959            </li>
960            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul>
961                  <li>WWW-Authenticate header&nbsp;&nbsp;<a href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a href="#rfc.iref.w.1"><b>4.4</b></a>, <a href="#rfc.xref.header.www-authenticate.2">5.1</a></li>
962               </ul>
963            </li>
964         </ul>
965      </div>
966      <div class="avoidbreak">
967         <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
968         <p><b>Roy T. Fielding</b>
969            (editor)
970            <br>Day Software<br>23 Corporate Plaza DR, Suite 280<br>Newport Beach, CA&nbsp;92660<br>USA<br>Phone: <a href="tel:+1-949-706-5300">+1-949-706-5300</a><br>Fax: <a href="fax:+1-949-706-5305">+1-949-706-5305</a><br>EMail: <a href="mailto:fielding@gbiv.com">fielding@gbiv.com</a><br>URI: <a href="http://roy.gbiv.com/">http://roy.gbiv.com/</a></p>
971         <p><b>Jim Gettys</b><br>One Laptop per Child<br>21 Oak Knoll Road<br>Carlisle, MA&nbsp;01741<br>USA<br>EMail: <a href="mailto:jg@laptop.org">jg@laptop.org</a><br>URI: <a href="http://www.laptop.org/">http://www.laptop.org/</a></p>
972         <p><b>Jeffrey C. Mogul</b><br>Hewlett-Packard Company<br>HP Labs, Large Scale Systems Group<br>1501 Page Mill Road, MS 1177<br>Palo Alto, CA&nbsp;94304<br>USA<br>EMail: <a href="mailto:JeffMogul@acm.org">JeffMogul@acm.org</a></p>
973         <p><b>Henrik Frystyk Nielsen</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>USA<br>EMail: <a href="mailto:henrikn@microsoft.com">henrikn@microsoft.com</a></p>
974         <p><b>Larry Masinter</b><br>Adobe Systems, Incorporated<br>345 Park Ave<br>San Jose, CA&nbsp;95110<br>USA<br>EMail: <a href="mailto:LMM@acm.org">LMM@acm.org</a><br>URI: <a href="http://larry.masinter.net/">http://larry.masinter.net/</a></p>
975         <p><b>Paul J. Leach</b><br>Microsoft Corporation<br>1 Microsoft Way<br>Redmond, WA&nbsp;98052<br>EMail: <a href="mailto:paulle@microsoft.com">paulle@microsoft.com</a></p>
976         <p><b>Tim Berners-Lee</b><br>World Wide Web Consortium<br>MIT Computer Science and Artificial Intelligence Laboratory<br>The Stata Center, Building 32<br>32 Vassar Street<br>Cambridge, MA&nbsp;02139<br>USA<br>EMail: <a href="mailto:timbl@w3.org">timbl@w3.org</a><br>URI: <a href="http://www.w3.org/People/Berners-Lee/">http://www.w3.org/People/Berners-Lee/</a></p>
977         <p><b>Yves Lafon</b>
978            (editor)
979            <br>World Wide Web Consortium<br>W3C / ERCIM<br>2004, rte des Lucioles<br>Sophia-Antipolis, AM&nbsp;06902<br>France<br>EMail: <a href="mailto:ylafon@w3.org">ylafon@w3.org</a><br>URI: <a href="http://www.raubacapeu.net/people/yves/">http://www.raubacapeu.net/people/yves/</a></p>
980         <p><b>Julian F. Reschke</b>
981            (editor)
982            <br>greenbytes GmbH<br>Hafenweg 16<br>Muenster, NW&nbsp;48155<br>Germany<br>Phone: <a href="tel:+492512807760">+49 251 2807760</a><br>Fax: <a href="fax:+492512807761">+49 251 2807761</a><br>EMail: <a href="mailto:julian.reschke@greenbytes.de">julian.reschke@greenbytes.de</a><br>URI: <a href="http://greenbytes.de/tech/webdav/">http://greenbytes.de/tech/webdav/</a></p>
983      </div>
984      <div id="rfc.copyright">
985         <h1><a href="#rfc.copyright">Full Copyright Statement</a></h1>
986         <p>Copyright © The IETF Trust (2008).</p>
987         <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
988            authors retain all their rights.
989         </p>
990         <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
991            HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
992            DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
993            WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
994         </p>
995      </div>
996      <div id="rfc.ipr">
997         <h1><a href="#rfc.ipr">Intellectual Property</a></h1>
998         <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
999            be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
1000            license under such rights might or might not be available; nor does it represent that it has made any independent effort to
1001            identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
1002            BCP 79.
1003         </p>
1004         <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
1005            of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
1006            of this specification can be obtained from the IETF on-line IPR repository at <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.
1007         </p>
1008         <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
1009            rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
1010            at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
1011         </p>
1012      </div>
1013   </body>
1014</html>
Note: See TracBrowser for help on using the repository browser.