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