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

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

add 'notes' entry to auth scheme registry (see #141)

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