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

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

Relationship between 401, Authorization and WWW-Authenticate (see #78)

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