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

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

Prepare publication of -17.

  • Property svn:eol-style set to native
File size: 57.1 KB
[29]1<?xml version="1.0" encoding="utf-8"?>
[101]2<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
[8]3<!DOCTYPE rfc [
4  <!ENTITY MAY "<bcp14 xmlns=''>MAY</bcp14>">
5  <!ENTITY MUST "<bcp14 xmlns=''>MUST</bcp14>">
6  <!ENTITY MUST-NOT "<bcp14 xmlns=''>MUST NOT</bcp14>">
7  <!ENTITY OPTIONAL "<bcp14 xmlns=''>OPTIONAL</bcp14>">
8  <!ENTITY RECOMMENDED "<bcp14 xmlns=''>RECOMMENDED</bcp14>">
9  <!ENTITY REQUIRED "<bcp14 xmlns=''>REQUIRED</bcp14>">
10  <!ENTITY SHALL "<bcp14 xmlns=''>SHALL</bcp14>">
11  <!ENTITY SHALL-NOT "<bcp14 xmlns=''>SHALL NOT</bcp14>">
12  <!ENTITY SHOULD "<bcp14 xmlns=''>SHOULD</bcp14>">
13  <!ENTITY SHOULD-NOT "<bcp14 xmlns=''>SHOULD NOT</bcp14>">
[29]14  <!ENTITY ID-VERSION "latest">
[1443]15  <!ENTITY ID-MONTH "October">
[1099]16  <!ENTITY ID-YEAR "2011">
[1101]17  <!ENTITY mdash "&#8212;">
[1452]18  <!ENTITY architecture                 "<xref target='Part1' x:rel='#architecture' xmlns:x=''/>">
[424]19  <!ENTITY notation                     "<xref target='Part1' x:rel='#notation' xmlns:x=''/>">
[205]20  <!ENTITY notation-abnf                "<xref target='Part1' x:rel='#notation.abnf' xmlns:x=''/>">
[1399]21  <!ENTITY acks                         "<xref target='Part1' x:rel='#acks' xmlns:x=''/>">
[205]22  <!ENTITY basic-rules                  "<xref target='Part1' x:rel='#basic.rules' xmlns:x=''/>">
[1396]23  <!ENTITY field-rules                  "<xref target='Part1' x:rel='#field.rules' xmlns:x=''/>">
[961]24  <!ENTITY effective-request-uri        "<xref target='Part1' x:rel='#effective.request.uri' xmlns:x=''/>">
[1356]25  <!ENTITY msg-orient-and-buffering     "<xref target='Part1' x:rel='#message-orientation-and-buffering' xmlns:x=''/>">
[998]26  <!ENTITY end-to-end.and-hop-by-hop    "<xref target='Part1' x:rel='#end-to-end.and.hop-by-hop.header-fields' xmlns:x=''/>">
[31]27  <!ENTITY shared-and-non-shared-caches "<xref target='Part6' x:rel='#shared.and.non-shared.caches' xmlns:x=''/>">
29<?rfc toc="yes" ?>
[29]30<?rfc symrefs="yes" ?>
31<?rfc sortrefs="yes" ?>
[8]32<?rfc compact="yes"?>
33<?rfc subcompact="no" ?>
34<?rfc linkmailto="no" ?>
35<?rfc editing="no" ?>
[205]36<?rfc comments="yes"?>
37<?rfc inline="yes"?>
[799]38<?rfc rfcedstyle="yes"?>
[8]39<?rfc-ext allow-markup-in-artwork="yes" ?>
40<?rfc-ext include-references-in-index="yes" ?>
[308]41<rfc obsoletes="2616" updates="2617" category="std" x:maturity-level="draft"
[446]42     ipr="pre5378Trust200902" docName="draft-ietf-httpbis-p7-auth-&ID-VERSION;"
[153]43     xmlns:x=''>
[120]46  <title abbrev="HTTP/1.1, Part 7">HTTP/1.1, part 7: Authentication</title>
[29]48  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]49    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[8]50    <address>
51      <postal>
[1106]52        <street>345 Park Ave</street>
53        <city>San Jose</city>
[8]54        <region>CA</region>
[1106]55        <code>95110</code>
[29]56        <country>USA</country>
[8]57      </postal>
[29]58      <email></email>
59      <uri></uri>
[8]60    </address>
61  </author>
[29]63  <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]64    <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
[8]65    <address>
66      <postal>
[29]67        <street>21 Oak Knoll Road</street>
68        <city>Carlisle</city>
[8]69        <region>MA</region>
[29]70        <code>01741</code>
71        <country>USA</country>
[8]72      </postal>
[844]73      <email></email>
74      <uri></uri>
[8]75    </address>
76  </author>
78  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
[29]79    <organization abbrev="HP">Hewlett-Packard Company</organization>
[8]80    <address>
81      <postal>
[29]82        <street>HP Labs, Large Scale Systems Group</street>
83        <street>1501 Page Mill Road, MS 1177</street>
[8]84        <city>Palo Alto</city>
85        <region>CA</region>
[29]86        <code>94304</code>
87        <country>USA</country>
[8]88      </postal>
[29]89      <email></email>
[8]90    </address>
91  </author>
93  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
[29]94    <organization abbrev="Microsoft">Microsoft Corporation</organization>
[8]95    <address>
96      <postal>
[29]97        <street>1 Microsoft Way</street>
98        <city>Redmond</city>
99        <region>WA</region>
100        <code>98052</code>
101        <country>USA</country>
[8]102      </postal>
[29]103      <email></email>
[8]104    </address>
105  </author>
107  <author initials="L." surname="Masinter" fullname="Larry Masinter">
[1106]108    <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[8]109    <address>
110      <postal>
[29]111        <street>345 Park Ave</street>
112        <city>San Jose</city>
[8]113        <region>CA</region>
[29]114        <code>95110</code>
115        <country>USA</country>
[8]116      </postal>
[29]117      <email></email>
118      <uri></uri>
[8]119    </address>
120  </author>
122  <author initials="P." surname="Leach" fullname="Paul J. Leach">
123    <organization abbrev="Microsoft">Microsoft Corporation</organization>
124    <address>
125      <postal>
126        <street>1 Microsoft Way</street>
127        <city>Redmond</city>
128        <region>WA</region>
129        <code>98052</code>
130      </postal>
131      <email></email>
132    </address>
133  </author>
135  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
136    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
137    <address>
138      <postal>
[34]139        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
140        <street>The Stata Center, Building 32</street>
141        <street>32 Vassar Street</street>
[8]142        <city>Cambridge</city>
143        <region>MA</region>
144        <code>02139</code>
[29]145        <country>USA</country>
[8]146      </postal>
147      <email></email>
[34]148      <uri></uri>
[8]149    </address>
150  </author>
[95]152  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
153    <organization abbrev="W3C">World Wide Web Consortium</organization>
154    <address>
155      <postal>
156        <street>W3C / ERCIM</street>
157        <street>2004, rte des Lucioles</street>
158        <city>Sophia-Antipolis</city>
159        <region>AM</region>
160        <code>06902</code>
161        <country>France</country>
162      </postal>
163      <email></email>
164      <uri></uri>
165    </address>
166  </author>
168  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
169    <organization abbrev="greenbytes">greenbytes GmbH</organization>
170    <address>
171      <postal>
172        <street>Hafenweg 16</street>
173        <city>Muenster</city><region>NW</region><code>48155</code>
174        <country>Germany</country>
175      </postal>
[609]176      <phone>+49 251 2807760</phone>
177      <facsimile>+49 251 2807761</facsimile>
178      <email></email>
179      <uri></uri>
[95]180    </address>
181  </author>
[31]183  <date month="&ID-MONTH;" year="&ID-YEAR;"/>
[440]184  <workgroup>HTTPbis Working Group</workgroup>
[1373]188   The Hypertext Transfer Protocol (HTTP) is an application-level protocol for
189   distributed, collaborative, hypermedia information systems. HTTP has been in
190   use by the World Wide Web global information initiative since 1990. This
191   document is Part 7 of the seven-part specification that defines the protocol
192   referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616.
195   Part 7 defines the HTTP Authentication framework.
199<note title="Editorial Note (To be removed by RFC Editor)">
200  <t>
201    Discussion of this draft should take place on the HTTPBIS working group
[1268]202    mailing list (, which is archived at
203    <eref target=""/>.
204  </t>
205  <t>
206    The current issues list is at
207    <eref target=""/> and related
208    documents (including fancy diffs) can be found at
[324]209    <eref target=""/>.
[36]210  </t>
[153]211  <t>
[1401]212    The changes in this draft are summarized in <xref target="changes.since.16"/>.
[153]213  </t>
217<section title="Introduction" anchor="introduction">
[998]219   This document defines HTTP/1.1 access control and authentication. It
220   includes the relevant parts of <xref target="RFC2616" x:fmt="none">RFC 2616</xref>
221   with only minor changes, plus the general framework for HTTP authentication,
222   as previously defined in "HTTP Authentication: Basic and Digest Access
223   Authentication" (<xref target="RFC2617"/>).
226   HTTP provides several &OPTIONAL; challenge-response authentication
[998]227   mechanisms which can be used by a server to challenge a client request and
228   by a client to provide authentication information. The "basic" and "digest"
229   authentication schemes continue to be specified in
230   <xref target="RFC2617" x:fmt="none">RFC 2617</xref>.
[1452]233<section title="Conformance and Error Handling" anchor="intro.conformance.and.error.handling">
235   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
236   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
237   document are to be interpreted as described in <xref target="RFC2119"/>.
[1452]240   This document defines conformance criteria for several roles in HTTP
241   communication, including Senders, Recipients, Clients, Servers, User-Agents,
242   Origin Servers, Intermediaries, Proxies and Gateways. See &architecture;
243   for definitions of these terms.
246   An implementation is considered conformant if it complies with all of the
247   requirements associated with its role(s). Note that SHOULD-level requirements
248   are relevant here, unless one of the documented exceptions is applicable.
251   This document also uses ABNF to define valid protocol elements
252   (<xref target="notation"/>). In addition to the prose requirements placed
253   upon them, Senders &MUST-NOT; generate protocol elements that are invalid.
256   Unless noted otherwise, Recipients &MAY; take steps to recover a usable
257   protocol element from an invalid construct. However, HTTP does not define
258   specific error handling mechanisms, except in cases where it has direct
259   impact on security. This is because different uses of the protocol require
260   different error handling strategies; for example, a Web browser may wish to
261   transparently recover from a response where the Location header field
262   doesn't parse according to the ABNF, whereby in a systems control protocol
263   using HTTP, this type of error recovery could lead to dangerous consequences.
[424]267<section title="Syntax Notation" anchor="notation">
[425]268  <x:anchor-alias value="ALPHA"/>
269  <x:anchor-alias value="CR"/>
270  <x:anchor-alias value="DIGIT"/>
271  <x:anchor-alias value="LF"/>
272  <x:anchor-alias value="OCTET"/>
273  <x:anchor-alias value="VCHAR"/>
[998]274  <x:anchor-alias value="SP"/>
[543]276  This specification uses the ABNF syntax defined in &notation; (which
277  extends the syntax defined in <xref target="RFC5234"/> with a list rule).
278  <xref target="collected.abnf"/> shows the collected ABNF, with the list
279  rule expanded.
[425]282  The following core rules are included by
283  reference, as defined in <xref target="RFC5234" x:fmt="," x:sec="B.1"/>:
284  ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls),
285  DIGIT (decimal 0-9), DQUOTE (double quote),
286  HEXDIG (hexadecimal 0-9/A-F/a-f), LF (line feed),
[1425]287  OCTET (any 8-bit sequence of data), SP (space), and
288  VCHAR (any visible US-ASCII character).
291<section title="Core Rules" anchor="core.rules">
[998]292   <x:anchor-alias value="quoted-string"/>
293   <x:anchor-alias value="token"/>
[1386]294   <x:anchor-alias value="BWS"/>
[998]295   <x:anchor-alias value="OWS"/>
[1396]297   The core rules below are defined in <xref target="Part1"/>:
299<figure><artwork type="abnf2616">
[1386]300  <x:ref>BWS</x:ref>           = &lt;BWS, defined in &basic-rules;&gt;
[998]301  <x:ref>OWS</x:ref>           = &lt;OWS, defined in &basic-rules;&gt;
[1396]302  <x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in &field-rules;&gt;
303  <x:ref>token</x:ref>         = &lt;token, defined in &field-rules;&gt;
[998]309<section title="Access Authentication Framework" anchor="access.authentication.framework">
311<section title="Challenge and Response" anchor="challenge.and.response">
[998]312  <x:anchor-alias value="auth-scheme"/>
313  <x:anchor-alias value="auth-param"/>
[1394]314  <x:anchor-alias value="b64token"/>
[229]315  <x:anchor-alias value="challenge"/>
316  <x:anchor-alias value="credentials"/>
[998]318   HTTP provides a simple challenge-response authentication mechanism
319   that can be used by a server to challenge a client request and by a
320   client to provide authentication information. It uses an extensible,
[1394]321   case-insensitive token to identify the authentication scheme, followed
322   by additional information necessary for achieving authentication via that
323   scheme. The latter can either be a comma-separated list of attribute-value
324   pairs or a single sequence of characters capable of holding base64-encoded
325   information.
[1394]327<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="b64token" primary="true"/><iref primary="true" item="Grammar" subitem="b64token"/>
[1386]328  auth-scheme    = <x:ref>token</x:ref>
[1386]330  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> )
332  b64token       = 1*( <x:ref>ALPHA</x:ref> / <x:ref>DIGIT</x:ref> /
333                       "-" / "." / "_" / "~" / "+" / "/" ) *"="
[1394]336   The "b64token" syntax allows the 66 unreserved URI characters (<xref target="RFC3986"/>),
337   plus a few others, so that it can hold a base64, base64url (URL and filename
338   safe alphabet), base32, or base16 (hex) encoding, with or without padding, but
339   excluding whitespace (<xref target="RFC4648"/>).
[998]342   The 401 (Unauthorized) response message is used by an origin server
343   to challenge the authorization of a user agent. This response &MUST;
344   include a WWW-Authenticate header field containing at least one
[1344]345   challenge applicable to the requested resource.
348   The 407 (Proxy Authentication Required) response message is used by a proxy to
[998]349   challenge the authorization of a client and &MUST; include a Proxy-Authenticate
350   header field containing at least one challenge
351   applicable to the proxy for the requested resource.
[1387]353<figure><artwork type="abnf2616"><iref item="challenge" primary="true"/><iref primary="true" item="Grammar" subitem="challenge"/>
[1394]354  <x:ref>challenge</x:ref>   = <x:ref>auth-scheme</x:ref> [ 1*<x:ref>SP</x:ref> ( <x:ref>b64token</x:ref> / #<x:ref>auth-param</x:ref> ) ]
357  <t>
[1343]358     <x:h>Note:</x:h> User agents will need to take special care in parsing the
359     WWW-Authenticate and Proxy-Authenticate header field values because they
360     can contain more than one challenge, or if more than one of each is
361     provided, since the contents of a challenge can itself contain a
362     comma-separated list of authentication parameters.
[998]363  </t>
366  <t>
[1343]367     <x:h>Note:</x:h> Many browsers fail to parse challenges containing unknown
368     schemes. A workaround for this problem is to list well-supported schemes
[1344]369     (such as "basic") first.<!-- see -->
[1018]370  </t>
[1344]373   A user agent that wishes to authenticate itself with an origin server
374   &mdash; usually, but not necessarily, after receiving a 401 (Unauthorized)
375   &mdash; &MAY; do so by including an Authorization header field with the
376   request.
379   A client that wishes to authenticate itself with a proxy &mdash; usually,
380   but not necessarily, after receiving a 407 (Proxy Authentication Required)
381   &mdash; &MAY; do so by including a Proxy-Authorization header field with the
382   request.
385   Both the Authorization field value and the Proxy-Authorization field value
386   consist of credentials containing the authentication information of the
387   client for the realm of the resource being requested. The user agent &MUST;
[998]388   choose to use one of the challenges with the strongest auth-scheme it
[1344]389   understands and request credentials from the user based upon that challenge.
[1387]391<figure><artwork type="abnf2616"><iref item="credentials" primary="true"/><iref primary="true" item="Grammar" subitem="credentials"/>
[1394]392  <x:ref>credentials</x:ref> = <x:ref>auth-scheme</x:ref> [ 1*<x:ref>SP</x:ref> ( <x:ref>b64token</x:ref> / #<x:ref>auth-param</x:ref> ) ]
395   If the origin server does not wish to accept the credentials sent
396   with a request, it &SHOULD; return a 401 (Unauthorized) response. The
397   response &MUST; include a WWW-Authenticate header field containing at
398   least one (possibly new) challenge applicable to the requested
[1344]399   resource.
402   If a proxy does not accept the credentials sent with a
[998]403   request, it &SHOULD; return a 407 (Proxy Authentication Required). The
404   response &MUST; include a Proxy-Authenticate header field containing a
405   (possibly new) challenge applicable to the proxy for the requested
406   resource.
409   The HTTP protocol does not restrict applications to this simple
410   challenge-response mechanism for access authentication. Additional
411   mechanisms &MAY; be used, such as encryption at the transport level or
412   via message encapsulation, and with additional header fields
[1107]413   specifying authentication information. However, such additional
[998]414   mechanisms are not defined by this specification.
[1107]417   Proxies &MUST; forward the WWW-Authenticate and Authorization headers
418   unmodified and follow the rules found in <xref target="header.authorization"/>.
[1344]422<section title="Protection Space (Realm)" anchor="">
[1354]423  <iref item="Protection Space"/>
424  <iref item="Realm"/>
[1354]426   The authentication parameter realm is reserved for use by authentication
427   schemes that wish to indicate the scope of protection:
[1387]429<figure><artwork type="abnf2616"><iref item="realm" primary="true"/><iref item="realm-value" primary="true"/><iref primary="true" item="Grammar" subitem="realm"/>
[1395]430  realm       = "realm" <x:ref>BWS</x:ref> "=" <x:ref>BWS</x:ref> realm-value
[1344]431  realm-value = quoted-string
[1354]434   A <x:dfn>protection space</x:dfn> is defined by the canonical root URI (the
435   scheme and authority components of the effective request URI; see
436   <xref target="Part1" x:fmt="of" x:rel="#effective.request.uri"/>) of the
437   server being accessed, in combination with the realm value if present.
[1344]438   These realms allow the protected resources on a server to be
439   partitioned into a set of protection spaces, each with its own
440   authentication scheme and/or authorization database. The realm value
441   is a string, generally assigned by the origin server, which can have
442   additional semantics specific to the authentication scheme. Note that
443   there can be multiple challenges with the same auth-scheme but
444   different realms.
447   The protection space determines the domain over which credentials can
448   be automatically applied. If a prior request has been authorized, the
449   same credentials &MAY; be reused for all other requests within that
450   protection space for a period of time determined by the
451   authentication scheme, parameters, and/or user preference. Unless
452   otherwise defined by the authentication scheme, a single protection
453   space cannot extend outside the scope of its server.
[1026]457<section title="Authentication Scheme Registry" anchor="authentication.scheme.registry">
459  The HTTP Authentication Scheme Registry defines the name space for the
460  authentication schemes in challenges and credentials.
463  Registrations &MUST; include the following fields:
464  <list style="symbols">
465    <t>Authentication Scheme Name</t>
466    <t>Pointer to specification text</t>
[1371]467    <t>Notes (optional)</t>
[1026]468  </list>
471  Values to be added to this name space are subject to IETF review
472  (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>).
475  The registry itself is maintained at <eref target=""/>.
478<section title="Considerations for New Authentication Schemes" anchor="">
480  There are certain aspects of the HTTP Authentication Framework that put
481  constraints on how new authentication schemes can work:
484  <list style="symbols">
[1360]485    <x:lt>
[1356]486    <t>
487      Authentication schemes need to be compatible with the inherent
488      constraints of HTTP; for instance, that messages need to keep their
489      semantics when inspected in isolation, thus an authentication scheme
490      can not bind information to the TCP session over which the message
491      was received (see &msg-orient-and-buffering;).
492    </t>
[1360]493    </x:lt>
494    <x:lt>
[1356]495    <t>
496      The authentication parameter "realm" is reserved for defining Protection
497      Spaces as defined in <xref target=""/>. New schemes
498      &MUST-NOT; use it in a way incompatible with that definition.
499    </t>
[1360]500    </x:lt>
501    <x:lt>
[1356]502    <t>
[1394]503      The "b64token" notation was introduced for compatibility with existing
504      authentication schemes and can only be used once per challenge/credentials.
505      New schemes thus ought to use the "auth-param" syntax instead, because
506      otherwise future extensions will be impossible.
507    </t>
508    </x:lt>
509    <x:lt>
510    <t>
[1465]511      The parsing of challenges and credentials is defined by this specification,
512      and cannot be modified by new authentication schemes. When the auth-param
513      syntax is used, all parameters ought to support both token and
514      quoted-string syntax, and syntactical constraints ought to be defined on
515      the field value after parsing (i.e., quoted-string processing). This is
516      necessary so that recipients can use a generic parser that applies to
517      all authentication schemes.
518    </t>
519    <t>
520      <x:h>Note:</x:h> the fact that the value syntax for the "realm" parameter
521      is restricted to quoted-string was a bad design choice not to be repeated
522      for new parameters.
523    </t>
524    </x:lt>
525    <x:lt>
526    <t>
[1357]527      Authentication schemes need to document whether they are usable in
[1356]528      origin-server authentication (i.e., using WWW-Authenticate), and/or
529      proxy authentication (i.e., using Proxy-Authenticate).
[1360]530    </t>
531    </x:lt>
532    <x:lt>
533    <t>
534      The credentials carried in an Authorization header field are specific to
535      the User Agent, and therefore have the same effect on HTTP caches as the
536      "private" Cache-Control response directive, within the scope of the
537      request they appear in.
538    </t>
539    <t>
540      Therefore, new authentication schemes which choose not to carry
541      credentials in the Authorization header (e.g., using a newly defined
542      header) will need to explicitly disallow caching, by mandating the use of
543      either Cache-Control request directives (e.g., "no-store") or response
544      directives (e.g., "private").
545    </t>
546    </x:lt>
[1356]547  </list>
[838]555<section title="Status Code Definitions" anchor="status.code.definitions">
[39]556<section title="401 Unauthorized" anchor="status.401">
557  <iref primary="true" item="401 Unauthorized (status code)" x:for-anchor=""/>
558  <iref primary="true" item="Status Codes" subitem="401 Unauthorized" x:for-anchor=""/>
560   The request requires user authentication. The response &MUST; include a
561   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
[965]562   applicable to the target resource. The client &MAY; repeat the
[39]563   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
564   the request already included Authorization credentials, then the 401
565   response indicates that authorization has been refused for those
566   credentials. If the 401 response contains the same challenge as the
567   prior response, and the user agent has already attempted
568   authentication at least once, then the user &SHOULD; be presented the
[874]569   representation that was given in the response, since that representation might
[998]570   include relevant diagnostic information.
573<section title="407 Proxy Authentication Required" anchor="status.407">
574  <iref primary="true" item="407 Proxy Authentication Required (status code)" x:for-anchor=""/>
575  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required" x:for-anchor=""/>
577   This code is similar to 401 (Unauthorized), but indicates that the
[998]578   client ought to first authenticate itself with the proxy. The proxy &MUST;
[39]579   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
[965]580   challenge applicable to the proxy for the target resource. The
[39]581   client &MAY; repeat the request with a suitable Proxy-Authorization
[998]582   header field (<xref target="header.proxy-authorization"/>).
[1415]587<section title="Header Field Definitions" anchor="header.field.definitions">
[117]589   This section defines the syntax and semantics of HTTP/1.1 header fields
590   related to authentication.
593<section title="Authorization" anchor="header.authorization">
[1120]594  <iref primary="true" item="Authorization header field" x:for-anchor=""/>
595  <iref primary="true" item="Header Fields" subitem="Authorization" x:for-anchor=""/>
[229]596  <x:anchor-alias value="Authorization"/>
[1163]598   The "Authorization" header field allows a user agent to authenticate
[1101]599   itself with a server &mdash; usually, but not necessarily, after receiving a 401
[698]600   (Unauthorized) response. Its value consists of credentials containing
601   information of the user agent for the realm of the resource being
602   requested.
[1230]604<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Authorization"/>
605  <x:ref>Authorization</x:ref> = <x:ref>credentials</x:ref>
[998]608   If a request is
[698]609   authenticated and a realm specified, the same credentials &SHOULD;
610   be valid for all other requests within this realm (assuming that
611   the authentication scheme itself does not require otherwise, such
612   as credentials that vary according to a challenge value or using
613   synchronized clocks).
[29]616      When a shared cache (see &shared-and-non-shared-caches;) receives a request
[8]617      containing an Authorization field, it &MUST-NOT; return the
618      corresponding response as a reply to any other request, unless one
619      of the following specific exceptions holds:
622  <list style="numbers">
623      <t>If the response includes the "s-maxage" cache-control
624         directive, the cache &MAY; use that response in replying to a
625         subsequent request. But (if the specified maximum age has
626         passed) a proxy cache &MUST; first revalidate it with the origin
[1163]627         server, using the header fields from the new request to allow
[8]628         the origin server to authenticate the new request. (This is the
629         defined behavior for s-maxage.) If the response includes "s-maxage=0",
630         the proxy &MUST; always revalidate it before re-using
631         it.</t>
633      <t>If the response includes the "must-revalidate" cache-control
634         directive, the cache &MAY; use that response in replying to a
635         subsequent request. But if the response is stale, all caches
636         &MUST; first revalidate it with the origin server, using the
[1163]637         header fields from the new request to allow the origin server
[8]638         to authenticate the new request.</t>
640      <t>If the response includes the "public" cache-control directive,
641         it &MAY; be returned in reply to any subsequent request.</t>
642  </list>
646<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
[1120]647  <iref primary="true" item="Proxy-Authenticate header field" x:for-anchor=""/>
648  <iref primary="true" item="Header Fields" subitem="Proxy-Authenticate" x:for-anchor=""/>
[229]649  <x:anchor-alias value="Proxy-Authenticate"/>
[1163]651   The "Proxy-Authenticate" header field consists of a challenge that
[698]652   indicates the authentication scheme and parameters applicable to the proxy
[965]653   for this effective request URI (&effective-request-uri;). It &MUST; be included as part
[698]654   of a 407 (Proxy Authentication Required) response.
[1230]656<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/>
657  <x:ref>Proxy-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
[998]660   Unlike WWW-Authenticate, the Proxy-Authenticate header field applies only to
[8]661   the current connection and &SHOULD-NOT;  be passed on to downstream
662   clients. However, an intermediate proxy might need to obtain its own
663   credentials by requesting them from the downstream client, which in
664   some circumstances will appear as if the proxy is forwarding the
665   Proxy-Authenticate header field.
669<section title="Proxy-Authorization" anchor="header.proxy-authorization">
[1120]670  <iref primary="true" item="Proxy-Authorization header field" x:for-anchor=""/>
671  <iref primary="true" item="Header Fields" subitem="Proxy-Authorization" x:for-anchor=""/>
[229]672  <x:anchor-alias value="Proxy-Authorization"/>
[1163]674   The "Proxy-Authorization" header field allows the client to
[8]675   identify itself (or its user) to a proxy which requires
[698]676   authentication. Its value consists of
[8]677   credentials containing the authentication information of the user
678   agent for the proxy and/or realm of the resource being requested.
[1230]680<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/>
681  <x:ref>Proxy-Authorization</x:ref> = <x:ref>credentials</x:ref>
[998]684   Unlike Authorization, the Proxy-Authorization header field applies only to
[8]685   the next outbound proxy that demanded authentication using the Proxy-Authenticate
686   field. When multiple proxies are used in a chain, the
687   Proxy-Authorization header field is consumed by the first outbound
688   proxy that was expecting to receive credentials. A proxy &MAY; relay
689   the credentials from the client request to the next proxy if that is
690   the mechanism by which the proxies cooperatively authenticate a given
691   request.
695<section title="WWW-Authenticate" anchor="header.www-authenticate">
[1120]696  <iref primary="true" item="WWW-Authenticate header field" x:for-anchor=""/>
697  <iref primary="true" item="Header Fields" subitem="WWW-Authenticate" x:for-anchor=""/>
[229]698  <x:anchor-alias value="WWW-Authenticate"/>
[1163]700   The "WWW-Authenticate" header field consists of at least one
[698]701   challenge that indicates the authentication scheme(s) and parameters
[1360]702   applicable to the effective request URI (&effective-request-uri;).
705   It &MUST; be included in 401 (Unauthorized) response messages and &MAY; be
706   included in other response messages to indicate that supplying credentials
707   (or different credentials) might affect the response.
[1230]709<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/>
710  <x:ref>WWW-Authenticate</x:ref> = 1#<x:ref>challenge</x:ref>
[998]713   User agents are advised to take special care in parsing the WWW-Authenticate
[8]714   field value as it might contain more than one challenge,
715   or if more than one WWW-Authenticate header field is provided, the
716   contents of a challenge itself can contain a comma-separated list of
717   authentication parameters.
720  <preamble>For instance:</preamble>
721  <artwork type="example">
722  WWW-Authenticate: Newauth realm="apps", type=1,
723                    title="Login to \"apps\"", Basic realm="simple"
725  <postamble>
726  This header field contains two challenges; one for the "Newauth" scheme
727  with a realm value of "apps", and two additional parameters "type" and
728  "title", and another one for the "Basic" scheme with a realm value of "simple".
[29]734<section title="IANA Considerations" anchor="IANA.considerations">
[1026]736<section title="Authenticaton Scheme Registry" anchor="authentication.scheme.registration">
738  The registration procedure for HTTP Authentication Schemes is defined by
739  <xref target="authentication.scheme.registry"/> of this document.
742   The HTTP Method Authentication Scheme shall be created at <eref target=""/>.
[700]746<section title="Status Code Registration" anchor="status.code.registration">
748   The HTTP Status Code Registry located at <eref target=""/>
[969]749   shall be updated with the registrations below:
751<?BEGININC p7-auth.iana-status-codes ?>
752<!--AUTOGENERATED FROM extract-status-code-defs.xslt, do not edit manually-->
753<texttable align="left" suppress-title="true" anchor="iana.status.code.registration.table">
754   <ttcol>Value</ttcol>
755   <ttcol>Description</ttcol>
756   <ttcol>Reference</ttcol>
757   <c>401</c>
758   <c>Unauthorized</c>
759   <c>
760      <xref target="status.401"/>
761   </c>
762   <c>407</c>
763   <c>Proxy Authentication Required</c>
764   <c>
765      <xref target="status.407"/>
766   </c>
769<?ENDINC p7-auth.iana-status-codes ?>
[921]772<section title="Header Field Registration" anchor="header.field.registration">
[969]774   The Message Header Field Registry located at <eref target=""/> shall be updated
[290]775   with the permanent registrations below (see <xref target="RFC3864"/>):
[680]777<?BEGININC p7-auth.iana-headers ?>
[253]778<!--AUTOGENERATED FROM extract-header-defs.xslt, do not edit manually-->
[290]779<texttable align="left" suppress-title="true" anchor="iana.header.registration.table">
[253]780   <ttcol>Header Field Name</ttcol>
781   <ttcol>Protocol</ttcol>
782   <ttcol>Status</ttcol>
783   <ttcol>Reference</ttcol>
785   <c>Authorization</c>
786   <c>http</c>
787   <c>standard</c>
788   <c>
789      <xref target="header.authorization"/>
790   </c>
791   <c>Proxy-Authenticate</c>
792   <c>http</c>
793   <c>standard</c>
794   <c>
795      <xref target="header.proxy-authenticate"/>
796   </c>
797   <c>Proxy-Authorization</c>
798   <c>http</c>
799   <c>standard</c>
800   <c>
801      <xref target="header.proxy-authorization"/>
802   </c>
803   <c>WWW-Authenticate</c>
804   <c>http</c>
805   <c>standard</c>
806   <c>
807      <xref target="header.www-authenticate"/>
808   </c>
[680]811<?ENDINC p7-auth.iana-headers ?>
[290]813   The change controller is: "IETF ( - Internet Engineering Task Force".
818<section title="Security Considerations" anchor="security.considerations">
820   This section is meant to inform application developers, information
821   providers, and users of the security limitations in HTTP/1.1 as
822   described by this document. The discussion does not include
823   definitive solutions to the problems revealed, though it does make
824   some suggestions for reducing security risks.
827<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
829   Existing HTTP clients and user agents typically retain authentication
[145]830   information indefinitely. HTTP/1.1 does not provide a method for a
[8]831   server to direct clients to discard these cached credentials. This is
832   a significant defect that requires further extensions to HTTP.
833   Circumstances under which credential caching can interfere with the
834   application's security model include but are not limited to:
835  <list style="symbols">
836     <t>Clients which have been idle for an extended period following
837        which the server might wish to cause the client to reprompt the
838        user for credentials.</t>
840     <t>Applications which include a session termination indication
[746]841        (such as a "logout" or "commit" button on a page) after which
842        the server side of the application "knows" that there is no
[8]843        further reason for the client to retain the credentials.</t>
844  </list>
847   This is currently under separate study. There are a number of work-arounds
848   to parts of this problem, and we encourage the use of
849   password protection in screen savers, idle time-outs, and other
850   methods which mitigate the security problems inherent in this
851   problem. In particular, user agents which cache credentials are
852   encouraged to provide a readily accessible mechanism for discarding
853   cached credentials under user control.
[1364]858<section title="Acknowledgments" anchor="acks">
[998]860  This specification takes over the definition of the HTTP Authentication
[1363]861  Framework, previously defined in <xref target="RFC2617" x:fmt="none">RFC 2617</xref>.
862  We thank John Franks, Phillip M. Hallam-Baker, Jeffery L. Hostetler, Scott D. Lawrence,
[998]863  Paul J. Leach, Ari Luotonen, and Lawrence C. Stewart for their work
[1389]864  on that specification. See <xref target="RFC2617" x:fmt="of" x:sec="6"/>
[1363]865  for further acknowledgements. 
868  See &acks; for the Acknowledgments related to this document revision.
[119]875<references title="Normative References">
[205]877<reference anchor="Part1">
878  <front>
879    <title abbrev="HTTP/1.1">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</title>
880    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]881      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[205]882      <address><email></email></address>
883    </author>
884    <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]885      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
886      <address><email></email></address>
[205]887    </author>
888    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
889      <organization abbrev="HP">Hewlett-Packard Company</organization>
890      <address><email></email></address>
891    </author>
892    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
893      <organization abbrev="Microsoft">Microsoft Corporation</organization>
894      <address><email></email></address>
895    </author>
896    <author initials="L." surname="Masinter" fullname="Larry Masinter">
[1106]897      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[205]898      <address><email></email></address>
899    </author>
900    <author initials="P." surname="Leach" fullname="Paul J. Leach">
901      <organization abbrev="Microsoft">Microsoft Corporation</organization>
902      <address><email></email></address>
903    </author>
904    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
905      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
906      <address><email></email></address>
907    </author>
908    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
909      <organization abbrev="W3C">World Wide Web Consortium</organization>
910      <address><email></email></address>
911    </author>
912    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
913      <organization abbrev="greenbytes">greenbytes GmbH</organization>
914      <address><email></email></address>
915    </author>
916    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
917  </front>
918  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p1-messaging-&ID-VERSION;"/>
919  <x:source href="p1-messaging.xml" basename="p1-messaging"/>
[31]922<reference anchor="Part6">
[119]923  <front>
924    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
925    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
[1106]926      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]927      <address><email></email></address>
928    </author>
929    <author initials="J." surname="Gettys" fullname="Jim Gettys">
[844]930      <organization abbrev="Alcatel-Lucent">Alcatel-Lucent Bell Labs</organization>
931      <address><email></email></address>
[119]932    </author>
933    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
934      <organization abbrev="HP">Hewlett-Packard Company</organization>
935      <address><email></email></address>
936    </author>
937    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
938      <organization abbrev="Microsoft">Microsoft Corporation</organization>
939      <address><email></email></address>
940    </author>
941    <author initials="L." surname="Masinter" fullname="Larry Masinter">
[1106]942      <organization abbrev="Adobe">Adobe Systems Incorporated</organization>
[119]943      <address><email></email></address>
944    </author>
945    <author initials="P." surname="Leach" fullname="Paul J. Leach">
946      <organization abbrev="Microsoft">Microsoft Corporation</organization>
947      <address><email></email></address>
948    </author>
949    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
950      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
951      <address><email></email></address>
952    </author>
953    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
954      <organization abbrev="W3C">World Wide Web Consortium</organization>
955      <address><email></email></address>
956    </author>
[601]957    <author initials="M." surname="Nottingham" fullname="Mark Nottingham" role="editor">
[1440]958      <organization>Rackspace</organization>
[601]959      <address><email></email></address>
960    </author>
[119]961    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
962      <organization abbrev="greenbytes">greenbytes GmbH</organization>
963      <address><email></email></address>
964    </author>
965    <date month="&ID-MONTH;" year="&ID-YEAR;"/>
966  </front>
967  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-&ID-VERSION;"/>
968  <x:source href="p6-cache.xml" basename="p6-cache"/>
[96]971<reference anchor="RFC2119">
972  <front>
973    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
974    <author initials="S." surname="Bradner" fullname="Scott Bradner">
975      <organization>Harvard University</organization>
976      <address><email></email></address>
977    </author>
978    <date month="March" year="1997"/>
979  </front>
980  <seriesInfo name="BCP" value="14"/>
981  <seriesInfo name="RFC" value="2119"/>
[425]984<reference anchor="RFC5234">
985  <front>
986    <title abbrev="ABNF for Syntax Specifications">Augmented BNF for Syntax Specifications: ABNF</title>
987    <author initials="D." surname="Crocker" fullname="Dave Crocker" role="editor">
988      <organization>Brandenburg InternetWorking</organization>
989      <address>
[728]990        <email></email>
991      </address> 
[425]992    </author>
993    <author initials="P." surname="Overell" fullname="Paul Overell">
994      <organization>THUS plc.</organization>
995      <address>
[728]996        <email></email>
997      </address>
[425]998    </author>
999    <date month="January" year="2008"/>
1000  </front>
1001  <seriesInfo name="STD" value="68"/>
1002  <seriesInfo name="RFC" value="5234"/>
1007<references title="Informative References">
1009<reference anchor="RFC2616">
1010  <front>
1011    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
1012    <author initials="R." surname="Fielding" fullname="R. Fielding">
1013      <organization>University of California, Irvine</organization>
1014      <address><email></email></address>
1015    </author>
1016    <author initials="J." surname="Gettys" fullname="J. Gettys">
1017      <organization>W3C</organization>
1018      <address><email></email></address>
1019    </author>
1020    <author initials="J." surname="Mogul" fullname="J. Mogul">
1021      <organization>Compaq Computer Corporation</organization>
1022      <address><email></email></address>
1023    </author>
1024    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
1025      <organization>MIT Laboratory for Computer Science</organization>
1026      <address><email></email></address>
1027    </author>
1028    <author initials="L." surname="Masinter" fullname="L. Masinter">
1029      <organization>Xerox Corporation</organization>
1030      <address><email></email></address>
1031    </author>
1032    <author initials="P." surname="Leach" fullname="P. Leach">
1033      <organization>Microsoft Corporation</organization>
1034      <address><email></email></address>
1035    </author>
1036    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
1037      <organization>W3C</organization>
1038      <address><email></email></address>
1039    </author>
1040    <date month="June" year="1999"/>
1041  </front>
1042  <seriesInfo name="RFC" value="2616"/>
[998]1045<reference anchor="RFC2617">
1046  <front>
1047    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
1048    <author initials="J." surname="Franks" fullname="John Franks">
1049      <organization>Northwestern University, Department of Mathematics</organization>
1050      <address><email></email></address>
1051    </author>
1052    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
1053      <organization>Verisign Inc.</organization>
1054      <address><email></email></address>
1055    </author>
1056    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
1057      <organization>AbiSource, Inc.</organization>
1058      <address><email></email></address>
1059    </author>
1060    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
1061      <organization>Agranat Systems, Inc.</organization>
1062      <address><email></email></address>
1063    </author>
1064    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
1065      <organization>Microsoft Corporation</organization>
1066      <address><email></email></address>
1067    </author>
1068    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
1069      <organization>Netscape Communications Corporation</organization>
1070    </author>
1071    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
1072      <organization>Open Market, Inc.</organization>
1073      <address><email></email></address>
1074    </author>
1075    <date month="June" year="1999"/>
1076  </front>
1077  <seriesInfo name="RFC" value="2617"/>
[253]1080<reference anchor='RFC3864'>
1081  <front>
1082    <title>Registration Procedures for Message Header Fields</title>
1083    <author initials='G.' surname='Klyne' fullname='G. Klyne'>
1084      <organization>Nine by Nine</organization>
1085      <address><email></email></address>
1086    </author>
1087    <author initials='M.' surname='Nottingham' fullname='M. Nottingham'>
1088      <organization>BEA Systems</organization>
1089      <address><email></email></address>
1090    </author>
1091    <author initials='J.' surname='Mogul' fullname='J. Mogul'>
1092      <organization>HP Labs</organization>
1093      <address><email></email></address>
1094    </author>
1095    <date year='2004' month='September' />
1096  </front>
1097  <seriesInfo name='BCP' value='90' />
1098  <seriesInfo name='RFC' value='3864' />
[1394]1101<reference anchor="RFC3986">
1102 <front>
1103  <title abbrev='URI Generic Syntax'>Uniform Resource Identifier (URI): Generic Syntax</title>
1104  <author initials='T.' surname='Berners-Lee' fullname='Tim Berners-Lee'>
1105    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
1106    <address>
1107       <email></email>
1108       <uri></uri>
1109    </address>
1110  </author>
1111  <author initials='R.' surname='Fielding' fullname='Roy T. Fielding'>
1112    <organization abbrev="Day Software">Day Software</organization>
1113    <address>
1114      <email></email>
1115      <uri></uri>
1116    </address>
1117  </author>
1118  <author initials='L.' surname='Masinter' fullname='Larry Masinter'>
1119    <organization abbrev="Adobe Systems">Adobe Systems Incorporated</organization>
1120    <address>
1121      <email></email>
1122      <uri></uri>
1123    </address>
1124  </author>
1125  <date month='January' year='2005'></date>
1126 </front>
1127 <seriesInfo name="STD" value="66"/>
1128 <seriesInfo name="RFC" value="3986"/>
1131<reference anchor="RFC4648">
1132  <front>
1133    <title>The Base16, Base32, and Base64 Data Encodings</title>
1134    <author fullname="S. Josefsson" initials="S." surname="Josefsson"/>
1135    <date year="2006" month="October"/>
1136  </front>
1137  <seriesInfo value="4648" name="RFC"/>
[1026]1140<reference anchor='RFC5226'>
1141  <front>
1142    <title>Guidelines for Writing an IANA Considerations Section in RFCs</title>
1143    <author initials='T.' surname='Narten' fullname='T. Narten'>
1144      <organization>IBM</organization>
1145      <address><email></email></address>
1146    </author>
1147    <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'>
1148      <organization>Google</organization>
1149      <address><email></email></address>
1150    </author>
1151    <date year='2008' month='May' />
1152  </front>
1153  <seriesInfo name='BCP' value='26' />
1154  <seriesInfo name='RFC' value='5226' />
[1385]1159<section title="Changes from RFCs 2616 and 2617" anchor="changes.from.rfc.2616">
[1385]1161  The "realm" parameter isn't required anymore in general; consequently, the
1162  ABNF allows challenges without any auth parameters.
1163  (<xref target="access.authentication.framework"/>)
[1394]1166  The "b64token" alternative to auth-param lists has been added for consistency
1167  with legacy authentication schemes such as "Basic".
1168  (<xref target="access.authentication.framework"/>)
[1230]1171  Change ABNF productions for header fields to only define the field value.
[1415]1172  (<xref target="header.field.definitions"/>)
[680]1176<?BEGININC p7-auth.abnf-appendix ?>
[427]1177<section xmlns:x="" title="Collected ABNF" anchor="collected.abnf">
1179<artwork type="abnf" name="p7-auth.parsed-abnf">
[1230]1180<x:ref>Authorization</x:ref> = credentials
[1386]1182<x:ref>BWS</x:ref> = &lt;BWS, defined in [Part1], Section 1.2.2&gt;
[427]1184<x:ref>OWS</x:ref> = &lt;OWS, defined in [Part1], Section 1.2.2&gt;
[1230]1186<x:ref>Proxy-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS
[425]1187 challenge ] )
[1230]1188<x:ref>Proxy-Authorization</x:ref> = credentials
[1230]1190<x:ref>WWW-Authenticate</x:ref> = *( "," OWS ) challenge *( OWS "," [ OWS challenge
1191 ] )
[1386]1193<x:ref>auth-param</x:ref> = token BWS "=" BWS ( token / quoted-string )
[998]1194<x:ref>auth-scheme</x:ref> = token
[1394]1196<x:ref>b64token</x:ref> = 1*( ALPHA / DIGIT / "-" / "." / "_" / "~" / "+" / "/" )
1197 *"="
[1394]1199<x:ref>challenge</x:ref> = auth-scheme [ 1*SP ( b64token / [ ( "," / auth-param ) *(
1200 OWS "," [ OWS auth-param ] ) ] ) ]
1201<x:ref>credentials</x:ref> = auth-scheme [ 1*SP ( b64token / [ ( "," / auth-param )
1202 *( OWS "," [ OWS auth-param ] ) ] ) ]
[1396]1204<x:ref>quoted-string</x:ref> = &lt;quoted-string, defined in [Part1], Section 3.2.3&gt;
[1395]1206realm = "realm" BWS "=" BWS realm-value
[998]1207realm-value = quoted-string
[1396]1209<x:ref>token</x:ref> = &lt;token, defined in [Part1], Section 3.2.3&gt;
[532]1212<figure><preamble>ABNF diagnostics:</preamble><artwork type="inline">
1213; Authorization defined but not used
[425]1214; Proxy-Authenticate defined but not used
1215; Proxy-Authorization defined but not used
1216; WWW-Authenticate defined but not used
[998]1217; realm defined but not used
[680]1219<?ENDINC p7-auth.abnf-appendix ?>
[252]1221<section title="Change Log (to be removed by RFC Editor before publication)"  anchor="change.log">
[1002]1223<section title="Since RFC 2616">
1225  Extracted relevant partitions from <xref target="RFC2616"/>.
1229<section title="Since draft-ietf-httpbis-p7-auth-00">
[152]1231  Closed issues:
1232  <list style="symbols"> 
[119]1233    <t>
[324]1234      <eref target=""/>:
[152]1235      "Normative and Informative references"
[119]1236    </t>
1237  </list>
[170]1241<section title="Since draft-ietf-httpbis-p7-auth-01">
[324]1243  Ongoing work on ABNF conversion (<eref target=""/>):
[191]1244  <list style="symbols"> 
1245    <t>
1246      Explicitly import BNF rules for "challenge" and "credentials" from RFC2617.
1247    </t>
[205]1248    <t>
1249      Add explicit references to BNF syntax and rules imported from other parts of the specification.
1250    </t>
[191]1251  </list>
[252]1255<section title="Since draft-ietf-httpbis-p7-auth-02" anchor="changes.since.02">
[994]1257  Ongoing work on IANA Message Header Field Registration (<eref target=""/>):
[253]1258  <list style="symbols"> 
1259    <t>
[994]1260      Reference RFC 3984, and update header field registrations for header fields defined
[253]1261      in this document.
1262    </t>
1263  </list>
[267]1267<section title="Since draft-ietf-httpbis-p7-auth-03" anchor="changes.since.03">
[1388]1269  None.
[323]1273<section title="Since draft-ietf-httpbis-p7-auth-04" anchor="changes.since.04">
[365]1275  Ongoing work on ABNF conversion (<eref target=""/>):
1276  <list style="symbols"> 
1277    <t>
1278      Use "/" instead of "|" for alternatives.
1279    </t>
1280    <t>
1281      Introduce new ABNF rules for "bad" whitespace ("BWS"), optional
1282      whitespace ("OWS") and required whitespace ("RWS").
1283    </t>
1284    <t>
1285      Rewrite ABNFs to spell out whitespace rules, factor out
[994]1286      header field value format definitions.
[365]1287    </t>
1288  </list>
[382]1292<section title="Since draft-ietf-httpbis-p7-auth-05" anchor="changes.since.05">
[543]1294  Final work on ABNF conversion (<eref target=""/>):
[421]1295  <list style="symbols"> 
1296    <t>
[424]1297      Add appendix containing collected and expanded ABNF, reorganize ABNF introduction.
[421]1298    </t>
1299  </list>
[547]1303<section title="Since draft-ietf-httpbis-p7-auth-06" anchor="changes.since.06">
[603]1305  None.
[604]1309<section title="Since draft-ietf-httpbis-p7-auth-07" anchor="changes.since.07">
[700]1311  Closed issues:
1312  <list style="symbols"> 
1313    <t>
1314      <eref target=""/>:
1315      "move IANA registrations for optional status codes"
1316    </t>
1317  </list>
[720]1321<section title="Since draft-ietf-httpbis-p7-auth-08" anchor="changes.since.08">
[765]1323  No significant changes.
[773]1327<section title="Since draft-ietf-httpbis-p7-auth-09" anchor="changes.since.09">
[823]1329  Partly resolved issues:
1330  <list style="symbols"> 
1331    <t>
1332      <eref target=""/>:
1333      "Term for the requested resource's URI"
1334    </t>
1335  </list>
[841]1339<section title="Since draft-ietf-httpbis-p7-auth-10" anchor="changes.since.10">
[1328]1341  None.
[973]1345<section title="Since draft-ietf-httpbis-p7-auth-11" anchor="changes.since.11">
[998]1347  Closed issues:
1348  <list style="symbols"> 
1349    <t>
[1006]1350      <eref target=""/>:
1351      "introduction to part 7 is work-in-progress"
1352    </t>
1353    <t>
[998]1354      <eref target=""/>:
1355      "auth-param syntax"
1356    </t>
1357    <t>
[1165]1358      <eref target=""/>:
1359      "Header Classification"
1360    </t>
1361    <t>
[998]1362      <eref target=""/>:
1363      "absorbing the auth framework from 2617"
1364    </t>
1365  </list>
1368  Partly resolved issues:
1369  <list style="symbols"> 
1370    <t>
1371      <eref target=""/>:
1372      "should we have an auth scheme registry"
1373    </t>
1374  </list>
[1052]1378<section title="Since draft-ietf-httpbis-p7-auth-12" anchor="changes.since.12">
[1180]1380  None.
1384<section title="Since draft-ietf-httpbis-p7-auth-13" anchor="changes.since.13">
[1230]1386  Closed issues:
1387  <list style="symbols">
1388    <t>
1389      <eref target=""/>:
1390      "untangle ABNFs for header fields"
1391    </t>
1392  </list>
[1271]1396<section title="Since draft-ietf-httpbis-p7-auth-14" anchor="changes.since.14">
[1328]1398  None.
[1326]1402<section title="Since draft-ietf-httpbis-p7-auth-15" anchor="changes.since.15">
[1354]1404  Closed issues:
1405  <list style="symbols">
1406    <t>
[1360]1407      <eref target=""/>:
1408      "Relationship between 401, Authorization and WWW-Authenticate"
1409    </t>
1410    <t>
[1354]1411      <eref target=""/>:
1412      "Realm required on challenges"
1413    </t>
[1356]1414    <t>
[1394]1415      <eref target=""/>:
1416      "auth-param syntax"
1417    </t>
1418    <t>
[1356]1419      <eref target=""/>:
1420      "Considerations for new authentications schemes"
1421    </t>
[1378]1422    <t>
[1386]1423      <eref target=""/>:
1424      "LWS in auth-param ABNF"
1425    </t>
1426    <t>
[1378]1427      <eref target=""/>:
1428      "credentials ABNF missing SP (still using implied LWS?)"
1429    </t>
[1354]1430  </list>
[1401]1434<section title="Since draft-ietf-httpbis-p7-auth-16" anchor="changes.since.16">
[1452]1436  Closed issues:
1437  <list style="symbols"> 
1438    <t>
1439      <eref target=""/>:
1440      "Document HTTP's error-handling philosophy"
1441    </t>
[1465]1442    <t>
1443      <eref target=""/>:
1444      "add advice on defining auth scheme parameters"
1445    </t>
[1452]1446  </list>
[1467]1450<section title="Since draft-ietf-httpbis-p7-auth-17" anchor="changes.since.17">
1452  No changes yet.
Note: See TracBrowser for help on using the repository browser.