source: draft-ietf-httpbis/01/draft-ietf-httpbis-p7-auth-01.xml @ 166

Last change on this file since 166 was 166, checked in by fielding@…, 12 years ago

generated draft 01

  • Property svn:eol-style set to native
File size: 25.1 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!--
3    This XML document is the output of clean-for-DTD.xslt; a tool that strips
4    extensions to RFC2629(bis) from documents for processing with xml2rfc.
5-->
6<?xml-stylesheet type='text/xsl' href='../myxml2rfc.xslt'?>
7<?rfc toc="yes" ?>
8<?rfc symrefs="yes" ?>
9<?rfc sortrefs="yes" ?>
10<?rfc compact="yes"?>
11<?rfc subcompact="no" ?>
12<?rfc linkmailto="no" ?>
13<?rfc editing="no" ?>
14<!DOCTYPE rfc
15  PUBLIC "" "rfc2629.dtd">
16<rfc obsoletes="2616" updates="2617" category="std" ipr="full3978" docName="draft-ietf-httpbis-p7-auth-01">
17<front>
18
19  <title abbrev="HTTP/1.1, Part 7">HTTP/1.1, part 7: Authentication</title>
20
21  <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
22    <organization abbrev="Day Software">Day Software</organization>
23    <address>
24      <postal>
25        <street>23 Corporate Plaza DR, Suite 280</street>
26        <city>Newport Beach</city>
27        <region>CA</region>
28        <code>92660</code>
29        <country>USA</country>
30      </postal>
31      <phone>+1-949-706-5300</phone>
32      <facsimile>+1-949-706-5305</facsimile>
33      <email>fielding@gbiv.com</email>
34      <uri>http://roy.gbiv.com/</uri>
35    </address>
36  </author>
37
38  <author initials="J." surname="Gettys" fullname="Jim Gettys">
39    <organization>One Laptop per Child</organization>
40    <address>
41      <postal>
42        <street>21 Oak Knoll Road</street>
43        <city>Carlisle</city>
44        <region>MA</region>
45        <code>01741</code>
46        <country>USA</country>
47      </postal>
48      <email>jg@laptop.org</email>
49      <uri>http://www.laptop.org/</uri>
50    </address>
51  </author>
52 
53  <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
54    <organization abbrev="HP">Hewlett-Packard Company</organization>
55    <address>
56      <postal>
57        <street>HP Labs, Large Scale Systems Group</street>
58        <street>1501 Page Mill Road, MS 1177</street>
59        <city>Palo Alto</city>
60        <region>CA</region>
61        <code>94304</code>
62        <country>USA</country>
63      </postal>
64      <email>JeffMogul@acm.org</email>
65    </address>
66  </author>
67
68  <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
69    <organization abbrev="Microsoft">Microsoft Corporation</organization>
70    <address>
71      <postal>
72        <street>1 Microsoft Way</street>
73        <city>Redmond</city>
74        <region>WA</region>
75        <code>98052</code>
76        <country>USA</country>
77      </postal>
78      <email>henrikn@microsoft.com</email>
79    </address>
80  </author>
81
82  <author initials="L." surname="Masinter" fullname="Larry Masinter">
83    <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
84    <address>
85      <postal>
86        <street>345 Park Ave</street>
87        <city>San Jose</city>
88        <region>CA</region>
89        <code>95110</code>
90        <country>USA</country>
91      </postal>
92      <email>LMM@acm.org</email>
93      <uri>http://larry.masinter.net/</uri>
94    </address>
95  </author>
96 
97  <author initials="P." surname="Leach" fullname="Paul J. Leach">
98    <organization abbrev="Microsoft">Microsoft Corporation</organization>
99    <address>
100      <postal>
101        <street>1 Microsoft Way</street>
102        <city>Redmond</city>
103        <region>WA</region>
104        <code>98052</code>
105      </postal>
106      <email>paulle@microsoft.com</email>
107    </address>
108  </author>
109   
110  <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
111    <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
112    <address>
113      <postal>
114        <street>MIT Computer Science and Artificial Intelligence Laboratory</street>
115        <street>The Stata Center, Building 32</street>
116        <street>32 Vassar Street</street>
117        <city>Cambridge</city>
118        <region>MA</region>
119        <code>02139</code>
120        <country>USA</country>
121      </postal>
122      <email>timbl@w3.org</email>
123      <uri>http://www.w3.org/People/Berners-Lee/</uri>
124    </address>
125  </author>
126
127  <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
128    <organization abbrev="W3C">World Wide Web Consortium</organization>
129    <address>
130      <postal>
131        <street>W3C / ERCIM</street>
132        <street>2004, rte des Lucioles</street>
133        <city>Sophia-Antipolis</city>
134        <region>AM</region>
135        <code>06902</code>
136        <country>France</country>
137      </postal>
138      <email>ylafon@w3.org</email>
139      <uri>http://www.raubacapeu.net/people/yves/</uri>
140    </address>
141  </author>
142
143  <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
144    <organization abbrev="greenbytes">greenbytes GmbH</organization>
145    <address>
146      <postal>
147        <street>Hafenweg 16</street>
148        <city>Muenster</city><region>NW</region><code>48155</code>
149        <country>Germany</country>
150      </postal>
151      <phone>+49 251 2807760</phone>   
152      <facsimile>+49 251 2807761</facsimile>   
153      <email>julian.reschke@greenbytes.de</email>       
154      <uri>http://greenbytes.de/tech/webdav/</uri>     
155    </address>
156  </author>
157
158  <date month="January" year="2008" day="12"/>
159
160<abstract>
161<t>
162   The Hypertext Transfer Protocol (HTTP) is an application-level
163   protocol for distributed, collaborative, hypermedia information
164   systems. HTTP has been in use by the World Wide Web global information
165   initiative since 1990. This document is Part 7 of the seven-part specification
166   that defines the protocol referred to as "HTTP/1.1" and, taken together,
167   obsoletes RFC 2616.  Part 7 defines HTTP Authentication.
168</t>
169</abstract>
170
171<note title="Editorial Note (To be removed by RFC Editor)">
172  <t>
173    Discussion of this draft should take place on the HTTPBIS working group
174    mailing list (ietf-http-wg@w3.org). The current issues list is
175    at <eref target="http://www.tools.ietf.org/wg/httpbis/trac/report/11"/>
176    and related documents (including fancy diffs) can be found at
177    <eref target="http://www.tools.ietf.org/wg/httpbis/"/>.
178  </t>
179  <t>
180    This draft incorporates those issue resolutions that were either
181    collected in the original RFC2616 errata list (<eref target="http://purl.org/NET/http-errata"/>),
182    or which were agreed upon on the mailing list between October 2006 and
183    November 2007 (as published in "draft-lafon-rfc2616bis-03").
184  </t>
185</note>
186</front>
187<middle>
188<section title="Introduction" anchor="introduction">
189<t>
190   This document defines HTTP/1.1 access control and authentication. Right now it
191   includes the extracted relevant sections of
192   RFC 2616 with only minor changes.
193   The intention is to move the general framework for HTTP authentication here,
194   as currently specified in <xref target="RFC2617"/>, and allow the individual
195   authentication mechanisms to be defined elsewhere.  This introduction will
196   be rewritten when that occurs.
197</t>
198<t>
199   HTTP provides several OPTIONAL challenge-response authentication
200   mechanisms which can be used by a server to challenge a client
201   request and by a client to provide authentication information. The
202   general framework for access authentication, and the specification of
203   "basic" and "digest" authentication, are specified in "HTTP
204   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. This
205   specification adopts the definitions of "challenge" and "credentials"
206   from that specification.
207</t>
208
209<section title="Requirements" anchor="intro.requirements">
210<t>
211   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
212   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
213   document are to be interpreted as described in <xref target="RFC2119"/>.
214</t>
215<t>
216   An implementation is not compliant if it fails to satisfy one or more
217   of the MUST or REQUIRED level requirements for the protocols it
218   implements. An implementation that satisfies all the MUST or REQUIRED
219   level and all the SHOULD level requirements for its protocols is said
220   to be "unconditionally compliant"; one that satisfies all the MUST
221   level requirements but not all the SHOULD level requirements for its
222   protocols is said to be "conditionally compliant."
223</t>
224</section>
225</section>
226
227<section title="Status Code Definitions">
228<section title="401 Unauthorized" anchor="status.401">
229  <iref primary="true" item="401 Unauthorized (status code)"/>
230  <iref primary="true" item="Status Codes" subitem="401 Unauthorized"/>
231<t>
232   The request requires user authentication. The response MUST include a
233   WWW-Authenticate header field (<xref target="header.www-authenticate"/>) containing a challenge
234   applicable to the requested resource. The client MAY repeat the
235   request with a suitable Authorization header field (<xref target="header.authorization"/>). If
236   the request already included Authorization credentials, then the 401
237   response indicates that authorization has been refused for those
238   credentials. If the 401 response contains the same challenge as the
239   prior response, and the user agent has already attempted
240   authentication at least once, then the user SHOULD be presented the
241   entity that was given in the response, since that entity might
242   include relevant diagnostic information. HTTP access authentication
243   is explained in "HTTP Authentication: Basic and Digest Access
244   Authentication" <xref target="RFC2617"/>.
245</t>
246</section>
247<section title="407 Proxy Authentication Required" anchor="status.407">
248  <iref primary="true" item="407 Proxy Authentication Required (status code)"/>
249  <iref primary="true" item="Status Codes" subitem="407 Proxy Authentication Required"/>
250<t>
251   This code is similar to 401 (Unauthorized), but indicates that the
252   client must first authenticate itself with the proxy. The proxy MUST
253   return a Proxy-Authenticate header field (<xref target="header.proxy-authenticate"/>) containing a
254   challenge applicable to the proxy for the requested resource. The
255   client MAY repeat the request with a suitable Proxy-Authorization
256   header field (<xref target="header.proxy-authorization"/>). HTTP access authentication is explained
257   in "HTTP Authentication: Basic and Digest Access Authentication"
258   <xref target="RFC2617"/>.
259</t>
260</section>
261</section>
262
263<section title="Header Field Definitions" anchor="header.fields">
264<t>
265   This section defines the syntax and semantics of HTTP/1.1 header fields
266   related to authentication.
267</t>
268
269<section title="Authorization" anchor="header.authorization">
270  <iref primary="true" item="Authorization header"/>
271  <iref primary="true" item="Headers" subitem="Authorization"/>
272<t>
273      A user agent that wishes to authenticate itself with a server--
274      usually, but not necessarily, after receiving a 401 response--does
275      so by including an Authorization request-header field with the
276      request.  The Authorization field value consists of credentials
277      containing the authentication information of the user agent for
278      the realm of the resource being requested.
279</t>
280<figure><iref primary="true" item="Grammar" subitem="Authorization"/><artwork type="abnf2616"><![CDATA[
281  Authorization  = "Authorization" ":" credentials
282]]></artwork></figure>
283<t>
284      HTTP access authentication is described in "HTTP Authentication:
285      Basic and Digest Access Authentication" <xref target="RFC2617"/>. If a request is
286      authenticated and a realm specified, the same credentials SHOULD
287      be valid for all other requests within this realm (assuming that
288      the authentication scheme itself does not require otherwise, such
289      as credentials that vary according to a challenge value or using
290      synchronized clocks).
291</t>
292<t>
293      When a shared cache (see Section 8 of <xref target="Part6"/>) receives a request
294      containing an Authorization field, it MUST NOT return the
295      corresponding response as a reply to any other request, unless one
296      of the following specific exceptions holds:
297</t>
298<t>
299  <list style="numbers">
300      <t>If the response includes the "s-maxage" cache-control
301         directive, the cache MAY use that response in replying to a
302         subsequent request. But (if the specified maximum age has
303         passed) a proxy cache MUST first revalidate it with the origin
304         server, using the request-headers from the new request to allow
305         the origin server to authenticate the new request. (This is the
306         defined behavior for s-maxage.) If the response includes "s-maxage=0",
307         the proxy MUST always revalidate it before re-using
308         it.</t>
309
310      <t>If the response includes the "must-revalidate" cache-control
311         directive, the cache MAY use that response in replying to a
312         subsequent request. But if the response is stale, all caches
313         MUST first revalidate it with the origin server, using the
314         request-headers from the new request to allow the origin server
315         to authenticate the new request.</t>
316
317      <t>If the response includes the "public" cache-control directive,
318         it MAY be returned in reply to any subsequent request.</t>
319  </list>
320</t>
321</section>
322
323<section title="Proxy-Authenticate" anchor="header.proxy-authenticate">
324  <iref primary="true" item="Proxy-Authenticate header"/>
325  <iref primary="true" item="Headers" subitem="Proxy-Authenticate"/>
326<t>
327   The Proxy-Authenticate response-header field MUST be included as part
328   of a 407 (Proxy Authentication Required) response. The field value
329   consists of a challenge that indicates the authentication scheme and
330   parameters applicable to the proxy for this Request-URI.
331</t>
332<figure><iref primary="true" item="Grammar" subitem="Proxy-Authenticate"/><artwork type="abnf2616"><![CDATA[
333  Proxy-Authenticate  = "Proxy-Authenticate" ":" 1#challenge
334]]></artwork></figure>
335<t>
336   The HTTP access authentication process is described in "HTTP
337   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
338   WWW-Authenticate, the Proxy-Authenticate header field applies only to
339   the current connection and SHOULD NOT  be passed on to downstream
340   clients. However, an intermediate proxy might need to obtain its own
341   credentials by requesting them from the downstream client, which in
342   some circumstances will appear as if the proxy is forwarding the
343   Proxy-Authenticate header field.
344</t>
345</section>
346
347<section title="Proxy-Authorization" anchor="header.proxy-authorization">
348  <iref primary="true" item="Proxy-Authorization header"/>
349  <iref primary="true" item="Headers" subitem="Proxy-Authorization"/>
350<t>
351   The Proxy-Authorization request-header field allows the client to
352   identify itself (or its user) to a proxy which requires
353   authentication. The Proxy-Authorization field value consists of
354   credentials containing the authentication information of the user
355   agent for the proxy and/or realm of the resource being requested.
356</t>
357<figure><iref primary="true" item="Grammar" subitem="Proxy-Authorization"/><artwork type="abnf2616"><![CDATA[
358  Proxy-Authorization     = "Proxy-Authorization" ":" credentials
359]]></artwork></figure>
360<t>
361   The HTTP access authentication process is described in "HTTP
362   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. Unlike
363   Authorization, the Proxy-Authorization header field applies only to
364   the next outbound proxy that demanded authentication using the Proxy-Authenticate
365   field. When multiple proxies are used in a chain, the
366   Proxy-Authorization header field is consumed by the first outbound
367   proxy that was expecting to receive credentials. A proxy MAY relay
368   the credentials from the client request to the next proxy if that is
369   the mechanism by which the proxies cooperatively authenticate a given
370   request.
371</t>
372</section>
373
374<section title="WWW-Authenticate" anchor="header.www-authenticate">
375  <iref primary="true" item="WWW-Authenticate header"/>
376  <iref primary="true" item="Headers" subitem="WWW-Authenticate"/>
377<t>
378   The WWW-Authenticate response-header field MUST be included in 401
379   (Unauthorized) response messages. The field value consists of at
380   least one challenge that indicates the authentication scheme(s) and
381   parameters applicable to the Request-URI.
382</t>
383<figure><iref primary="true" item="Grammar" subitem="WWW-Authenticate"/><artwork type="abnf2616"><![CDATA[
384  WWW-Authenticate  = "WWW-Authenticate" ":" 1#challenge
385]]></artwork></figure>
386<t>
387   The HTTP access authentication process is described in "HTTP
388   Authentication: Basic and Digest Access Authentication" <xref target="RFC2617"/>. User
389   agents are advised to take special care in parsing the WWW-Authenticate
390   field value as it might contain more than one challenge,
391   or if more than one WWW-Authenticate header field is provided, the
392   contents of a challenge itself can contain a comma-separated list of
393   authentication parameters.
394</t>
395</section>
396
397</section>
398
399<section title="IANA Considerations" anchor="IANA.considerations">
400<t>
401   TBD.
402</t>
403</section>
404
405<section title="Security Considerations" anchor="security.considerations">
406<t>
407   This section is meant to inform application developers, information
408   providers, and users of the security limitations in HTTP/1.1 as
409   described by this document. The discussion does not include
410   definitive solutions to the problems revealed, though it does make
411   some suggestions for reducing security risks.
412</t>
413
414<section title="Authentication Credentials and Idle Clients" anchor="auth.credentials.and.idle.clients">
415<t>
416   Existing HTTP clients and user agents typically retain authentication
417   information indefinitely. HTTP/1.1 does not provide a method for a
418   server to direct clients to discard these cached credentials. This is
419   a significant defect that requires further extensions to HTTP.
420   Circumstances under which credential caching can interfere with the
421   application's security model include but are not limited to:
422  <list style="symbols">
423     <t>Clients which have been idle for an extended period following
424        which the server might wish to cause the client to reprompt the
425        user for credentials.</t>
426
427     <t>Applications which include a session termination indication
428        (such as a `logout' or `commit' button on a page) after which
429        the server side of the application `knows' that there is no
430        further reason for the client to retain the credentials.</t>
431  </list>
432</t>
433<t>
434   This is currently under separate study. There are a number of work-arounds
435   to parts of this problem, and we encourage the use of
436   password protection in screen savers, idle time-outs, and other
437   methods which mitigate the security problems inherent in this
438   problem. In particular, user agents which cache credentials are
439   encouraged to provide a readily accessible mechanism for discarding
440   cached credentials under user control.
441</t>
442</section>
443</section>
444
445<section title="Acknowledgments" anchor="ack">
446<t>
447  TBD.
448</t>
449</section>
450</middle>
451
452<back>
453
454<references title="Normative References">
455
456<reference anchor="Part6">
457  <front>
458    <title abbrev="HTTP/1.1">HTTP/1.1, part 6: Caching</title>
459    <author initials="R." surname="Fielding" fullname="Roy T. Fielding" role="editor">
460      <organization abbrev="Day Software">Day Software</organization>
461      <address><email>fielding@gbiv.com</email></address>
462    </author>
463    <author initials="J." surname="Gettys" fullname="Jim Gettys">
464      <organization>One Laptop per Child</organization>
465      <address><email>jg@laptop.org</email></address>
466    </author>
467    <author initials="J." surname="Mogul" fullname="Jeffrey C. Mogul">
468      <organization abbrev="HP">Hewlett-Packard Company</organization>
469      <address><email>JeffMogul@acm.org</email></address>
470    </author>
471    <author initials="H." surname="Frystyk" fullname="Henrik Frystyk Nielsen">
472      <organization abbrev="Microsoft">Microsoft Corporation</organization>
473      <address><email>henrikn@microsoft.com</email></address>
474    </author>
475    <author initials="L." surname="Masinter" fullname="Larry Masinter">
476      <organization abbrev="Adobe Systems">Adobe Systems, Incorporated</organization>
477      <address><email>LMM@acm.org</email></address>
478    </author>
479    <author initials="P." surname="Leach" fullname="Paul J. Leach">
480      <organization abbrev="Microsoft">Microsoft Corporation</organization>
481      <address><email>paulle@microsoft.com</email></address>
482    </author>
483    <author initials="T." surname="Berners-Lee" fullname="Tim Berners-Lee">
484      <organization abbrev="W3C/MIT">World Wide Web Consortium</organization>
485      <address><email>timbl@w3.org</email></address>
486    </author>
487    <author initials="Y." surname="Lafon" fullname="Yves Lafon" role="editor">
488      <organization abbrev="W3C">World Wide Web Consortium</organization>
489      <address><email>ylafon@w3.org</email></address>
490    </author>
491    <author initials="J. F." surname="Reschke" fullname="Julian F. Reschke" role="editor">
492      <organization abbrev="greenbytes">greenbytes GmbH</organization>
493      <address><email>julian.reschke@greenbytes.de</email></address>
494    </author>
495    <date month="January" year="2008"/>
496  </front>
497  <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p6-cache-01"/>
498 
499</reference>
500
501<reference anchor="RFC2119">
502  <front>
503    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
504    <author initials="S." surname="Bradner" fullname="Scott Bradner">
505      <organization>Harvard University</organization>
506      <address><email>sob@harvard.edu</email></address>
507    </author>
508    <date month="March" year="1997"/>
509  </front>
510  <seriesInfo name="BCP" value="14"/>
511  <seriesInfo name="RFC" value="2119"/>
512</reference>
513
514<reference anchor="RFC2617">
515  <front>
516    <title abbrev="HTTP Authentication">HTTP Authentication: Basic and Digest Access Authentication</title>
517    <author initials="J." surname="Franks" fullname="John Franks">
518      <organization>Northwestern University, Department of Mathematics</organization>
519      <address><email>john@math.nwu.edu</email></address>
520    </author>
521    <author initials="P.M." surname="Hallam-Baker" fullname="Phillip M. Hallam-Baker">
522      <organization>Verisign Inc.</organization>
523      <address><email>pbaker@verisign.com</email></address>
524    </author>
525    <author initials="J.L." surname="Hostetler" fullname="Jeffery L. Hostetler">
526      <organization>AbiSource, Inc.</organization>
527      <address><email>jeff@AbiSource.com</email></address>
528    </author>
529    <author initials="S.D." surname="Lawrence" fullname="Scott D. Lawrence">
530      <organization>Agranat Systems, Inc.</organization>
531      <address><email>lawrence@agranat.com</email></address>
532    </author>
533    <author initials="P.J." surname="Leach" fullname="Paul J. Leach">
534      <organization>Microsoft Corporation</organization>
535      <address><email>paulle@microsoft.com</email></address>
536    </author>
537    <author initials="A." surname="Luotonen" fullname="Ari Luotonen">
538      <organization>Netscape Communications Corporation</organization>
539    </author>
540    <author initials="L." surname="Stewart" fullname="Lawrence C. Stewart">
541      <organization>Open Market, Inc.</organization>
542      <address><email>stewart@OpenMarket.com</email></address>
543    </author>
544    <date month="June" year="1999"/>
545  </front>
546  <seriesInfo name="RFC" value="2617"/>
547</reference>
548
549</references>
550
551<references title="Informative References">
552
553<reference anchor="RFC2616">
554  <front>
555    <title>Hypertext Transfer Protocol -- HTTP/1.1</title>
556    <author initials="R." surname="Fielding" fullname="R. Fielding">
557      <organization>University of California, Irvine</organization>
558      <address><email>fielding@ics.uci.edu</email></address>
559    </author>
560    <author initials="J." surname="Gettys" fullname="J. Gettys">
561      <organization>W3C</organization>
562      <address><email>jg@w3.org</email></address>
563    </author>
564    <author initials="J." surname="Mogul" fullname="J. Mogul">
565      <organization>Compaq Computer Corporation</organization>
566      <address><email>mogul@wrl.dec.com</email></address>
567    </author>
568    <author initials="H." surname="Frystyk" fullname="H. Frystyk">
569      <organization>MIT Laboratory for Computer Science</organization>
570      <address><email>frystyk@w3.org</email></address>
571    </author>
572    <author initials="L." surname="Masinter" fullname="L. Masinter">
573      <organization>Xerox Corporation</organization>
574      <address><email>masinter@parc.xerox.com</email></address>
575    </author>
576    <author initials="P." surname="Leach" fullname="P. Leach">
577      <organization>Microsoft Corporation</organization>
578      <address><email>paulle@microsoft.com</email></address>
579    </author>
580    <author initials="T." surname="Berners-Lee" fullname="T. Berners-Lee">
581      <organization>W3C</organization>
582      <address><email>timbl@w3.org</email></address>
583    </author>
584    <date month="June" year="1999"/>
585  </front>
586  <seriesInfo name="RFC" value="2616"/>
587</reference>
588
589</references>
590
591
592<section title="Compatibility with Previous Versions" anchor="compatibility">
593
594<section title="Changes from RFC 2616" anchor="changes.from.rfc.2616">
595</section>
596
597</section>
598
599<section title="Change Log (to be removed by RFC Editor before publication)">
600
601<section title="Since RFC2616">
602<t>
603  Extracted relevant partitions from <xref target="RFC2616"/>.
604</t>
605</section>
606
607<section title="Since draft-ietf-httpbis-p7-auth-00">
608<t>
609  Closed issues:
610  <list style="symbols"> 
611    <t>
612      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/35"/>:
613      "Normative and Informative references"
614    </t>
615  </list>
616</t>
617</section>
618
619</section>
620
621</back>
622</rfc>
Note: See TracBrowser for help on using the repository browser.