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

Last change on this file since 2521 was 2519, checked in by fielding@…, 7 years ago

(editorial) Remove unnecessary or duplicate ABNF that can be replaced with core rules: word, specials, attribute, value, and quoted-cpair; addresses #541

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