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

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

align sbatracts and put a paragraph break inside for readability

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