Changeset 698 for draft-ietf-httpbis/latest/p7-auth.html
- Timestamp:
- 26/09/09 10:09:09 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p7-auth.html
r697 r698 390 390 <meta name="DC.Creator" content="Reschke, J. F."> 391 391 <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 392 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-2 5">392 <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-09-26"> 393 393 <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"> 394 394 <meta name="DC.Description.Abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication."> … … 427 427 </tr> 428 428 <tr> 429 <td class="header left">Expires: March 29, 2010</td>429 <td class="header left">Expires: March 30, 2010</td> 430 430 <td class="header right">H. Frystyk</td> 431 431 </tr> … … 476 476 <tr> 477 477 <td class="header left"></td> 478 <td class="header right">September 2 5, 2009</td>478 <td class="header right">September 26, 2009</td> 479 479 </tr> 480 480 </table> … … 500 500 <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>>. 501 501 </p> 502 <p>This Internet-Draft will expire in March 29, 2010.</p>502 <p>This Internet-Draft will expire in March 30, 2010.</p> 503 503 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 504 504 <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 627 627 <div id="rfc.iref.h.1"></div> 628 628 <h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> <a id="header.authorization" href="#header.authorization">Authorization</a></h2> 629 <p id="rfc.section.3.1.p.1"> A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does630 so by including an "Authorization" request-header field with the request. The field value consists of credentials containing631 the authentication information of the user agentfor the realm of the resource being requested.629 <p id="rfc.section.3.1.p.1">The "Authorization" request-header field allows a user agent to authenticate itself with a server -- usually, but not necessary, 630 after receiving a 401 (Unauthorized) response. Its value consists of credentials containing information of the user agent 631 for the realm of the resource being requested. 632 632 </p> 633 633 <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span><span id="rfc.iref.g.4"></span> <a href="#header.authorization" class="smpl">Authorization</a> = "Authorization" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.authorization" class="smpl">Authorization-v</a> … … 652 652 <div id="rfc.iref.h.2"></div> 653 653 <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a> <a id="header.proxy-authenticate" href="#header.proxy-authenticate">Proxy-Authenticate</a></h2> 654 <p id="rfc.section.3.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 indicates655 the authentication scheme and parameters applicable to the proxy for this request-target.654 <p id="rfc.section.3.2.p.1">The "Proxy-Authenticate" response-header field consists of a challenge that indicates the authentication scheme and parameters 655 applicable to the proxy for this request-target. It <em class="bcp14">MUST</em> be included as part of a 407 (Proxy Authentication Required) response. 656 656 </p> 657 657 <div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.5"></span><span id="rfc.iref.g.6"></span> <a href="#header.proxy-authenticate" class="smpl">Proxy-Authenticate</a> = "Proxy-Authenticate" ":" <a href="#core.rules" class="smpl">OWS</a> … … 666 666 <h2 id="rfc.section.3.3"><a href="#rfc.section.3.3">3.3</a> <a id="header.proxy-authorization" href="#header.proxy-authorization">Proxy-Authorization</a></h2> 667 667 <p id="rfc.section.3.3.p.1">The "Proxy-Authorization" request-header field allows the client to identify itself (or its user) to a proxy which requires 668 authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the669 user agent for the proxyand/or realm of the resource being requested.668 authentication. Its value consists of credentials containing the authentication information of the user agent for the proxy 669 and/or realm of the resource being requested. 670 670 </p> 671 671 <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.7"></span><span id="rfc.iref.g.8"></span> <a href="#header.proxy-authorization" class="smpl">Proxy-Authorization</a> = "Proxy-Authorization" ":" <a href="#core.rules" class="smpl">OWS</a> … … 680 680 <div id="rfc.iref.h.4"></div> 681 681 <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a> <a id="header.www-authenticate" href="#header.www-authenticate">WWW-Authenticate</a></h2> 682 <p id="rfc.section.3.4.p.1">The "WWW-Authenticate" response-header field <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages. The field value consists of at least one challenge that indicates the683 a uthentication scheme(s) and parameters applicable to the request-target.682 <p id="rfc.section.3.4.p.1">The "WWW-Authenticate" response-header field consists of at least one challenge that indicates the authentication scheme(s) 683 and parameters applicable to the request-target. It <em class="bcp14">MUST</em> be included in 401 (Unauthorized) response messages. 684 684 </p> 685 685 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.9"></span><span id="rfc.iref.g.10"></span> <a href="#header.www-authenticate" class="smpl">WWW-Authenticate</a> = "WWW-Authenticate" ":" <a href="#core.rules" class="smpl">OWS</a> <a href="#header.www-authenticate" class="smpl">WWW-Authenticate-v</a>
Note: See TracChangeset
for help on using the changeset viewer.