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

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

take advantage of new version of rfc2629.xslt.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/html;charset=utf-8
File size: 55.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">
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
39dl.empty dd {
40  margin-top: .5em;
41}
42dl p {
43  margin-left: 0em;
44}
45dt {
46  margin-top: .5em;
47}
48h1 {
49  font-size: 14pt;
50  line-height: 21pt;
51  page-break-after: avoid;
52}
53h1.np {
54  page-break-before: always;
55}
56h1 a {
57  color: #333333;
58}
59h2 {
60  font-size: 12pt;
61  line-height: 15pt;
62  page-break-after: avoid;
63}
64h2 a {
65  color: black;
66}
67h3 {
68  font-size: 10pt;
69  page-break-after: avoid;
70}
71h3 a {
72  color: black;
73}
74h4 {
75  font-size: 10pt;
76  page-break-after: avoid;
77}
78h4 a {
79  color: black;
80}
81h5 {
82  font-size: 10pt;
83  page-break-after: avoid;
84}
85h5 a {
86  color: black;
87}
88img {
89  margin-left: 3em;
90}
91li {
92  margin-left: 2em;
93  margin-right: 2em;
94}
95ol {
96  margin-left: 2em;
97  margin-right: 2em;
98}
99ol p {
100  margin-left: 0em;
101}
102p {
103  margin-left: 2em;
104  margin-right: 2em;
105}
106pre {
107  margin-left: 3em;
108  background-color: lightyellow;
109  padding: .25em;
110}
111pre.text2 {
112  border-style: dotted;
113  border-width: 1px;
114  background-color: #f0f0f0;
115  width: 69em;
116}
117pre.inline {
118  background-color: white;
119  padding: 0em;
120}
121pre.text {
122  border-style: dotted;
123  border-width: 1px;
124  background-color: #f8f8f8;
125  width: 69em;
126}
127pre.drawing {
128  border-style: solid;
129  border-width: 1px;
130  background-color: #f8f8f8;
131  padding: 2em;
132}
133table {
134  margin-left: 2em;
135}
136table.header {
137  width: 95%;
138  font-size: 10pt;
139  color: white;
140}
141td.top {
142  vertical-align: top;
143}
144td.topnowrap {
145  vertical-align: top;
146  white-space: nowrap; 
147}
148td.header {
149  background-color: gray;
150  width: 50%;
151}
152td.header a {
153  color: white;
154}
155td.reference {
156  vertical-align: top;
157  white-space: nowrap;
158  padding-right: 1em;
159}
160thead {
161  display:table-header-group;
162}
163ul.toc {
164  list-style: none;
165  margin-left: 1.5em;
166  margin-right: 0em;
167  padding-left: 0em;
168}
169li.tocline0 {
170  line-height: 150%;
171  font-weight: bold;
172  font-size: 10pt;
173  margin-left: 0em;
174  margin-right: 0em;
175}
176li.tocline1 {
177  line-height: normal;
178  font-weight: normal;
179  font-size: 9pt;
180  margin-left: 0em;
181  margin-right: 0em;
182}
183li.tocline2 {
184  font-size: 0pt;
185}
186ul p {
187  margin-left: 0em;
188}
189ul.ind {
190  list-style: none;
191  margin-left: 1.5em;
192  margin-right: 0em;
193  padding-left: 0em;
194}
195li.indline0 {
196  font-weight: bold;
197  line-height: 200%;
198  margin-left: 0em;
199  margin-right: 0em;
200}
201li.indline1 {
202  font-weight: normal;
203  line-height: 150%;
204  margin-left: 0em;
205  margin-right: 0em;
206}
207.bcp14 {
208  font-style: normal;
209  text-transform: lowercase;
210  font-variant: small-caps;
211}
212.comment {
213  background-color: yellow;
214}
215.center {
216  text-align: center;
217}
218.error {
219  color: red;
220  font-style: italic;
221  font-weight: bold;
222}
223.figure {
224  font-weight: bold;
225  text-align: center;
226  font-size: 9pt;
227}
228.filename {
229  color: #333333;
230  font-weight: bold;
231  font-size: 12pt;
232  line-height: 21pt;
233  text-align: center;
234}
235.fn {
236  font-weight: bold;
237}
238.hidden {
239  display: none;
240}
241.left {
242  text-align: left;
243}
244.right {
245  text-align: right;
246}
247.title {
248  color: #990000;
249  font-size: 18pt;
250  line-height: 18pt;
251  font-weight: bold;
252  text-align: center;
253  margin-top: 36pt;
254}
255.vcardline {
256  display: block;
257}
258.warning {
259  font-size: 14pt;
260  background-color: yellow;
261}
262
263
264@media print {
265  .noprint {
266    display: none;
267  }
268 
269  a {
270    color: black;
271    text-decoration: none;
272  }
273
274  table.header {
275    width: 90%;
276  }
277
278  td.header {
279    width: 50%;
280    color: black;
281    background-color: white;
282    vertical-align: top;
283    font-size: 12pt;
284  }
285
286  ul.toc a::after {
287    content: leader('.') target-counter(attr(href), page);
288  }
289 
290  a.iref {
291    content: target-counter(attr(href), page);
292  }
293 
294  .print2col {
295    column-count: 2;
296    -moz-column-count: 2;
297    column-fill: auto;
298  }
299}
300
301@page {
302  @top-left {
303       content: "INTERNET DRAFT"; 
304  } 
305  @top-right {
306       content: "May 2008"; 
307  } 
308  @top-center {
309       content: "HTTP/1.1, Part 7"; 
310  } 
311  @bottom-left {
312       content: "Fielding, et al."; 
313  } 
314  @bottom-center {
315       content: "Standards Track"; 
316  } 
317  @bottom-right {
318       content: "[Page " counter(page) "]"; 
319  } 
320}
321
322@page:first { 
323    @top-left {
324      content: normal;
325    }
326    @top-right {
327      content: normal;
328    }
329    @top-center {
330      content: normal;
331    }
332}
333</style><link rel="Contents" href="#rfc.toc">
334      <link rel="Author" href="#rfc.authors">
335      <link rel="Copyright" href="#rfc.copyright">
336      <link rel="Index" href="#rfc.index">
337      <link rel="Chapter" title="1 Introduction" href="#rfc.section.1">
338      <link rel="Chapter" title="2 Notational Conventions and Generic Grammar" href="#rfc.section.2">
339      <link rel="Chapter" title="3 Status Code Definitions" href="#rfc.section.3">
340      <link rel="Chapter" title="4 Header Field Definitions" href="#rfc.section.4">
341      <link rel="Chapter" title="5 IANA Considerations" href="#rfc.section.5">
342      <link rel="Chapter" title="6 Security Considerations" href="#rfc.section.6">
343      <link rel="Chapter" title="7 Acknowledgments" href="#rfc.section.7">
344      <link rel="Chapter" href="#rfc.section.8" title="8 References">
345      <link rel="Appendix" title="A Compatibility with Previous Versions" href="#rfc.section.A">
346      <link rel="Appendix" title="B Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.B">
347      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.367, 2008-05-19 13:00:19, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
348      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
349      <meta name="DC.Creator" content="Fielding, R.">
350      <meta name="DC.Creator" content="Gettys, J.">
351      <meta name="DC.Creator" content="Mogul, J.">
352      <meta name="DC.Creator" content="Frystyk, H.">
353      <meta name="DC.Creator" content="Masinter, L.">
354      <meta name="DC.Creator" content="Leach, P.">
355      <meta name="DC.Creator" content="Berners-Lee, T.">
356      <meta name="DC.Creator" content="Lafon, Y.">
357      <meta name="DC.Creator" content="Reschke, J. F.">
358      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
359      <meta name="DC.Date.Issued" scheme="ISO8601" content="2008-05">
360      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
361      <meta name="DC.Description.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.">
362   </head>
363   <body>
364      <table summary="header information" class="header" border="0" cellpadding="1" cellspacing="1">
365         <tr>
366            <td class="header left">Network Working Group</td>
367            <td class="header right">R. Fielding, Editor</td>
368         </tr>
369         <tr>
370            <td class="header left">Internet Draft</td>
371            <td class="header right">Day Software</td>
372         </tr>
373         <tr>
374            <td class="header left">
375               &lt;draft-ietf-httpbis-p7-auth-latest&gt;
376               
377            </td>
378            <td class="header right">J. Gettys</td>
379         </tr>
380         <tr>
381            <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
382            </td>
383            <td class="header right">One Laptop per Child</td>
384         </tr>
385         <tr>
386            <td class="header left">Updates: <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)
387            </td>
388            <td class="header right">J. Mogul</td>
389         </tr>
390         <tr>
391            <td class="header left">Intended status: Standards Track</td>
392            <td class="header right">HP</td>
393         </tr>
394         <tr>
395            <td class="header left">Expires: November 2008</td>
396            <td class="header right">H. Frystyk</td>
397         </tr>
398         <tr>
399            <td class="header left"></td>
400            <td class="header right">Microsoft</td>
401         </tr>
402         <tr>
403            <td class="header left"></td>
404            <td class="header right">L. Masinter</td>
405         </tr>
406         <tr>
407            <td class="header left"></td>
408            <td class="header right">Adobe Systems</td>
409         </tr>
410         <tr>
411            <td class="header left"></td>
412            <td class="header right">P. Leach</td>
413         </tr>
414         <tr>
415            <td class="header left"></td>
416            <td class="header right">Microsoft</td>
417         </tr>
418         <tr>
419            <td class="header left"></td>
420            <td class="header right">T. Berners-Lee</td>
421         </tr>
422         <tr>
423            <td class="header left"></td>
424            <td class="header right">W3C/MIT</td>
425         </tr>
426         <tr>
427            <td class="header left"></td>
428            <td class="header right">Y. Lafon, Editor</td>
429         </tr>
430         <tr>
431            <td class="header left"></td>
432            <td class="header right">W3C</td>
433         </tr>
434         <tr>
435            <td class="header left"></td>
436            <td class="header right">J. F. Reschke, Editor</td>
437         </tr>
438         <tr>
439            <td class="header left"></td>
440            <td class="header right">greenbytes</td>
441         </tr>
442         <tr>
443            <td class="header left"></td>
444            <td class="header right">May 19, 2008</td>
445         </tr>
446      </table>
447      <p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-ietf-httpbis-p7-auth-latest</span></p>
448      <h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1>
449      <p>By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she
450         is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section
451         6 of BCP 79.
452      </p>
453      <p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note
454         that other groups may also distribute working documents as Internet-Drafts.
455      </p>
456      <p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other
457         documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as “work
458         in progress”.
459      </p>
460      <p>The list of current Internet-Drafts can be accessed at &lt;<a href="http://www.ietf.org/ietf/1id-abstracts.txt">http://www.ietf.org/ietf/1id-abstracts.txt</a>&gt;.
461      </p>
462      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
463      </p>
464      <p>This Internet-Draft will expire in November 2008.</p>
465      <h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> 
466      <p>The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information
467         systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the
468         seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part
469         7 defines HTTP Authentication.
470      </p> 
471      <h1 id="rfc.note.1"><a href="#rfc.note.1">Editorial Note (To be removed by RFC Editor)</a></h1> 
472      <p>Discussion of this draft should take place on the HTTPBIS working group mailing list (ietf-http-wg@w3.org). The current issues
473         list is at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/trac/report/11">http://www.tools.ietf.org/wg/httpbis/trac/report/11</a>&gt; and related documents (including fancy diffs) can be found at &lt;<a href="http://www.tools.ietf.org/wg/httpbis/">http://www.tools.ietf.org/wg/httpbis/</a>&gt;.
474      </p> 
475      <p>This draft incorporates those issue resolutions that were either collected in the original RFC2616 errata list (&lt;<a href="http://purl.org/NET/http-errata">http://purl.org/NET/http-errata</a>&gt;), or which were agreed upon on the mailing list between October 2006 and November 2007 (as published in "draft-lafon-rfc2616bis-03").
476      </p> 
477      <hr class="noprint">
478      <h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1>
479      <ul class="toc">
480         <li class="tocline0">1.&nbsp;&nbsp;&nbsp;<a href="#introduction">Introduction</a><ul class="toc">
481               <li class="tocline1">1.1&nbsp;&nbsp;&nbsp;<a href="#intro.requirements">Requirements</a></li>
482            </ul>
483         </li>
484         <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#notation">Notational Conventions and Generic Grammar</a></li>
485         <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.3">Status Code Definitions</a><ul class="toc">
486               <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li>
487               <li class="tocline1">3.2&nbsp;&nbsp;&nbsp;<a href="#status.407">407 Proxy Authentication Required</a></li>
488            </ul>
489         </li>
490         <li class="tocline0">4.&nbsp;&nbsp;&nbsp;<a href="#header.fields">Header Field Definitions</a><ul class="toc">
491               <li class="tocline1">4.1&nbsp;&nbsp;&nbsp;<a href="#header.authorization">Authorization</a></li>
492               <li class="tocline1">4.2&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authenticate">Proxy-Authenticate</a></li>
493               <li class="tocline1">4.3&nbsp;&nbsp;&nbsp;<a href="#header.proxy-authorization">Proxy-Authorization</a></li>
494               <li class="tocline1">4.4&nbsp;&nbsp;&nbsp;<a href="#header.www-authenticate">WWW-Authenticate</a></li>
495            </ul>
496         </li>
497         <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a></li>
498         <li class="tocline0">6.&nbsp;&nbsp;&nbsp;<a href="#security.considerations">Security Considerations</a><ul class="toc">
499               <li class="tocline1">6.1&nbsp;&nbsp;&nbsp;<a href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></li>
500            </ul>
501         </li>
502         <li class="tocline0">7.&nbsp;&nbsp;&nbsp;<a href="#ack">Acknowledgments</a></li>
503         <li class="tocline0">8.&nbsp;&nbsp;&nbsp;<a href="#rfc.references">References</a><ul class="toc">
504               <li class="tocline1">8.1&nbsp;&nbsp;&nbsp;<a href="#rfc.references.1">Normative References</a></li>
505               <li class="tocline1">8.2&nbsp;&nbsp;&nbsp;<a href="#rfc.references.2">Informative References</a></li>
506            </ul>
507         </li>
508         <li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li>
509         <li class="tocline0">A.&nbsp;&nbsp;&nbsp;<a href="#compatibility">Compatibility with Previous Versions</a><ul class="toc">
510               <li class="tocline1">A.1&nbsp;&nbsp;&nbsp;<a href="#changes.from.rfc.2616">Changes from RFC 2616</a></li>
511            </ul>
512         </li>
513         <li class="tocline0">B.&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B">Change Log (to be removed by RFC Editor before publication)</a><ul class="toc">
514               <li class="tocline1">B.1&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.1">Since RFC2616</a></li>
515               <li class="tocline1">B.2&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.2">Since draft-ietf-httpbis-p7-auth-00</a></li>
516               <li class="tocline1">B.3&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.3">Since draft-ietf-httpbis-p7-auth-01</a></li>
517               <li class="tocline1">B.4&nbsp;&nbsp;&nbsp;<a href="#rfc.section.B.4">Since draft-ietf-httpbis-p7-auth-02</a></li>
518            </ul>
519         </li>
520         <li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li>
521         <li class="tocline0"><a href="#rfc.index">Index</a></li>
522      </ul>
523      <h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a>&nbsp;<a id="introduction" href="#introduction">Introduction</a></h1>
524      <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
525         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
526         occurs.
527      </p>
528      <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
529         provide authentication information. The general framework for access authentication, and the specification of "basic" and
530         "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.
531      </p>
532      <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>
533      <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"
534         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>.
535      </p>
536      <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."
537      </p>
538      <h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a>&nbsp;<a id="notation" href="#notation">Notational Conventions and Generic Grammar</a></h1>
539      <p id="rfc.section.2.p.1">This specification uses the ABNF syntax defined in <a href="p1-messaging.html#notation.abnf" title="Augmented BNF">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>. <span class="comment">[abnf.dep: ABNF syntax and basic rules will be adopted from RFC 5234, see &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/36">http://tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;.]</span> 
540      </p>
541      <div id="abnf.dependencies">
542         <p id="rfc.section.2.p.2">    The ABNF rules below are defined in other specifications:</p>
543      </div>
544      <div id="rfc.figure.u.1"></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;
545  <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;
546</pre><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;Status Code Definitions
547      </h1>
548      <div id="rfc.iref.2"></div>
549      <div id="rfc.iref.s.1"></div>
550      <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a>&nbsp;<a id="status.401" href="#status.401">401 Unauthorized</a></h2>
551      <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
552         refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has
553         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
554         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>.
555      </p>
556      <div id="rfc.iref.3"></div>
557      <div id="rfc.iref.s.2"></div>
558      <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a id="status.407" href="#status.407">407 Proxy Authentication Required</a></h2>
559      <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
560         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>.
561      </p>
562      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
563      <p id="rfc.section.4.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to authentication.</p>
564      <div id="rfc.iref.a.1"></div>
565      <div id="rfc.iref.h.1"></div>
566      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="header.authorization" href="#header.authorization">Authorization</a></h2>
567      <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
568         so by including an Authorization request-header field with the request. The Authorization field value consists of credentials
569         containing the authentication information of the user agent for the realm of the resource being requested.
570      </p>
571      <div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.3"></span>  <a href="#header.authorization" class="smpl">Authorization</a>  = "Authorization" ":" <a href="#abnf.dependencies" class="smpl">credentials</a>
572</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,
573         such as credentials that vary according to a challenge value or using synchronized clocks).
574      </p>
575      <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:
576      </p>
577      <p id="rfc.section.4.1.p.5"> </p>
578      <ol>
579         <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
580            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.
581         </li>
582         <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
583            the new request.
584         </li>
585         <li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned in reply to any subsequent request.
586         </li>
587      </ol>
588      <div id="rfc.iref.p.1"></div>
589      <div id="rfc.iref.h.2"></div>
590      <h2 id="rfc.section.4.2"><a href="#rfc.section.4.2">4.2</a>&nbsp;<a id="header.proxy-authenticate" href="#header.proxy-authenticate">Proxy-Authenticate</a></h2>
591      <p id="rfc.section.4.2.p.1">The Proxy-Authenticate response-header field <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
592         the authentication scheme and parameters applicable to the proxy for this Request-URI.
593      </p>
594      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.4"></span>  <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a>  = "Proxy-Authenticate" ":" 1#<a href="#abnf.dependencies" class="smpl">challenge</a>
595</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
596         them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate
597         header field.
598      </p>
599      <div id="rfc.iref.p.2"></div>
600      <div id="rfc.iref.h.3"></div>
601      <h2 id="rfc.section.4.3"><a href="#rfc.section.4.3">4.3</a>&nbsp;<a id="header.proxy-authorization" href="#header.proxy-authorization">Proxy-Authorization</a></h2>
602      <p id="rfc.section.4.3.p.1">The Proxy-Authorization request-header field allows the client to identify itself (or its user) to a proxy which requires
603         authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the
604         user agent for the proxy and/or realm of the resource being requested.
605      </p>
606      <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.5"></span>  <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a>     = "Proxy-Authorization" ":" <a href="#abnf.dependencies" class="smpl">credentials</a>
607</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
608         using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed
609         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
610         authenticate a given request.
611      </p>
612      <div id="rfc.iref.w.1"></div>
613      <div id="rfc.iref.h.4"></div>
614      <h2 id="rfc.section.4.4"><a href="#rfc.section.4.4">4.4</a>&nbsp;<a id="header.www-authenticate" href="#header.www-authenticate">WWW-Authenticate</a></h2>
615      <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
616         authentication scheme(s) and parameters applicable to the Request-URI.
617      </p>
618      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.6"></span>  <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a>  = "WWW-Authenticate" ":" 1#<a href="#abnf.dependencies" class="smpl">challenge</a>
619</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
620         challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a
621         comma-separated list of authentication parameters.
622      </p>
623      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1>
624      <p id="rfc.section.5.p.1"> <span class="comment">[rfc.comment.1: TBD.]</span> 
625      </p>
626      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
627      <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
628         as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does
629         make some suggestions for reducing security risks.
630      </p>
631      <h2 id="rfc.section.6.1"><a href="#rfc.section.6.1">6.1</a>&nbsp;<a id="auth.credentials.and.idle.clients" href="#auth.credentials.and.idle.clients">Authentication Credentials and Idle Clients</a></h2>
632      <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
633         a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further
634         extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include
635         but are not limited to:
636      </p>
637      <ul>
638         <li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt
639            the user for credentials.
640         </li>
641         <li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which
642            the server side of the application `knows' that there is no further reason for the client to retain the credentials.
643         </li>
644      </ul>
645      <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
646         use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent
647         in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism
648         for discarding cached credentials under user control.
649      </p>
650      <h1 id="rfc.section.7"><a href="#rfc.section.7">7.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
651      <p id="rfc.section.7.p.1"> <span class="comment">[rfc.comment.2: TBD.]</span> 
652      </p>
653      <h1 id="rfc.references"><a id="rfc.section.8" href="#rfc.section.8">8.</a> References
654      </h1>
655      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
656      </h2>
657      <table summary="Normative References">       
658         <tr>
659            <td class="reference"><b id="Part1">[Part1]</b></td>
660            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), May&nbsp;2008.
661            </td>
662         </tr>
663         <tr>
664            <td class="reference"><b id="Part6">[Part6]</b></td>
665            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), May&nbsp;2008.
666            </td>
667         </tr>
668         <tr>
669            <td class="reference"><b id="RFC2119">[RFC2119]</b></td>
670            <td class="top"><a 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.
671            </td>
672         </tr>
673         <tr>
674            <td class="reference"><b id="RFC2617">[RFC2617]</b></td>
675            <td class="top"><a title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a title="Verisign Inc.">Hallam-Baker, P.M.</a>, <a title="AbiSource, Inc.">Hostetler, J.L.</a>, <a title="Agranat Systems, Inc.">Lawrence, S.D.</a>, <a title="Microsoft Corporation">Leach, P.J.</a>, Luotonen, A., and <a 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.
676            </td>
677         </tr>
678      </table>
679      <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References
680      </h2>
681      <table summary="Informative References"> 
682         <tr>
683            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
684            <td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a 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.
685            </td>
686         </tr>
687      </table>
688      <h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1>
689      <address class="vcard"><span class="vcardline"><span class="fn">Roy T. Fielding</span>
690            (editor)
691            <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><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>
692      <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><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>
693      <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><span class="email">JeffMogul@acm.org</span></a></span></address>
694      <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><span class="email">henrikn@microsoft.com</span></a></span></address>
695      <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><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>
696      <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><span class="email">paulle@microsoft.com</span></a></span></address>
697      <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><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>
698      <address class="vcard"><span class="vcardline"><span class="fn">Yves Lafon</span>
699            (editor)
700            <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><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>
701      <address class="vcard"><span class="vcardline"><span class="fn">Julian F. Reschke</span>
702            (editor)
703            <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><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>
704      <h1 id="rfc.section.A"><a href="#rfc.section.A">A.</a>&nbsp;<a id="compatibility" href="#compatibility">Compatibility with Previous Versions</a></h1>
705      <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>
706      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;Change Log (to be removed by RFC Editor before publication)
707      </h1>
708      <h2 id="rfc.section.B.1"><a href="#rfc.section.B.1">B.1</a>&nbsp;Since RFC2616
709      </h2>
710      <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>.
711      </p>
712      <h2 id="rfc.section.B.2"><a href="#rfc.section.B.2">B.2</a>&nbsp;Since draft-ietf-httpbis-p7-auth-00
713      </h2>
714      <p id="rfc.section.B.2.p.1">Closed issues: </p>
715      <ul>
716         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35</a>&gt;: "Normative and Informative references"
717         </li>
718      </ul>
719      <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a>&nbsp;Since draft-ietf-httpbis-p7-auth-01
720      </h2>
721      <p id="rfc.section.B.3.p.1">Ongoing work on ABNF conversion (&lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/36</a>&gt;):
722      </p>
723      <ul>
724         <li>Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.</li>
725         <li>Add explicit references to BNF syntax and rules imported from other parts of the specification.</li>
726      </ul>
727      <h2 id="rfc.section.B.4"><a href="#rfc.section.B.4">B.4</a>&nbsp;Since draft-ietf-httpbis-p7-auth-02
728      </h2>
729      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
730      <p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the
731         authors retain all their rights.
732      </p>
733      <p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION
734         HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE
735         DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN
736         WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
737      </p>
738      <h1><a id="rfc.ipr" href="#rfc.ipr">Intellectual Property</a></h1>
739      <p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might
740         be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any
741         license under such rights might or might not be available; nor does it represent that it has made any independent effort to
742         identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and
743         BCP 79.
744      </p>
745      <p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result
746         of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users
747         of this specification can be obtained from the IETF on-line IPR repository at &lt;<a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>&gt;.
748      </p>
749      <p>The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary
750         rights that may cover technology that may be required to implement this standard. Please address the information to the IETF
751         at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.
752      </p>
753      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
754      <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> 
755      </p>
756      <div class="print2col">
757         <ul class="ind">
758            <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind">
759                  <li class="indline1">401 Unauthorized (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.2"><b>3.1</b></a></li>
760                  <li class="indline1">407 Proxy Authentication Required (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.3"><b>3.2</b></a></li>
761               </ul>
762            </li>
763            <li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind">
764                  <li class="indline1">Authorization header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.authorization.1">3.1</a>, <a class="iref" href="#rfc.iref.a.1"><b>4.1</b></a></li>
765               </ul>
766            </li>
767            <li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b>G</b></a><ul class="ind">
768                  <li class="indline1"><tt>Grammar</tt>&nbsp;&nbsp;
769                     <ul class="ind">
770                        <li class="indline1"><tt>Authorization</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.3"><b>4.1</b></a></li>
771                        <li class="indline1"><tt>challenge</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.1"><b>2</b></a></li>
772                        <li class="indline1"><tt>credentials</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.2"><b>2</b></a></li>
773                        <li class="indline1"><tt>Proxy-Authenticate</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.4"><b>4.2</b></a></li>
774                        <li class="indline1"><tt>Proxy-Authorization</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.5"><b>4.3</b></a></li>
775                        <li class="indline1"><tt>WWW-Authenticate</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.g.6"><b>4.4</b></a></li>
776                     </ul>
777                  </li>
778               </ul>
779            </li>
780            <li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind">
781                  <li class="indline1">Headers&nbsp;&nbsp;
782                     <ul class="ind">
783                        <li class="indline1">Authorization&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.authorization.1">3.1</a>, <a class="iref" href="#rfc.iref.h.1"><b>4.1</b></a></li>
784                        <li class="indline1">Proxy-Authenticate&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>4.2</b></a></li>
785                        <li class="indline1">Proxy-Authorization&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>4.3</b></a></li>
786                        <li class="indline1">WWW-Authenticate&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>4.4</b></a></li>
787                     </ul>
788                  </li>
789               </ul>
790            </li>
791            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
792                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#Part1"><b>8.1</b></a><ul class="ind">
793                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a></li>
794                     </ul>
795                  </li>
796                  <li class="indline1"><em>Part6</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">4.1</a>, <a class="iref" href="#Part6"><b>8.1</b></a><ul class="ind">
797                        <li class="indline1"><em>Section 9</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part6.1">4.1</a></li>
798                     </ul>
799                  </li>
800                  <li class="indline1">Proxy-Authenticate header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a class="iref" href="#rfc.iref.p.1"><b>4.2</b></a></li>
801                  <li class="indline1">Proxy-Authorization header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a class="iref" href="#rfc.iref.p.2"><b>4.3</b></a></li>
802               </ul>
803            </li>
804            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
805                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>8.1</b></a></li>
806                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>
807                  <li class="indline1"><em>RFC2617</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2617.1">1</a>, <a class="iref" href="#rfc.xref.RFC2617.2">1</a>, <a class="iref" href="#rfc.xref.RFC2617.3">2</a>, <a class="iref" href="#rfc.xref.RFC2617.4">2</a>, <a class="iref" href="#rfc.xref.RFC2617.5">3.1</a>, <a class="iref" href="#rfc.xref.RFC2617.6">3.2</a>, <a class="iref" href="#rfc.xref.RFC2617.7">4.1</a>, <a class="iref" href="#rfc.xref.RFC2617.8">4.2</a>, <a class="iref" href="#rfc.xref.RFC2617.9">4.3</a>, <a class="iref" href="#rfc.xref.RFC2617.10">4.4</a>, <a class="iref" href="#RFC2617"><b>8.1</b></a><ul class="ind">
808                        <li class="indline1"><em>Section 1.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2617.3">2</a>, <a class="iref" href="#rfc.xref.RFC2617.4">2</a></li>
809                     </ul>
810                  </li>
811               </ul>
812            </li>
813            <li class="indline0"><a id="rfc.index.S" href="#rfc.index.S"><b>S</b></a><ul class="ind">
814                  <li class="indline1">Status Codes&nbsp;&nbsp;
815                     <ul class="ind">
816                        <li class="indline1">401 Unauthorized&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a></li>
817                        <li class="indline1">407 Proxy Authentication Required&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a></li>
818                     </ul>
819                  </li>
820               </ul>
821            </li>
822            <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind">
823                  <li class="indline1">WWW-Authenticate header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a class="iref" href="#rfc.iref.w.1"><b>4.4</b></a></li>
824               </ul>
825            </li>
826         </ul>
827      </div>
828   </body>
829</html>
Note: See TracBrowser for help on using the repository browser.