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

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

add BWS ("bad" whitespace) around "=" in auth-param (see #287)

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