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

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

clarify not about parsing *-Authenticate header fields

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