source: draft-ietf-httpbis/latest/p7-auth.xml @ 1894

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

Trim index.

  • Property svn:eol-style set to native
  • Property svn:mime-type set to text/xml
File size: 50.0 KB
Line 
1<?xml version="1.0" encoding="utf-8"?>
2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns='http://purl.org/net/xml2rfc/ext'>SHOULD NOT</bcp14>">
14  <!ENTITY ID-VERSION "latest">
15  <!ENTITY ID-MONTH "September">
16  <!ENTITY ID-YEAR "2012">
17  <!ENTITY mdash "&#8212;">
18  <!ENTITY Note "<x:h xmlns:x='http://purl.org/net/xml2rfc/ext'>Note:</x:h>">
19  <!ENTITY architecture                 "<xref target='Part1' x:rel='#architecture' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
20  <!ENTITY conformance                  "<xref target='Part1' x:rel='#conformance' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
21  <!ENTITY notation                     "<xref target='Part1' x:rel='#notation' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
22  <!ENTITY abnf-extension               "<xref target='Part1' x:rel='#abnf.extension' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
23  <!ENTITY acks                         "<xref target='Part1' x:rel='#acks' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
24  <!ENTITY whitespace                   "<xref target='Part1' x:rel='#whitespace' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
25  <!ENTITY field-components             "<xref target='Part1' x:rel='#field.components' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
26  <!ENTITY effective-request-uri        "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
27  <!ENTITY msg-orient-and-buffering     "<xref target='Part1' x:rel='#intermediaries' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
28  <!ENTITY end-to-end.and-hop-by-hop    "<xref target='Part1' x:rel='#end-to-end.and.hop-by-hop.header-fields' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
29  <!ENTITY status.403                   "<xref target='Part2' x:rel='#status.403' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
30  <!ENTITY shared-and-non-shared-caches "<xref target='Part6' x:rel='#shared.and.non-shared.caches' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
31]>
32<?rfc toc="yes" ?>
33<?rfc symrefs="yes" ?>
34<?rfc sortrefs="yes" ?>
35<?rfc compact="yes"?>
36<?rfc subcompact="no" ?>
37<?rfc linkmailto="no" ?>
38<?rfc editing="no" ?>
39<?rfc comments="yes"?>
40<?rfc inline="yes"?>
41<?rfc rfcedstyle="yes"?>
42<?rfc-ext allow-markup-in-artwork="yes" ?>
43<?rfc-ext include-references-in-index="yes" ?>
44<rfc obsoletes="2616" updates="2617" category="std" x:maturity-level="proposed"
45     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;"
46     xmlns:x='http://purl.org/net/xml2rfc/ext'>
47<x:link rel="prev" basename="p6-cache"/>
48<x:feedback template="mailto:ietf-http-wg@w3.org?subject={docname},%20%22{section}%22&amp;body=&lt;{ref}&gt;:"/>
49<front>
50
51  <title abbrev="HTTP/1.1 Authentication">Hypertext Transfer Protocol (HTTP/1.1): Authentication</title>
52
53  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
54    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
55    <address>
56      <postal>
57        <street>345 Park Ave</street>
58        <city>San Jose</city>
59        <region>CA</region>
60        <code>95110</code>
61        <country>USA</country>
62      </postal>
63      <email>fielding@gbiv.com</email>
64      <uri>http://roy.gbiv.com/</uri>
65    </address>
66  </author>
67
68  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
69    <organization abbrev="W3C">World Wide Web Consortium</organization>
70    <address>
71      <postal>
72        <street>W3C / ERCIM</street>
73        <street>2004, rte des Lucioles</street>
74        <city>Sophia-Antipolis</city>
75        <region>AM</region>
76        <code>06902</code>
77        <country>France</country>
78      </postal>
79      <email>ylafon@w3.org</email>
80      <uri>http://www.raubacapeu.net/people/yves/</uri>
81    </address>
82  </author>
83
84  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
85    <organization abbrev="greenbytes">greenbytes GmbH</organization>
86    <address>
87      <postal>
88        <street>Hafenweg 16</street>
89        <city>Muenster</city><region>NW</region><code>48155</code>
90        <country>Germany</country>
91      </postal>
92      <email>julian.reschke@greenbytes.de</email>
93      <uri>http://greenbytes.de/tech/webdav/</uri>
94    </address>
95  </author>
96
97  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
98  <workgroup>HTTPbis Working Group</workgroup>
99
100<abstract>
101<t>
102   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
103   distributed, collaborative, hypermedia information systems. This document
104   defines the HTTP Authentication framework.
105</t>
106</abstract>
107
108<note title="Editorial Note (To be removed by RFC Editor)">
109  <t>
110    Discussion of this draft takes place on the HTTPBIS working group
111    mailing list (ietf-http-wg@w3.org), which is archived at
112    <eref target="http://lists.w3.org/Archives/Public/ietf-http-wg/"/>.
113  </t>
114  <t>
115    The current issues list is at
116    <eref target="http://tools.ietf.org/wg/httpbis/trac/report/3"/> and related
117    documents (including fancy diffs) can be found at
118    <eref target="http://tools.ietf.org/wg/httpbis/"/>.
119  </t>
120  <t>
121    The changes in this draft are summarized in <xref target="changes.since.20"/>.
122  </t>
123</note>
124</front>
125<middle>
126<section title="Introduction" anchor="introduction">
127<t>
128   This document defines HTTP/1.1 access control and authentication. It
129   includes the relevant parts of <xref target="RFC2616" x:fmt="none">RFC 2616</xref>
130   with only minor changes (<xref target="RFC2616"/>), plus the general framework for HTTP authentication,
131   as previously defined in "HTTP Authentication: Basic and Digest Access
132   Authentication" (<xref target="RFC2617"/>).
133</t>
134<t>
135   HTTP provides several &OPTIONAL; challenge-response authentication
136   mechanisms which can be used by a server to challenge a client request and
137   by a client to provide authentication information. The "basic" and "digest"
138   authentication schemes continue to be specified in
139   <xref target="RFC2617" x:fmt="none">RFC 2617</xref>.
140</t>
141
142<section title="Conformance and Error Handling" anchor="conformance">
143<t>
144   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
145   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
146   document are to be interpreted as described in <xref target="RFC2119"/>.
147</t>
148<t>
149   Conformance criteria and considerations regarding error handling
150   are defined in &conformance;.
151</t>
152</section>
153
154<section title="Syntax Notation" anchor="notation">
155<t>
156   This specification uses the Augmented Backus-Naur Form (ABNF) notation
157   of <xref target="RFC5234"/> with the list rule extension defined in
158   &notation;. <xref target="imported.abnf"/> describes rules imported from
159   other documents. <xref target="collected.abnf"/> shows the collected ABNF
160   with the list rule expanded.
161</t>
162</section>
163</section>
164
165<section title="Access Authentication Framework" anchor="access.authentication.framework">
166
167<section title="Challenge and Response" anchor="challenge.and.response">
168  <x:anchor-alias value="auth-scheme"/>
169  <x:anchor-alias value="auth-param"/>
170  <x:anchor-alias value="token68"/>
171  <x:anchor-alias value="challenge"/>
172  <x:anchor-alias value="credentials"/>
173<t>
174   HTTP provides a simple challenge-response authentication mechanism
175   that can be used by a server to challenge a client request and by a
176   client to provide authentication information. It uses an extensible,
177   case-insensitive token to identify the authentication scheme, followed
178   by additional information necessary for achieving authentication via that
179   scheme. The latter can either be a comma-separated list of parameters or a
180   single sequence of characters capable of holding base64-encoded
181   information.
182</t>
183<t>
184   Parameters are name-value pairs where the name is matched case-insensitively,
185   and each parameter name &MUST; only occur once per challenge.
186</t>
187<figure><artwork type="abnf2616"><iref item="auth-scheme" primary="true"/><iref item="auth-param" primary="true"/><iref primary="true" item="Grammar" subitem="auth-scheme"/><iref primary="true" item="Grammar" subitem="auth-param"/><iref item="token68" primary="true"/><iref primary="true" item="Grammar" subitem="token68"/>
188  auth-scheme    = <x:ref>token</x:ref>
189 
190  auth-param     = <x:ref>token</x:ref> <x:ref>BWS</x:ref> "=" <x:ref>BWS</x:ref> ( <x:ref>token</x:ref> / <x:ref>quoted-string</x:ref> )
191
192  token68        = 1*( <x:ref>ALPHA</x:ref> / <x:ref>DIGIT</x:ref> /
193                       "-" / "." / "_" / "~" / "+" / "/" ) *"="
194</artwork></figure>
195<t>
196   The "token68" syntax allows the 66 unreserved URI characters (<xref target="RFC3986"/>),
197   plus a few others, so that it can hold a base64, base64url (URL and filename
198   safe alphabet), base32, or base16 (hex) encoding, with or without padding, but
199   excluding whitespace (<xref target="RFC4648"/>).
200</t>
201<t>
202   The <x:ref>401 (Unauthorized)</x:ref> response message is used by an origin server
203   to challenge the authorization of a user agent. This response &MUST;
204   include a <x:ref>WWW-Authenticate</x:ref> header field containing at least one
205   challenge applicable to the requested resource.
206</t>
207<t>  
208   The <x:ref>407 (Proxy Authentication Required)</x:ref> response message is
209   used by a proxy to challenge the authorization of a client and &MUST;
210   include a <x:ref>Proxy-Authenticate</x:ref> header field containing at least
211   one challenge applicable to the proxy for the requested resource.
212</t>
213<figure><artwork type="abnf2616"><iref item="challenge" primary="true"/><iref primary="true" item="Grammar" subitem="challenge"/>
214  <x:ref>challenge</x:ref>   = <x:ref>auth-scheme</x:ref> [ 1*<x:ref>SP</x:ref> ( <x:ref>token68</x:ref> / #<x:ref>auth-param</x:ref> ) ]
215</artwork></figure>
216<x:note>
217  <t>
218     &Note; User agents will need to take special care in parsing the
219     <x:ref>WWW-Authenticate</x:ref> and <x:ref>Proxy-Authenticate</x:ref>
220     header field values because they can contain more than one challenge, or
221     if more than one of each is provided, since the contents of a challenge
222     can itself contain a comma-separated list of authentication parameters.
223  </t>
224</x:note>
225<x:note>
226  <t>
227     &Note; Many clients fail to parse challenges containing unknown
228     schemes. A workaround for this problem is to list well-supported schemes
229     (such as "basic") first.<!-- see http://greenbytes.de/tech/tc/httpauth/#multibasicunknown2 -->
230  </t>
231</x:note>
232<t>
233   A user agent that wishes to authenticate itself with an origin server
234   &mdash; usually, but not necessarily, after receiving a <x:ref>401 (Unauthorized)</x:ref>
235   &mdash; can do so by including an <x:ref>Authorization</x:ref> header field with the
236   request.
237</t>
238<t>  
239   A client that wishes to authenticate itself with a proxy &mdash; usually,
240   but not necessarily, after receiving a <x:ref>407 (Proxy Authentication Required)</x:ref>
241   &mdash; can do so by including a <x:ref>Proxy-Authorization</x:ref> header field with the
242   request.
243</t>
244<t>
245   Both the <x:ref>Authorization</x:ref> field value and the <x:ref>Proxy-Authorization</x:ref> field value
246   contain the client's credentials for the realm of the resource being
247   requested, based upon a challenge received from the server (possibly at
248   some point in the past). When creating their values, the user agent ought to
249   do so by selecting the challenge with what it considers to be the most
250   secure auth-scheme that it understands, obtaining credentials from the user
251   as appropriate.
252</t>
253<figure><artwork type="abnf2616"><iref item="credentials" primary="true"/><iref primary="true" item="Grammar" subitem="credentials"/>
254  <x:ref>credentials</x:ref> = <x:ref>auth-scheme</x:ref> [ 1*<x:ref>SP</x:ref> ( <x:ref>token68</x:ref> / #<x:ref>auth-param</x:ref> ) ]
255</artwork></figure>
256<t>
257   Upon a request for a protected resource that omits credentials, contains
258   invalid credentials (e.g., a bad password) or partial credentials (e.g.,
259   when the authentication scheme requires more than one round trip), an origin
260   server &SHOULD; return a <x:ref>401 (Unauthorized)</x:ref> response. Such
261   responses &MUST; include a <x:ref>WWW-Authenticate</x:ref> header field
262   containing at least one (possibly new) challenge applicable to the
263   requested resource.
264</t>
265<t>
266   Likewise, upon a request that requires authentication by proxies that omit
267   credentials or contain invalid or partial credentials, a proxy &SHOULD;
268   return a <x:ref>407 (Proxy Authentication Required)</x:ref> response. Such responses
269   &MUST; include a <x:ref>Proxy-Authenticate</x:ref> header field containing a (possibly
270   new) challenge applicable to the proxy.
271</t>
272<t>
273   A server receiving credentials that are valid, but not adequate to gain
274   access, ought to respond with the <x:ref>403 (Forbidden)</x:ref> status code (&status.403;).
275</t>
276<t>
277   The HTTP protocol does not restrict applications to this simple
278   challenge-response mechanism for access authentication. Additional
279   mechanisms &MAY; be used, such as encryption at the transport level or
280   via message encapsulation, and with additional header fields
281   specifying authentication information. However, such additional
282   mechanisms are not defined by this specification.
283</t>
284<t>
285   Proxies &MUST; forward the <x:ref>WWW-Authenticate</x:ref> and
286   <x:ref>Authorization</x:ref> header fields unmodified and follow the rules
287   found in <xref target="header.authorization"/>.
288</t>
289</section>
290
291<section title="Protection Space (Realm)" anchor="protection.space">
292  <iref item="Protection Space"/>
293  <iref item="Realm"/>
294  <iref item="Canonical Root URI"/>
295<t>
296   The authentication parameter realm is reserved for use by authentication
297   schemes that wish to indicate the scope of protection.
298</t>
299<t>
300   A <x:dfn>protection space</x:dfn> is defined by the canonical root URI (the
301   scheme and authority components of the effective request URI; see
302   <xref target="Part1" x:fmt="of" x:rel="#effective.request.uri"/>) of the
303   server being accessed, in combination with the realm value if present.
304   These realms allow the protected resources on a server to be
305   partitioned into a set of protection spaces, each with its own
306   authentication scheme and/or authorization database. The realm value
307   is a string, generally assigned by the origin server, which can have
308   additional semantics specific to the authentication scheme. Note that
309   there can be multiple challenges with the same auth-scheme but
310   different realms.
311</t>
312<t>
313   The protection space determines the domain over which credentials can
314   be automatically applied. If a prior request has been authorized, the
315   same credentials &MAY; be reused for all other requests within that
316   protection space for a period of time determined by the
317   authentication scheme, parameters, and/or user preference. Unless
318   otherwise defined by the authentication scheme, a single protection
319   space cannot extend outside the scope of its server.
320</t>
321<t>
322   For historical reasons, senders &MUST; only use the quoted-string syntax.
323   Recipients might have to support both token and quoted-string syntax for
324   maximum interoperability with existing clients that have been accepting both
325   notations for a long time.
326</t>
327</section>
328
329<section title="Authentication Scheme Registry" anchor="authentication.scheme.registry">
330<t>
331  The HTTP Authentication Scheme Registry defines the name space for the
332  authentication schemes in challenges and credentials.
333</t>
334<t>
335  Registrations &MUST; include the following fields:
336  <list style="symbols">
337    <t>Authentication Scheme Name</t>
338    <t>Pointer to specification text</t>
339    <t>Notes (optional)</t>
340  </list>
341</t>
342<t>
343  Values to be added to this name space require IETF Review
344  (see <xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
345</t>
346<t>
347  The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-authschemes"/>.
348</t>
349
350<section title="Considerations for New Authentication Schemes" anchor="considerations.for.new.authentication.schemes">
351<t>
352  There are certain aspects of the HTTP Authentication Framework that put
353  constraints on how new authentication schemes can work:
354</t>
355<t>
356  <list style="symbols">
357    <x:lt>
358    <t>
359      HTTP authentication is presumed to be stateless: all of the information
360      necessary to authenticate a request &MUST; be provided in the request,
361      rather than be dependent on the server remembering prior requests.
362      Authentication based on, or bound to, the underlying connection is
363      outside the scope of this specification and inherently flawed unless
364      steps are taken to ensure that the connection cannot be used by any
365      party other than the authenticated user
366      (see &msg-orient-and-buffering;).
367    </t>
368    </x:lt>
369    <x:lt>
370    <t>
371      The authentication parameter "realm" is reserved for defining Protection
372      Spaces as defined in <xref target="protection.space"/>. New schemes
373      &MUST-NOT; use it in a way incompatible with that definition.
374    </t>
375    </x:lt>
376    <x:lt>
377    <t>
378      The "token68" notation was introduced for compatibility with existing
379      authentication schemes and can only be used once per challenge/credentials.
380      New schemes thus ought to use the "auth-param" syntax instead, because
381      otherwise future extensions will be impossible.
382    </t>
383    </x:lt>
384    <x:lt>
385    <t>
386      The parsing of challenges and credentials is defined by this specification,
387      and cannot be modified by new authentication schemes. When the auth-param
388      syntax is used, all parameters ought to support both token and
389      quoted-string syntax, and syntactical constraints ought to be defined on
390      the field value after parsing (i.e., quoted-string processing). This is
391      necessary so that recipients can use a generic parser that applies to
392      all authentication schemes.
393    </t>
394    <t>
395      &Note; The fact that the value syntax for the "realm" parameter
396      is restricted to quoted-string was a bad design choice not to be repeated
397      for new parameters.
398    </t>
399    </x:lt>
400    <x:lt>
401    <t>
402      Definitions of new schemes ought to define the treatment of unknown
403      extension parameters. In general, a "must-ignore" rule is preferable
404      over "must-understand", because otherwise it will be hard to introduce
405      new parameters in the presence of legacy recipients. Furthermore,
406      it's good to describe the policy for defining new parameters (such
407      as "update the specification", or "use this registry").
408    </t>
409    </x:lt>
410    <x:lt>
411    <t>
412      Authentication schemes need to document whether they are usable in
413      origin-server authentication (i.e., using <x:ref>WWW-Authenticate</x:ref>),
414      and/or proxy authentication (i.e., using <x:ref>Proxy-Authenticate</x:ref>).
415    </t>
416    </x:lt>
417    <x:lt>
418    <t>
419      The credentials carried in an <x:ref>Authorization</x:ref> header field are specific to
420      the User Agent, and therefore have the same effect on HTTP caches as the
421      "private" Cache-Control response directive, within the scope of the
422      request they appear in.
423    </t>
424    <t>
425      Therefore, new authentication schemes which choose not to carry
426      credentials in the <x:ref>Authorization</x:ref> header field (e.g., using a newly defined
427      header field) will need to explicitly disallow caching, by mandating the use of
428      either Cache-Control request directives (e.g., "no-store") or response
429      directives (e.g., "private").
430    </t>
431    </x:lt>
432  </list>
433</t>
434</section>
435
436</section>
437
438</section>
439
440<section title="Status Code Definitions" anchor="status.code.definitions">
441<section title="401 Unauthorized" anchor="status.401">
442  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
443  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
444  <x:anchor-alias value="401 (Unauthorized)"/>
445<t>
446   The request requires user authentication. The response &MUST; include a
447   <x:ref>WWW-Authenticate</x:ref> header field (<xref target="header.www-authenticate"/>)
448   containing a challenge applicable to the target resource. The client &MAY;
449   repeat the request with a suitable <x:ref>Authorization</x:ref> header field
450   (<xref target="header.authorization"/>). If the request already included
451   Authorization credentials, then the 401 response indicates that authorization
452   has been refused for those credentials. If the 401 response contains the
453   same challenge as the prior response, and the user agent has already attempted
454   authentication at least once, then the user &SHOULD; be presented the
455   representation that was given in the response, since that representation might
456   include relevant diagnostic information.
457</t>
458</section>
459<section title="407 Proxy Authentication Required" anchor="status.407">
460  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
461  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
462  <x:anchor-alias value="407 (Proxy Authentication Required)"/>
463<t>
464   This code is similar to <x:ref>401 (Unauthorized)</x:ref>, but indicates that the
465   client ought to first authenticate itself with the proxy. The proxy &MUST;
466   return a <x:ref>Proxy-Authenticate</x:ref> header field (<xref target="header.proxy-authenticate"/>) containing a
467   challenge applicable to the proxy for the target resource. The
468   client &MAY; repeat the request with a suitable <x:ref>Proxy-Authorization</x:ref>
469   header field (<xref target="header.proxy-authorization"/>).
470</t>
471</section>
472</section>
473
474<section title="Header Field Definitions" anchor="header.field.definitions">
475<t>
476   This section defines the syntax and semantics of HTTP/1.1 header fields
477   related to authentication.
478</t>
479
480<section title="Authorization" anchor="header.authorization">
481  <iref primary="true" item="Authorization header field" x:for-anchor=""/>
482  <x:anchor-alias value="Authorization"/>
483<t>
484   The "Authorization" header field allows a user agent to authenticate
485   itself with a server &mdash; usually, but not necessarily, after receiving a <x:ref>401
486   (Unauthorized)</x:ref> response. Its value consists of credentials containing
487   information of the user agent for the realm of the resource being
488   requested.
489</t>
490<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
491  <x:ref>Authorization</x:ref> = <x:ref>credentials</x:ref>
492</artwork></figure>
493<t>
494   If a request is
495   authenticated and a realm specified, the same credentials &SHOULD;
496   be valid for all other requests within this realm (assuming that
497   the authentication scheme itself does not require otherwise, such
498   as credentials that vary according to a challenge value or using
499   synchronized clocks).
500</t>
501<t>
502      When a shared cache (see &shared-and-non-shared-caches;) receives a request
503      containing an Authorization field, it &MUST-NOT; return the
504      corresponding response as a reply to any other request, unless one
505      of the following specific exceptions holds:
506</t>
507<t>
508  <list style="numbers">
509      <t>If the response includes the "s-maxage" cache-control
510         directive, the cache &MAY; use that response in replying to a
511         subsequent request. But (if the specified maximum age has
512         passed) a proxy cache &MUST; first revalidate it with the origin
513         server, using the header fields from the new request to allow
514         the origin server to authenticate the new request. (This is the
515         defined behavior for s-maxage.) If the response includes "s-maxage=0",
516         the proxy &MUST; always revalidate it before re-using
517         it.</t>
518
519      <t>If the response includes the "must-revalidate" cache-control
520         directive, the cache &MAY; use that response in replying to a
521         subsequent request. But if the response is stale, all caches
522         &MUST; first revalidate it with the origin server, using the
523         header fields from the new request to allow the origin server
524         to authenticate the new request.</t>
525
526      <t>If the response includes the "public" cache-control directive,
527         it &MAY; be returned in reply to any subsequent request.</t>
528  </list>
529</t>
530</section>
531
532<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
533  <iref primary="true" item="Proxy-Authenticate header field" x:for-anchor=""/>
534  <x:anchor-alias value="Proxy-Authenticate"/>
535<t>
536   The "Proxy-Authenticate" header field consists of at least one
537   challenge that indicates the authentication scheme(s) and parameters
538   applicable to the proxy for this effective request URI (&effective-request-uri;).
539   It &MUST; be included as part of a <x:ref>407 (Proxy Authentication Required)</x:ref> response.
540</t>
541<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
542  <x:ref>Proxy-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
543</artwork></figure>
544<t>
545   Unlike <x:ref>WWW-Authenticate</x:ref>, the Proxy-Authenticate header field
546   applies only to the current connection, and intermediaries &SHOULD-NOT;
547   forward it to downstream clients. However, an intermediate proxy might need
548   to obtain its own credentials by requesting them from the downstream client,
549   which in some circumstances will appear as if the proxy is forwarding the
550   Proxy-Authenticate header field.
551</t>
552<t>
553   Note that the parsing considerations for <x:ref>WWW-Authenticate</x:ref>
554   apply to this header field as well; see <xref target="header.www-authenticate"/>
555   for details.
556</t>
557</section>
558
559<section title="Proxy-Authorization" anchor="header.proxy-authorization">
560  <iref primary="true" item="Proxy-Authorization header field" x:for-anchor=""/>
561  <x:anchor-alias value="Proxy-Authorization"/>
562<t>
563   The "Proxy-Authorization" header field allows the client to
564   identify itself (or its user) to a proxy which requires
565   authentication. Its value consists of
566   credentials containing the authentication information of the user
567   agent for the proxy and/or realm of the resource being requested.
568</t>
569<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
570  <x:ref>Proxy-Authorization</x:ref> = <x:ref>credentials</x:ref>
571</artwork></figure>
572<t>
573   Unlike <x:ref>Authorization</x:ref>, the Proxy-Authorization header field applies only to
574   the next outbound proxy that demanded authentication using the <x:ref>Proxy-Authenticate</x:ref>
575   field. When multiple proxies are used in a chain, the
576   Proxy-Authorization header field is consumed by the first outbound
577   proxy that was expecting to receive credentials. A proxy &MAY; relay
578   the credentials from the client request to the next proxy if that is
579   the mechanism by which the proxies cooperatively authenticate a given
580   request.
581</t>
582</section>
583
584<section title="WWW-Authenticate" anchor="header.www-authenticate">
585  <iref primary="true" item="WWW-Authenticate header field" x:for-anchor=""/>
586  <x:anchor-alias value="WWW-Authenticate"/>
587<t>
588   The "WWW-Authenticate" header field consists of at least one
589   challenge that indicates the authentication scheme(s) and parameters
590   applicable to the effective request URI (&effective-request-uri;).
591</t>
592<t>  
593   It &MUST; be included in <x:ref>401 (Unauthorized)</x:ref> response messages and &MAY; be
594   included in other response messages to indicate that supplying credentials
595   (or different credentials) might affect the response.
596</t>
597<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
598  <x:ref>WWW-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
599</artwork></figure>
600<t>
601   User agents are advised to take special care in parsing the WWW-Authenticate
602   field value as it might contain more than one challenge,
603   or if more than one WWW-Authenticate header field is provided, the
604   contents of a challenge itself can contain a comma-separated list of
605   authentication parameters.
606</t>
607<figure>
608  <preamble>For instance:</preamble>
609  <artwork type="example">
610  WWW-Authenticate: Newauth realm="apps", type=1,
611                    title="Login to \"apps\"", Basic realm="simple"
612</artwork>
613  <postamble>
614  This header field contains two challenges; one for the "Newauth" scheme
615  with a realm value of "apps", and two additional parameters "type" and
616  "title", and another one for the "Basic" scheme with a realm value of
617  "simple".
618</postamble></figure>
619<x:note>
620  <t>
621    &Note; The challenge grammar production uses the list syntax as
622    well. Therefore, a sequence of comma, whitespace, and comma can be
623    considered both as applying to the preceding challenge, or to be an
624    empty entry in the list of challenges. In practice, this ambiguity
625    does not affect the semantics of the header field value and thus is
626    harmless.
627  </t>
628</x:note>
629</section>
630
631</section>
632
633<section title="IANA Considerations" anchor="IANA.considerations">
634
635<section title="Authentication Scheme Registry" anchor="authentication.scheme.registration">
636<t>
637  The registration procedure for HTTP Authentication Schemes is defined by
638  <xref target="authentication.scheme.registry"/> of this document.
639</t>
640<t>
641   The HTTP Method Authentication Scheme shall be created at <eref target="http://www.iana.org/assignments/http-authschemes"/>.
642</t>
643</section>
644
645<section title="Status Code Registration" anchor="status.code.registration">
646<t>
647   The HTTP Status Code Registry located at <eref target="http://www.iana.org/assignments/http-status-codes"/>
648   shall be updated with the registrations below:
649</t>
650<?BEGININC p7-auth.iana-status-codes ?>
651<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
652<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
653   <ttcol>Value</ttcol>
654   <ttcol>Description</ttcol>
655   <ttcol>Reference</ttcol>
656   <c>401</c>
657   <c>Unauthorized</c>
658   <c>
659      <xref target="status.401"/>
660   </c>
661   <c>407</c>
662   <c>Proxy Authentication Required</c>
663   <c>
664      <xref target="status.407"/>
665   </c>
666</texttable>
667<!--(END)-->
668<?ENDINC p7-auth.iana-status-codes ?>
669</section>
670
671<section title="Header Field Registration" anchor="header.field.registration">
672<t>
673   The Message Header Field Registry located at <eref target="http://www.iana.org/assignments/message-headers/message-header-index.html"/> shall be updated
674   with the permanent registrations below (see <xref target="RFC3864"/>):
675</t>
676<?BEGININC p7-auth.iana-headers ?>
677<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
678<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
679   <ttcol>Header Field Name</ttcol>
680   <ttcol>Protocol</ttcol>
681   <ttcol>Status</ttcol>
682   <ttcol>Reference</ttcol>
683
684   <c>Authorization</c>
685   <c>http</c>
686   <c>standard</c>
687   <c>
688      <xref target="header.authorization"/>
689   </c>
690   <c>Proxy-Authenticate</c>
691   <c>http</c>
692   <c>standard</c>
693   <c>
694      <xref target="header.proxy-authenticate"/>
695   </c>
696   <c>Proxy-Authorization</c>
697   <c>http</c>
698   <c>standard</c>
699   <c>
700      <xref target="header.proxy-authorization"/>
701   </c>
702   <c>WWW-Authenticate</c>
703   <c>http</c>
704   <c>standard</c>
705   <c>
706      <xref target="header.www-authenticate"/>
707   </c>
708</texttable>
709<!--(END)-->
710<?ENDINC p7-auth.iana-headers ?>
711<t>
712   The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".
713</t>
714</section>
715</section>
716
717<section title="Security Considerations" anchor="security.considerations">
718<t>
719   This section is meant to inform application developers, information
720   providers, and users of the security limitations in HTTP/1.1 as
721   described by this document. The discussion does not include
722   definitive solutions to the problems revealed, though it does make
723   some suggestions for reducing security risks.
724</t>
725
726<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
727<t>
728   Existing HTTP clients and user agents typically retain authentication
729   information indefinitely. HTTP/1.1 does not provide a method for a
730   server to direct clients to discard these cached credentials. This is
731   a significant defect that requires further extensions to HTTP.
732   Circumstances under which credential caching can interfere with the
733   application's security model include but are not limited to:
734  <list style="symbols">
735     <t>Clients which have been idle for an extended period following
736        which the server might wish to cause the client to reprompt the
737        user for credentials.</t>
738
739     <t>Applications which include a session termination indication
740        (such as a "logout" or "commit" button on a page) after which
741        the server side of the application "knows" that there is no
742        further reason for the client to retain the credentials.</t>
743  </list>
744</t>
745<t>
746   This is currently under separate study. There are a number of work-arounds
747   to parts of this problem, and we encourage the use of
748   password protection in screen savers, idle time-outs, and other
749   methods which mitigate the security problems inherent in this
750   problem. In particular, user agents which cache credentials are
751   encouraged to provide a readily accessible mechanism for discarding
752   cached credentials under user control.
753</t>
754</section>
755
756<section title="Protection Spaces" anchor="protection.spaces">
757<t>
758  Authentication schemes that solely rely on the "realm" mechanism for
759  establishing a protection space will expose credentials to all resources on a
760  server. Clients that have successfully made authenticated requests with a
761  resource can use the same authentication credentials for other resources on
762  the same server. This makes it possible for a different resource to harvest
763  authentication credentials for other resources.
764</t>
765<t>
766  This is of particular concern when a server hosts resources for multiple
767  parties under the same canonical root URI (<xref target="protection.space"/>).
768  Possible mitigation strategies include restricting direct access to
769  authentication credentials (i.e., not making the content of the
770  <x:ref>Authorization</x:ref> request header field available), and separating protection
771  spaces by using a different host name for each party.
772</t>
773</section>
774</section>
775
776<section title="Acknowledgments" anchor="acks">
777<t>
778  This specification takes over the definition of the HTTP Authentication
779  Framework, previously defined in <xref target="RFC2617" x:fmt="none">RFC 2617</xref>.
780  We thank John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D. Lawrence,
781  Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for their work
782  on that specification. See <xref target="RFC2617" x:fmt="of" x:sec="6"/>
783  for further acknowledgements. 
784</t>
785<t>
786  See &acks; for the Acknowledgments related to this document revision.
787</t>
788</section>
789</middle>
790
791<back>
792
793<references title="Normative References">
794
795<reference anchor="Part1">
796  <front>
797    <title>Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing</title>
798    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
799      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
800      <address><email>fielding@gbiv.com</email></address>
801    </author>
802    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
803      <organization abbrev="W3C">World Wide Web Consortium</organization>
804      <address><email>ylafon@w3.org</email></address>
805    </author>
806    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
807      <organization abbrev="greenbytes">greenbytes GmbH</organization>
808      <address><email>julian.reschke@greenbytes.de</email></address>
809    </author>
810    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
811  </front>
812  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
813  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
814</reference>
815
816<reference anchor="Part2">
817  <front>
818    <title>Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content</title>
819    <author fullname="Roy T. Fielding" initials="R." role="editor" surname="Fielding">
820      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
821      <address><email>fielding@gbiv.com</email></address>
822    </author>
823    <author fullname="Yves Lafon" initials="Y." role="editor" surname="Lafon">
824      <organization abbrev="W3C">World Wide Web Consortium</organization>
825      <address><email>ylafon@w3.org</email></address>
826    </author>
827    <author fullname="Julian F. Reschke" initials="J. F." role="editor" surname="Reschke">
828      <organization abbrev="greenbytes">greenbytes GmbH</organization>
829      <address><email>julian.reschke@greenbytes.de</email></address>
830    </author>
831    <date month="&ID-MONTH;" year="&ID-YEAR;" />
832  </front>
833  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p2-semantics-&ID-VERSION;" />
834  <x:source basename="p2-semantics" href="p2-semantics.xml">
835    <x:defines>403 (Forbidden)</x:defines>
836    <x:defines>Location</x:defines>
837  </x:source>
838</reference>
839
840<reference anchor="Part6">
841  <front>
842    <title>Hypertext Transfer Protocol (HTTP/1.1): Caching</title>
843    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
844      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
845      <address><email>fielding@gbiv.com</email></address>
846    </author>
847    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
848      <organization abbrev="W3C">World Wide Web Consortium</organization>
849      <address><email>ylafon@w3.org</email></address>
850    </author>
851    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
852      <address><email>mnot@mnot.net</email></address>
853    </author>
854    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
855      <organization abbrev="greenbytes">greenbytes GmbH</organization>
856      <address><email>julian.reschke@greenbytes.de</email></address>
857    </author>
858    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
859  </front>
860  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
861  <x:source href="p6-cache.xml" basename="p6-cache"/>
862</reference>
863
864<reference anchor="RFC2119">
865  <front>
866    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
867    <author initials="S." surname="Bradner" fullname="Scott Bradner">
868      <organization>Harvard University</organization>
869      <address><email>sob@harvard.edu</email></address>
870    </author>
871    <date month="March" year="1997"/>
872  </front>
873  <seriesInfo name="BCP" value="14"/>
874  <seriesInfo name="RFC" value="2119"/>
875</reference>
876
877<reference anchor="RFC5234">
878  <front>
879    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
880    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
881      <organization>Brandenburg InternetWorking</organization>
882      <address>
883        <email>dcrocker@bbiw.net</email>
884      </address> 
885    </author>
886    <author initials="P." surname="Overell" fullname="Paul Overell">
887      <organization>THUS plc.</organization>
888      <address>
889        <email>paul.overell@thus.net</email>
890      </address>
891    </author>
892    <date month="January" year="2008"/>
893  </front>
894  <seriesInfo name="STD" value="68"/>
895  <seriesInfo name="RFC" value="5234"/>
896</reference>
897
898</references>
899
900<references title="Informative References">
901
902<reference anchor="RFC2616">
903  <front>
904    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
905    <author initials="R." surname="Fielding" fullname="R. Fielding">
906      <organization>University of California, Irvine</organization>
907      <address><email>fielding@ics.uci.edu</email></address>
908    </author>
909    <author initials="J." surname="Gettys" fullname="J. Gettys">
910      <organization>W3C</organization>
911      <address><email>jg@w3.org</email></address>
912    </author>
913    <author initials="J." surname="Mogul" fullname="J. Mogul">
914      <organization>Compaq Computer Corporation</organization>
915      <address><email>mogul@wrl.dec.com</email></address>
916    </author>
917    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
918      <organization>MIT Laboratory for Computer Science</organization>
919      <address><email>frystyk@w3.org</email></address>
920    </author>
921    <author initials="L." surname="Masinter" fullname="L. Masinter">
922      <organization>Xerox Corporation</organization>
923      <address><email>masinter@parc.xerox.com</email></address>
924    </author>
925    <author initials="P." surname="Leach" fullname="P. Leach">
926      <organization>Microsoft Corporation</organization>
927      <address><email>paulle@microsoft.com</email></address>
928    </author>
929    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
930      <organization>W3C</organization>
931      <address><email>timbl@w3.org</email></address>
932    </author>
933    <date month="June" year="1999"/>
934  </front>
935  <seriesInfo name="RFC" value="2616"/>
936</reference>
937
938<reference anchor="RFC2617">
939  <front>
940    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
941    <author initials="J." surname="Franks" fullname="John Franks">
942      <organization>Northwestern University, Department of Mathematics</organization>
943      <address><email>john@math.nwu.edu</email></address>
944    </author>
945    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
946      <organization>Verisign Inc.</organization>
947      <address><email>pbaker@verisign.com</email></address>
948    </author>
949    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
950      <organization>AbiSource, Inc.</organization>
951      <address><email>jeff@AbiSource.com</email></address>
952    </author>
953    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
954      <organization>Agranat Systems, Inc.</organization>
955      <address><email>lawrence@agranat.com</email></address>
956    </author>
957    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
958      <organization>Microsoft Corporation</organization>
959      <address><email>paulle@microsoft.com</email></address>
960    </author>
961    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
962      <organization>Netscape Communications Corporation</organization>
963    </author>
964    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
965      <organization>Open Market, Inc.</organization>
966      <address><email>stewart@OpenMarket.com</email></address>
967    </author>
968    <date month="June" year="1999"/>
969  </front>
970  <seriesInfo name="RFC" value="2617"/>
971</reference>
972
973<reference anchor='RFC3864'>
974  <front>
975    <title>Registration Procedures for Message Header Fields</title>
976    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
977      <organization>Nine by Nine</organization>
978      <address><email>GK-IETF@ninebynine.org</email></address>
979    </author>
980    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
981      <organization>BEA Systems</organization>
982      <address><email>mnot@pobox.com</email></address>
983    </author>
984    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
985      <organization>HP Labs</organization>
986      <address><email>JeffMogul@acm.org</email></address>
987    </author>
988    <date year='2004' month='September' />
989  </front>
990  <seriesInfo name='BCP' value='90' />
991  <seriesInfo name='RFC' value='3864' />
992</reference>
993
994<reference anchor="RFC3986">
995 <front>
996  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
997  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
998    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
999    <address>
1000       <email>timbl@w3.org</email>
1001       <uri>http://www.w3.org/People/Berners-Lee/</uri>
1002    </address>
1003  </author>
1004  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
1005    <organization abbrev="Day Software">Day Software</organization>
1006    <address>
1007      <email>fielding@gbiv.com</email>
1008      <uri>http://roy.gbiv.com/</uri>
1009    </address>
1010  </author>
1011  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
1012    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
1013    <address>
1014      <email>LMM@acm.org</email>
1015      <uri>http://larry.masinter.net/</uri>
1016    </address>
1017  </author>
1018  <date month='January' year='2005'></date>
1019 </front>
1020 <seriesInfo name="STD" value="66"/>
1021 <seriesInfo name="RFC" value="3986"/>
1022</reference>
1023
1024<reference anchor="RFC4648">
1025  <front>
1026    <title>The Base16, Base32, and Base64 Data Encodings</title>
1027    <author fullname="S. Josefsson" initials="S." surname="Josefsson"/>
1028    <date year="2006" month="October"/>
1029  </front>
1030  <seriesInfo value="4648" name="RFC"/>
1031</reference>
1032
1033<reference anchor='RFC5226'>
1034  <front>
1035    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
1036    <author initials='T.' surname='Narten' fullname='T. Narten'>
1037      <organization>IBM</organization>
1038      <address><email>narten@us.ibm.com</email></address>
1039    </author>
1040    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
1041      <organization>Google</organization>
1042      <address><email>Harald@Alvestrand.no</email></address>
1043    </author>
1044    <date year='2008' month='May' />
1045  </front>
1046  <seriesInfo name='BCP' value='26' />
1047  <seriesInfo name='RFC' value='5226' />
1048</reference>
1049
1050</references>
1051
1052<section title="Changes from RFCs 2616 and 2617" anchor="changes.from.rfc.2616">
1053<t>
1054  The "realm" parameter isn't required anymore in general; consequently, the
1055  ABNF allows challenges without any auth parameters.
1056  (<xref target="access.authentication.framework"/>)
1057</t>
1058<t>
1059  The "token68" alternative to auth-param lists has been added for consistency
1060  with legacy authentication schemes such as "Basic".
1061  (<xref target="access.authentication.framework"/>)
1062</t>
1063<t>
1064  Introduce Authentication Scheme Registry.
1065  (<xref target="authentication.scheme.registry"/>)
1066</t>
1067</section>
1068 
1069<section title="Imported ABNF" anchor="imported.abnf">
1070  <x:anchor-alias value="ALPHA"/>
1071  <x:anchor-alias value="CR"/>
1072  <x:anchor-alias value="DIGIT"/>
1073  <x:anchor-alias value="LF"/>
1074  <x:anchor-alias value="OCTET"/>
1075  <x:anchor-alias value="VCHAR"/>
1076  <x:anchor-alias value="SP"/>
1077  <x:anchor-alias value="quoted-string"/>
1078  <x:anchor-alias value="token"/>
1079  <x:anchor-alias value="BWS"/>
1080  <x:anchor-alias value="OWS"/>
1081<t>
1082  The following core rules are included by
1083  reference, as defined in <xref target="RFC5234" x:fmt="of" x:sec="B.1"/>:
1084  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
1085  DIGIT (decimal 0-9), DQUOTE (double quote),
1086  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
1087  OCTET (any 8-bit sequence of data), SP (space), and
1088  VCHAR (any visible US-ASCII character).
1089</t>
1090<t>
1091   The rules below are defined in <xref target="Part1"/>:
1092</t>
1093<figure><artwork type="abnf2616">
1094  <x:ref>BWS</x:ref>           = &lt;BWS, defined in &whitespace;&gt;
1095  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &whitespace;&gt;
1096  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-components;&gt;
1097  <x:ref>token</x:ref>         = &lt;token, defined in &field-components;&gt;
1098</artwork></figure>
1099</section>
1100
1101<?BEGININC p7-auth.abnf-appendix ?>
1102<section xmlns:x="http://purl.org/net/xml2rfc/ext" title="Collected ABNF" anchor="collected.abnf">
1103<figure>
1104<artwork type="abnf" name="p7-auth.parsed-abnf">
1105<x:ref>Authorization</x:ref> = credentials
1106
1107<x:ref>BWS</x:ref> = &lt;BWS, defined in [Part1], Section 3.2.1&gt;
1108
1109<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 3.2.1&gt;
1110
1111<x:ref>Proxy-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS
1112 challenge ] )
1113<x:ref>Proxy-Authorization</x:ref> = credentials
1114
1115<x:ref>WWW-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS challenge
1116 ] )
1117
1118<x:ref>auth-param</x:ref> = token BWS "=" BWS ( token / quoted-string )
1119<x:ref>auth-scheme</x:ref> = token
1120
1121<x:ref>challenge</x:ref> = auth-scheme [ 1*SP ( token68 / [ ( "," / auth-param ) *(
1122 OWS "," [ OWS auth-param ] ) ] ) ]
1123<x:ref>credentials</x:ref> = auth-scheme [ 1*SP ( token68 / [ ( "," / auth-param )
1124 *( OWS "," [ OWS auth-param ] ) ] ) ]
1125
1126<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 3.2.4&gt;
1127
1128<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 3.2.4&gt;
1129<x:ref>token68</x:ref> = 1*( ALPHA / DIGIT / "-" / "." / "_" / "~" / "+" / "/" )
1130 *"="
1131</artwork>
1132</figure>
1133</section>
1134<?ENDINC p7-auth.abnf-appendix ?>
1135
1136<section title="Change Log (to be removed by RFC Editor before publication)"  anchor="change.log">
1137<t>
1138  Changes up to the first Working Group Last Call draft are summarized
1139  in <eref target="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p7-auth-19#appendix-C"/>.
1140</t>
1141
1142<section title="Since draft-ietf-httpbis-p7-auth-19" anchor="changes.since.19">
1143<t>
1144  Closed issues:
1145  <list style="symbols">
1146    <t>
1147      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/348"/>:
1148      "Realms and scope"
1149    </t>
1150    <t>
1151      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/349"/>:
1152      "Strength"
1153    </t>
1154    <t>
1155      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/357"/>:
1156      "Authentication exchanges"
1157    </t>
1158    <t>
1159      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/361"/>:
1160      "ABNF requirements for recipients"
1161    </t>
1162    <t>
1163      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/368"/>:
1164      "note introduction of new IANA registries as normative changes"
1165    </t>
1166  </list>
1167</t>
1168</section>
1169
1170<section title="Since draft-ietf-httpbis-p7-auth-20" anchor="changes.since.20">
1171<t>
1172  Closed issues:
1173  <list style="symbols">
1174    <t>
1175      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/376"/>:
1176      "rename b64token for clarity"
1177    </t>
1178  </list>
1179</t>
1180<t>
1181  Other changes:
1182  <list style="symbols">
1183    <t>
1184      Conformance criteria and considerations regarding error handling are
1185      now defined in Part 1.
1186    </t>
1187  </list>
1188</t>
1189</section>
1190</section>
1191
1192</back>
1193</rfc>
Note: See TracBrowser for help on using the repository browser.