You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@labs.apache.org by fi...@apache.org on 2007/10/09 02:43:07 UTC
svn commit: r583028 -
/labs/webarch/trunk/http/draft-fielding-http/p7-auth.html
Author: fielding
Date: Mon Oct 8 17:43:07 2007
New Revision: 583028
URL: http://svn.apache.org/viewvc?rev=583028&view=rev
Log:
HTTP/1.1, part 7: Authentication
Added:
labs/webarch/trunk/http/draft-fielding-http/p7-auth.html (with props)
Added: labs/webarch/trunk/http/draft-fielding-http/p7-auth.html
URL: http://svn.apache.org/viewvc/labs/webarch/trunk/http/draft-fielding-http/p7-auth.html?rev=583028&view=auto
==============================================================================
--- labs/webarch/trunk/http/draft-fielding-http/p7-auth.html (added)
+++ labs/webarch/trunk/http/draft-fielding-http/p7-auth.html Mon Oct 8 17:43:07 2007
@@ -0,0 +1,335 @@
+<!DOCTYPE html
+ PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html lang="en"><head profile="http://www.w3.org/2006/03/hcard"><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><title>HTTP/1.1, part 7: Authentication</title><style type="text/css" title="Xml2Rfc (sans serif)">
+a {
+ text-decoration: none;
+}
+a.smpl {
+ color: black;
+}
+a:hover {
+ text-decoration: underline;
+}
+a:active {
+ text-decoration: underline;
+}
+address {
+ margin-top: 1em;
+ margin-left: 2em;
+ font-style: normal;
+}
+body {
+ color: black;
+ font-family: verdana, helvetica, arial, sans-serif;
+ font-size: 10pt;
+}
+cite {
+ font-style: normal;
+}
+dd {
+ margin-right: 2em;
+}
+dl {
+ margin-left: 2em;
+}
+
+dl.empty dd {
+ margin-top: .5em;
+}
+dl p {
+ margin-left: 0em;
+}
+dt {
+ margin-top: .5em;
+}
+h1 {
+ font-size: 14pt;
+ line-height: 21pt;
+ page-break-after: avoid;
+}
+h1.np {
+ page-break-before: always;
+}
+h1 a {
+ color: #333333;
+}
+h2 {
+ font-size: 12pt;
+ line-height: 15pt;
+ page-break-after: avoid;
+}
+h2 a {
+ color: black;
+}
+h3 {
+ font-size: 10pt;
+ page-break-after: avoid;
+}
+h3 a {
+ color: black;
+}
+h4 {
+ font-size: 10pt;
+ page-break-after: avoid;
+}
+h4 a {
+ color: black;
+}
+h5 {
+ font-size: 10pt;
+ page-break-after: avoid;
+}
+h5 a {
+ color: black;
+}
+img {
+ margin-left: 3em;
+}
+li {
+ margin-left: 2em;
+ margin-right: 2em;
+}
+ol {
+ margin-left: 2em;
+ margin-right: 2em;
+}
+ol p {
+ margin-left: 0em;
+}
+p {
+ margin-left: 2em;
+ margin-right: 2em;
+}
+pre {
+ margin-left: 3em;
+ background-color: lightyellow;
+ padding: .25em;
+}
+pre.text2 {
+ border-style: dotted;
+ border-width: 1px;
+ background-color: #f0f0f0;
+ width: 69em;
+}
+pre.inline {
+ background-color: white;
+ padding: 0em;
+}
+pre.text {
+ border-style: dotted;
+ border-width: 1px;
+ background-color: #f8f8f8;
+ width: 69em;
+}
+pre.drawing {
+ border-style: solid;
+ border-width: 1px;
+ background-color: #f8f8f8;
+ padding: 2em;
+}
+table {
+ margin-left: 2em;
+}
+table.header {
+ width: 95%;
+ font-size: 10pt;
+ color: white;
+}
+td.top {
+ vertical-align: top;
+}
+td.topnowrap {
+ vertical-align: top;
+ white-space: nowrap;
+}
+td.header {
+ background-color: gray;
+ width: 50%;
+}
+td.reference {
+ vertical-align: top;
+ white-space: nowrap;
+ padding-right: 1em;
+}
+thead {
+ display:table-header-group;
+}
+ul.toc {
+ list-style: none;
+ margin-left: 1.5em;
+ margin-right: 0em;
+ padding-left: 0em;
+}
+li.tocline0 {
+ line-height: 150%;
+ font-weight: bold;
+ font-size: 10pt;
+ margin-left: 0em;
+ margin-right: 0em;
+}
+li.tocline1 {
+ line-height: normal;
+ font-weight: normal;
+ font-size: 9pt;
+ margin-left: 0em;
+ margin-right: 0em;
+}
+li.tocline2 {
+ font-size: 0pt;
+}
+ul p {
+ margin-left: 0em;
+}
+ul.ind {
+ list-style: none;
+ margin-left: 1.5em;
+ margin-right: 0em;
+ padding-left: 0em;
+}
+li.indline0 {
+ font-weight: bold;
+ line-height: 200%;
+ margin-left: 0em;
+ margin-right: 0em;
+}
+li.indline1 {
+ font-weight: normal;
+ line-height: 150%;
+ margin-left: 0em;
+ margin-right: 0em;
+}
+.bcp14 {
+ font-style: normal;
+ text-transform: lowercase;
+ font-variant: small-caps;
+}
+.comment {
+ background-color: yellow;
+}
+.center {
+ text-align: center;
+}
+.error {
+ color: red;
+ font-style: italic;
+ font-weight: bold;
+}
+.figure {
+ font-weight: bold;
+ text-align: center;
+ font-size: 9pt;
+}
+.filename {
+ color: #333333;
+ font-weight: bold;
+ font-size: 12pt;
+ line-height: 21pt;
+ text-align: center;
+}
+.fn {
+ font-weight: bold;
+}
+.hidden {
+ display: none;
+}
+.left {
+ text-align: left;
+}
+.right {
+ text-align: right;
+}
+.title {
+ color: #990000;
+ font-size: 18pt;
+ line-height: 18pt;
+ font-weight: bold;
+ text-align: center;
+ margin-top: 36pt;
+}
+.vcardline {
+ display: block;
+}
+.warning {
+ font-size: 14pt;
+ background-color: yellow;
+}
+
+
+@media print {
+ .noprint {
+ display: none;
+ }
+
+ a {
+ color: black;
+ text-decoration: none;
+ }
+
+ table.header {
+ width: 90%;
+ }
+
+ td.header {
+ width: 50%;
+ color: black;
+ background-color: white;
+ vertical-align: top;
+ font-size: 12pt;
+ }
+
+ ul.toc a::after {
+ content: leader('.') target-counter(attr(href), page);
+ }
+
+ a.iref {
+ content: target-counter(attr(href), page);
+ }
+
+ .print2col {
+ column-count: 2;
+ -moz-column-count: 2;
+ column-fill: auto;
+ }
+}
+
+@page {
+ @top-left {
+ content: "INTERNET DRAFT";
+ }
+ @top-right {
+ content: "September 2007";
+ }
+ @top-center {
+ content: "HTTP/1.1";
+ }
+ @bottom-left {
+ content: "Fielding, et al.";
+ }
+ @bottom-center {
+ content: "Standards Track";
+ }
+ @bottom-right {
+ content: "[Page " counter(page) "]";
+ }
+}
+
+@page:first {
+ @top-left {
+ content: normal;
+ }
+ @top-right {
+ content: normal;
+ }
+ @top-center {
+ content: normal;
+ }
+}
+</style><link rel="Contents" href="#rfc.toc"><link rel="Author" href="#rfc.authors"><link rel="Copyright" href="#rfc.copyright"><link rel="Index" href="#rfc.index"><link rel="Chapter" title="1 Introduction" href="#rfc.section.1"><link rel="Chapter" title="2 Header Field Definitions" href="#rfc.section.2"><link rel="Chapter" title="3 Security Considerations" href="#rfc.section.3"><link rel="Chapter" title="4 Acknowledgments" href="#rfc.section.4"><link rel="Chapter" href="#rfc.section.5" title="5 References"><meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.346, 2007/10/07 13:54:24, XSLT vendor: SAXON 8.5.1 from Saxonica http://www.saxonica.com/"><link rel="schema.DC" href="http://purl.org/dc/elements/1.1/"><meta name="DC.Creator" content="Fielding, R."><meta name="DC.Creator" content="Gettys, J."><meta name="DC.Creator" content="Mogul, J."><meta name="DC.Creator" content="Frystyk, H."><meta name="DC.Creator" content="Masinter, L."><met
a name="DC.Creator" content="Leach, P."><meta name="DC.Creator" content="Berners-Lee, T."><meta name="DC.Identifier" content="urn:ietf:id:draft-fielding-http-p7-auth-00"><meta name="DC.Date.Issued" scheme="ISO8601" content="2007-09"><meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2068"><meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616"><meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2617"><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 eight-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, updates RFC 2616 and RFC 2617. Part 7 defines HTTP Authentication."></head><body><table summary="header information" class="header" border="0" cellpadding="1" cellspa
cing="1"><tr><td class="header left">Network Working Group</td><td class="header right">R. Fielding</td></tr><tr><td class="header left">Internet Draft</td><td class="header right">UC Irvine</td></tr><tr><td class="header left">
+ <draft-fielding-http-p7-auth-00>
+ </td><td class="header right">J. Gettys</td></tr><tr><td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2068">2068</a>,
+ <a href="http://tools.ietf.org/html/rfc2616">2616</a>,
+ <a href="http://tools.ietf.org/html/rfc2617">2617</a> (if approved)</td><td class="header right">Compaq/W3C</td></tr><tr><td class="header left">Intended status: Standards Track</td><td class="header right">J. Mogul</td></tr><tr><td class="header left">Expires: March 2008</td><td class="header right">Compaq</td></tr><tr><td class="header left"></td><td class="header right">H. Frystyk</td></tr><tr><td class="header left"></td><td class="header right">W3C/MIT</td></tr><tr><td class="header left"></td><td class="header right">L. Masinter</td></tr><tr><td class="header left"></td><td class="header right">Xerox</td></tr><tr><td class="header left"></td><td class="header right">P. Leach</td></tr><tr><td class="header left"></td><td class="header right">Microsoft</td></tr><tr><td class="header left"></td><td class="header right">T. Berners-Lee</td></tr><tr><td class="header left"></td><td class="header right">W3C/MIT</td></tr><tr><td class="header left"></td><td class="header
right">September 2007</td></tr></table><p class="title">HTTP/1.1, part 7: Authentication<br><span class="filename">draft-fielding-http-p7-auth-00</span></p><h1><a id="rfc.status" href="#rfc.status">Status of this Memo</a></h1><p>This document is an Internet-Draft and is subject to all provisions of section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she become aware will be disclosed, in accordance with RFC 3668.</p><p>Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts.</p><p>Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as referenc
e material or to cite them other than as “work in progress”.</p><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>>.</p><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>>.</p><p>This Internet-Draft will expire in March 2008.</p><h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1><p>Copyright © The IETF Trust (2007). All Rights Reserved.</p><h1 id="rfc.abstract"><a href="#rfc.abstract">Abstract</a></h1> <p>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 eight-part specification that defines the protocol referred to as
"HTTP/1.1" and, taken together, updates RFC 2616 and RFC 2617. Part 7 defines HTTP Authentication.</p> <hr class="noprint"><h1 class="np" id="rfc.toc"><a href="#rfc.toc">Table of Contents</a></h1><ul class="toc"><li class="tocline0">1. <a href="#rfc.section.1">Introduction</a></li><li class="tocline0">2. <a href="#rfc.section.2">Header Field Definitions</a><ul class="toc"><li class="tocline1">2.1 <a href="#header.authorization">Authorization</a></li><li class="tocline1">2.2 <a href="#header.proxy-authenticate">Proxy-Authenticate</a></li><li class="tocline1">2.3 <a href="#header.proxy-authorization">Proxy-Authorization</a></li><li class="tocline1">2.4 <a href="#header.www-authenticate">WWW-Authenticate</a></li></ul></li><li class="tocline0">3. <a href="#rfc.section.3">Security Considerations</a><ul class="toc"><li class="tocline1">3.1 <a hre
f="#rfc.section.3.1">Authentication Credentials and Idle Clients</a></li></ul></li><li class="tocline0">4. <a href="#rfc.section.4">Acknowledgments</a></li><li class="tocline0">5. <a href="#rfc.references">References</a></li><li class="tocline0"><a href="#rfc.authors">Authors' Addresses</a></li><li class="tocline0"><a href="#rfc.ipr">Intellectual Property and Copyright Statements</a></li><li class="tocline0"><a href="#rfc.index">Index</a></li></ul><h1 id="rfc.section.1" class="np"><a href="#rfc.section.1">1.</a> Introduction</h1><p id="rfc.section.1.p.1">This document will define aspects of HTTP related to access control and authentication. Right now it only includes the extracted relevant sections of <a href="#RFC2616">RFC 2616</a> <cite title="Hypertext Transfer Protocol -- HTTP/1.1" id="rfc.xref.RFC2616.1">[1]</cite> with only minor edits.</p><p id="rfc.section.1.p.2">HTTP provides several <em class="bcp14">OPTIONAL</em> challenge-re
sponse authentication mechanisms which can be used by a server to challenge a client request and by a client to provide authentication information. The general framework for access authentication, and the specification of "basic" and "digest" authentication, are specified in "HTTP Authentication: Basic and Digest Access Authentication" <a href="#RFC2617" id="rfc.xref.RFC2617.1"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[2]</cite></a>. This specification adopts the definitions of "challenge" and "credentials" from that specification.</p><h1 id="rfc.section.2"><a href="#rfc.section.2">2.</a> Header Field Definitions</h1><p id="rfc.section.2.p.1">This section defines the syntax and semantics of all standard HTTP/1.1 header fields. For entity-header fields, both sender and recipient refer to either the client or the server, depending on who sends and who receives the entity.</p><div id="rfc.iref.a.1"></div><div id="rfc.iref.h.1"></div><h2 id=
"rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="header.authorization" href="#header.authorization">Authorization</a></h2><p id="rfc.section.2.1.p.1">A user agent that wishes to authenticate itself with a server-- usually, but not necessarily, after receiving a 401 response--does so by including an Authorization request-header field with the request. The Authorization field value consists of credentials containing the authentication information of the user agent for the realm of the resource being requested.</p><div id="rfc.figure.u.1"></div><pre class="inline"><span id="rfc.iref.g.1"></span> Authorization = "Authorization" ":" credentials
+</pre><p id="rfc.section.2.1.p.3">HTTP access authentication is described 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">[2]</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, such as credentials that vary according to a challenge value or using synchronized clocks).</p><p id="rfc.section.2.1.p.4">When a shared cache (see [Part 6]) 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:</p><p id="rfc.section.2.1.p.5"> </p><ol><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 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.</li><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 the new request.</li><li>If the response includes the "public" cache-control directive, it <em class="bcp14">MAY</em> be returned
in reply to any subsequent request.</li></ol><div id="rfc.iref.p.1"></div><div id="rfc.iref.h.2"></div><h2 id="rfc.section.2.2"><a href="#rfc.section.2.2">2.2</a> <a id="header.proxy-authenticate" href="#header.proxy-authenticate">Proxy-Authenticate</a></h2><p id="rfc.section.2.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 the authentication scheme and parameters applicable to the proxy for this Request-URI.</p><div id="rfc.figure.u.2"></div><pre class="inline"><span id="rfc.iref.g.2"></span> Proxy-Authenticate = "Proxy-Authenticate" ":" 1#challenge
+</pre><p id="rfc.section.2.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.3"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[2]</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 them from the downstream client, which in some circumstances will appear as if the proxy is forwarding the Proxy-Authenticate header field.</p><div id="rfc.iref.p.2"></div><div id="rfc.iref.h.3"></div><h2 id="rfc.section.2.3"><a href="#rfc.section.2.3">2.3</a> <a id="header.proxy-authorization" href="#header.proxy-authorization">Proxy-Authorization</a></h2><p id="rfc.section.2.3.p.1">The Proxy-Authorization request-header field allows t
he client to identify itself (or its user) to a proxy which requires authentication. The Proxy-Authorization field value consists of credentials containing the authentication information of the user agent for the proxy and/or realm of the resource being requested.</p><div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.g.3"></span> Proxy-Authorization = "Proxy-Authorization" ":" credentials
+</pre><p id="rfc.section.2.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.4"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[2]</cite></a>. Unlike Authorization, the Proxy-Authorization header field applies only to the next outbound proxy that demanded authentication using the Proxy-Authenticate field. When multiple proxies are used in a chain, the Proxy-Authorization header field is consumed 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 authenticate a given request.</p><div id="rfc.iref.w.1"></div><div id="rfc.iref.h.4"></div><h2 id="rfc.section.2.4"><a href="#rfc.section.2.4">2.4</a> <a id="header.www-authenticate" href="#header.www-authenticate"
>WWW-Authenticate</a></h2><p id="rfc.section.2.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 authentication scheme(s) and parameters applicable to the Request-URI.</p><div id="rfc.figure.u.4"></div><pre class="inline"><span id="rfc.iref.g.4"></span> WWW-Authenticate = "WWW-Authenticate" ":" 1#challenge
+</pre><p id="rfc.section.2.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.5"><cite title="HTTP Authentication: Basic and Digest Access Authentication">[2]</cite></a>. User agents are advised to take special care in parsing the WWW-Authenticate field value as it might contain more than one challenge, or if more than one WWW-Authenticate header field is provided, the contents of a challenge itself can contain a comma-separated list of authentication parameters.</p><h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> Security Considerations</h1><p id="rfc.section.3.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1 as described by this document. The discussion does not include definitive solutions to the problems revealed, though it does make some suggestions for reducing se
curity risks.</p><h2 id="rfc.section.3.1"><a href="#rfc.section.3.1">3.1</a> Authentication Credentials and Idle Clients</h2><p id="rfc.section.3.1.p.1">Existing HTTP clients and user agents typically retain authentication information indefinitely. HTTP/1.1. does not provide a method for a server to direct clients to discard these cached credentials. This is a significant defect that requires further extensions to HTTP. Circumstances under which credential caching can interfere with the application's security model include but are not limited to: </p><ul><li>Clients which have been idle for an extended period following which the server might wish to cause the client to reprompt the user for credentials.</li><li>Applications which include a session termination indication (such as a `logout' or `commit' button on a page) after which the server side of the application `knows' that there is no further reason for the client to retain the credentials.</li></ul><p id="rfc.sect
ion.3.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 use of password protection in screen savers, idle time-outs, and other methods which mitigate the security problems inherent in this problem. In particular, user agents which cache credentials are encouraged to provide a readily accessible mechanism for discarding cached credentials under user control.</p><h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a> Acknowledgments</h1><p id="rfc.section.4.p.1">Based on an XML translation of RFC 2616 by Julian Reschke.</p><h1 id="rfc.references"><a href="#rfc.section.5" id="rfc.section.5">5.</a> References</h1><table summary="References"> <tr><td class="reference"><b id="RFC2616">[1]</b></td><td class="top"><a title="University of California, Irvine">Fielding, R.</a>, <a title="W3C">Gettys, J.</a>, <a title="Compaq Computer Corporation">Mogul, J.</a>, <a title="MIT Laboratory for Computer Scien
ce">Frystyk, H.</a>, <a title="Xerox Corporation">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, and <a title="W3C">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2616">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC 2616, June 1999.</td></tr> <tr><td class="reference"><b id="RFC2617">[2]</b></td><td class="top"><a title="Northwestern University, Department of Mathematics">Franks, J.</a>, <a title="Verisign Inc.">Hallam-Baker, P.M.</a>, <a title="AbiSource, Inc.">Hostetler, J.L.</a>, <a title="Agranat Systems, Inc.">Lawrence, S.D.</a>, <a title="Microsoft Corporation">Leach, P.J.</a>, Luotonen, A., and <a title="Open Market, Inc.">L. Stewart</a>, “<a href="http://tools.ietf.org/html/rfc2617">HTTP Authentication: Basic and Digest Access Authentication</a>”, RFC 2617, June 1999.</td></tr> </table><h1 id="rfc.authors"><a href="#rfc.authors">Authors' Addresses</a></h1><address class="vcard"><span clas
s="vcardline"><span class="fn">Roy T. Fielding</span><span class="n hidden"><span class="family-name">Fielding</span><span class="given-name">Roy T.</span></span></span><span class="org vcardline">Department of Information and Computer Science</span><span class="adr"><span class="street-address vcardline">University of California, Irvine</span><span class="vcardline"><span class="locality">Irvine</span>, <span class="region">CA</span> <span class="postal-code">92697-3425</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(949)824-1715"><span class="value">+1(949)824-1715</span></a></span><span class="vcardline">EMail: <a><span class="email">fielding@ics.uci.edu</span></a></span></address><address class="vcard"><span class="vcardline"><span class="fn">James Gettys</span><span class="n hidden"><span class="family-name">Gettys</span><span class="given-name">James</span></span></span><span class="org vcardline">World Wide Web Conso
rtium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMail: <a><span class="email">jg@w3.org</span></a></span></address><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">Compaq Computer Corporation</span><span class="adr"><span class="street-address vcardline">Western Research Laboratory</span><span class="street-address vcardline">250 University Aven
ue</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94305</span></span></span><span class="vcardline">EMail: <a><span class="email">mogul@wrl.dec.com</span></a></span></address><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">World Wide Web Consortium</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type">Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMa
il: <a><span class="email">frystyk@w3.org</span></a></span></address><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">Xerox Corporation</span><span class="adr"><span class="street-address vcardline">MIT Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">3333 Coyote Hill Road</span><span class="vcardline"><span class="locality">Palo Alto</span>, <span class="region">CA</span> <span class="postal-code">94034</span></span></span><span class="vcardline">EMail: <a><span class="email">masinter@parc.xerox.com</span></a></span></address><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">Microsof
t 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><span class="email">paulle@microsoft.com</span></a></span></address><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 Laboratory for Computer Science, NE43-356</span><span class="street-address vcardline">545 Technology Square</span><span class="vcardline"><span class="locality">Cambridge</span>, <span class="region">MA</span> <span class="postal-code">02139</span></span></span><span class="vcardline tel"><span class="type"
>Fax</span>: <a href="fax:+1(617)258-8682"><span class="value">+1(617)258-8682</span></a></span><span class="vcardline">EMail: <a><span class="email">timbl@w3.org</span></a></span></address><h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1><p>Copyright © The IETF Trust (2007).</p><p>This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.</p><p>This document and the information contained herein are provided on an “AS IS” basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.</p><h1><a id="r
fc.ipr" href="#rfc.ipr">Intellectual Property</a></h1><p>The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.</p><p>Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users 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>>.</p><p>The IETF invites any int
erested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at <a href="mailto:ietf-ipr@ietf.org">ietf-ipr@ietf.org</a>.</p><h1>Acknowledgement</h1><p>Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).</p><h1 id="rfc.index"><a href="#rfc.index">Index</a></h1><p class="noprint"><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.W">W</a> </p><div class="print2col"><ul class="ind"><li class="indline0"><a id="rfc.index.A" href="#rfc.index.A"><b>A</b></a><ul class="ind"><li class="indline1">Authorization header <a class="iref" href="#rfc.iref.a.1"><b>2.1</b></a></li></ul></li><li class="indline0"><a id="rfc.index.G" href="#rfc.index.G"><b
>G</b></a><ul class="ind"><li class="indline1"><tt>Grammar</tt> <ul class="ind"><li class="indline1"><tt>Authorization</tt> <a class="iref" href="#rfc.iref.g.1"><b>2.1</b></a></li><li class="indline1"><tt>Proxy-Authenticate</tt> <a class="iref" href="#rfc.iref.g.2"><b>2.2</b></a></li><li class="indline1"><tt>Proxy-Authorization</tt> <a class="iref" href="#rfc.iref.g.3"><b>2.3</b></a></li><li class="indline1"><tt>WWW-Authenticate</tt> <a class="iref" href="#rfc.iref.g.4"><b>2.4</b></a></li></ul></li></ul></li><li class="indline0"><a id="rfc.index.H" href="#rfc.index.H"><b>H</b></a><ul class="ind"><li class="indline1">Headers <ul class="ind"><li class="indline1">Authorization <a class="iref" href="#rfc.iref.h.1"><b>2.1</b></a></li><li class="indline1">Proxy-Authenticate <a class="iref" href="#rfc.iref.h.2"><b>2.2</b></a></li><li class="indline1">Proxy-Authorization <a class="iref
" href="#rfc.iref.h.3"><b>2.3</b></a></li><li class="indline1">WWW-Authenticate <a class="iref" href="#rfc.iref.h.4"><b>2.4</b></a></li></ul></li></ul></li><li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind"><li class="indline1">Proxy-Authenticate header <a class="iref" href="#rfc.iref.p.1"><b>2.2</b></a></li><li class="indline1">Proxy-Authorization header <a class="iref" href="#rfc.iref.p.2"><b>2.3</b></a></li></ul></li><li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind"><li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>5</b></a></li><li class="indline1"><em>RFC2617</em> <a class="iref" href="#rfc.xref.RFC2617.1">1</a>, <a class="iref" href="#rfc.xref.RFC2617.2">2.1</a>, <a class="iref" href="#rfc.xref.RFC2617.3">2.2</a>, <a class="iref" href="#rfc.xref.RFC2617.4">2.3</a>, <a
class="iref" href="#rfc.xref.RFC2617.5">2.4</a>, <a class="iref" href="#RFC2617"><b>5</b></a></li></ul></li><li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind"><li class="indline1">WWW-Authenticate header <a class="iref" href="#rfc.iref.w.1"><b>2.4</b></a></li></ul></li></ul></div></body></html>
\ No newline at end of file
Propchange: labs/webarch/trunk/http/draft-fielding-http/p7-auth.html
------------------------------------------------------------------------------
svn:eol-style = native
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@labs.apache.org
For additional commands, e-mail: commits-help@labs.apache.org