Changeset 1354 for draft-ietf-httpbis/latest/p7-auth.html
- Timestamp:
- 26/07/11 15:44:53 (12 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p7-auth.html
r1350 r1354 359 359 } 360 360 @bottom-center { 361 content: "Expires January 2 6, 2012";361 content: "Expires January 27, 2012"; 362 362 } 363 363 @bottom-right { … … 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2011-07-2 5">406 <meta name="dct.issued" scheme="ISO8601" content="2011-07-26"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: January 2 6, 2012</td>437 <td class="left">Expires: January 27, 2012</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">July 2 5, 2011</td>490 <td class="right">July 26, 2011</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on January 2 6, 2012.</p>518 <p>This Internet-Draft will expire on January 27, 2012.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 679 679 <p id="rfc.section.2.1.p.15">Proxies <em class="bcp14">MUST</em> forward the WWW-Authenticate and Authorization headers unmodified and follow the rules found in <a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section 4.1</a>. 680 680 </p> 681 <div id="rfc.iref.p.1"></div> 682 <div id="rfc.iref.r.1"></div> 681 683 <h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="protection.space" href="#protection.space">Protection Space (Realm)</a></h2> 682 <p id="rfc.section.2.2.p.1">The authentication parameter realm is defined for all authentication schemes:</p>683 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.r. 1"></span><span id="rfc.iref.r.2"></span> realm = "realm" "=" realm-value684 <p id="rfc.section.2.2.p.1">The authentication parameter realm is reserved for use by authentication schemes that wish to indicate the scope of protection:</p> 685 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.r.2"></span><span id="rfc.iref.r.3"></span> realm = "realm" "=" realm-value 684 686 realm-value = quoted-string 685 </pre><p id="rfc.section.2.2.p.3">The realm directive (case-insensitive) is required for all authentication schemes that issue a challenge. The realm value 686 (case-sensitive), in combination with the canonical root URI (the scheme and authority components of the effective request 687 URI; see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) of the server being accessed, defines the protection space. These realms allow the protected resources on a server to be 688 partitioned into a set of protection spaces, each with its own authentication scheme and/or authorization database. The realm 689 value is a string, generally assigned by the origin server, which can have additional semantics specific to the authentication 690 scheme. Note that there can be multiple challenges with the same auth-scheme but different realms. 687 </pre><p id="rfc.section.2.2.p.3">A <dfn>protection space</dfn> is defined by the canonical root URI (the scheme and authority components of the effective request URI; see <a href="p1-messaging.html#effective.request.uri" title="Effective Request URI">Section 4.3</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>) of the server being accessed, in combination with the realm value if present. These realms allow the protected resources 688 on a server to be partitioned into a set of protection spaces, each with its own authentication scheme and/or authorization 689 database. The realm value is a string, generally assigned by the origin server, which can have additional semantics specific 690 to the authentication scheme. Note that there can be multiple challenges with the same auth-scheme but different realms. 691 691 </p> 692 692 <p id="rfc.section.2.2.p.4">The protection space determines the domain over which credentials can be automatically applied. If a prior request has been … … 708 708 </p> 709 709 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1> 710 <div id="rfc.iref. 6"></div>710 <div id="rfc.iref.8"></div> 711 711 <div id="rfc.iref.s.1"></div> 712 712 <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> … … 716 716 information. 717 717 </p> 718 <div id="rfc.iref. 7"></div>718 <div id="rfc.iref.9"></div> 719 719 <div id="rfc.iref.s.2"></div> 720 720 <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> … … 748 748 </li> 749 749 </ol> 750 <div id="rfc.iref.p. 1"></div>750 <div id="rfc.iref.p.2"></div> 751 751 <div id="rfc.iref.h.2"></div> 752 752 <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> … … 759 759 header field. 760 760 </p> 761 <div id="rfc.iref.p. 2"></div>761 <div id="rfc.iref.p.3"></div> 762 762 <div id="rfc.iref.h.3"></div> 763 763 <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> … … 1085 1085 <p id="rfc.section.C.16.p.1">None.</p> 1086 1086 <h2 id="rfc.section.C.17"><a href="#rfc.section.C.17">C.17</a> <a id="changes.since.15" href="#changes.since.15">Since draft-ietf-httpbis-p7-auth-15</a></h2> 1087 <p id="rfc.section.C.17.p.1">None yet.</p> 1087 <p id="rfc.section.C.17.p.1">Closed issues: </p> 1088 <ul> 1089 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/177">http://tools.ietf.org/wg/httpbis/trac/ticket/177</a>>: "Realm required on challenges" 1090 </li> 1091 </ul> 1088 1092 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1089 1093 <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.W">W</a> … … 1092 1096 <ul class="ind"> 1093 1097 <li><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul> 1094 <li>401 Unauthorized (status code) <a href="#rfc.iref. 6"><b>3.1</b></a>, <a href="#rfc.xref.status.401.1">5.2</a></li>1095 <li>407 Proxy Authentication Required (status code) <a href="#rfc.iref. 7"><b>3.2</b></a>, <a href="#rfc.xref.status.407.1">5.2</a></li>1098 <li>401 Unauthorized (status code) <a href="#rfc.iref.8"><b>3.1</b></a>, <a href="#rfc.xref.status.401.1">5.2</a></li> 1099 <li>407 Proxy Authentication Required (status code) <a href="#rfc.iref.9"><b>3.2</b></a>, <a href="#rfc.xref.status.407.1">5.2</a></li> 1096 1100 </ul> 1097 1101 </li> … … 1140 1144 </ul> 1141 1145 </li> 1142 <li>Proxy-Authenticate header field <a href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a href="#rfc.iref.p.1"><b>4.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">5.3</a></li> 1143 <li>Proxy-Authorization header field <a href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a href="#rfc.iref.p.2"><b>4.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">5.3</a></li> 1146 <li>Protection Space <a href="#rfc.iref.p.1">2.2</a></li> 1147 <li>Proxy-Authenticate header field <a href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a href="#rfc.iref.p.2"><b>4.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">5.3</a></li> 1148 <li>Proxy-Authorization header field <a href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a href="#rfc.iref.p.3"><b>4.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">5.3</a></li> 1144 1149 </ul> 1145 1150 </li> 1146 1151 <li><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul> 1147 <li><tt>realm</tt> <a href="#rfc.iref.r.1"><b>2.2</b></a></li> 1148 <li><tt>realm-value</tt> <a href="#rfc.iref.r.2"><b>2.2</b></a></li> 1152 <li>Realm <a href="#rfc.iref.r.1">2.2</a></li> 1153 <li><tt>realm</tt> <a href="#rfc.iref.r.2"><b>2.2</b></a></li> 1154 <li><tt>realm-value</tt> <a href="#rfc.iref.r.3"><b>2.2</b></a></li> 1149 1155 <li><em>RFC2119</em> <a href="#rfc.xref.RFC2119.1">1.1</a>, <a href="#RFC2119"><b>8.1</b></a></li> 1150 1156 <li><em>RFC2616</em> <a href="#rfc.xref.RFC2616.1">1</a>, <a href="#rfc.xref.RFC2616.2">7</a>, <a href="#RFC2616"><b>8.2</b></a>, <a href="#rfc.xref.RFC2616.3">C.1</a></li>
Note: See TracChangeset
for help on using the changeset viewer.