Changeset 1026 for draft-ietf-httpbis/latest
- Timestamp:
- 07/10/10 15:03:59 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r1019 r1026 404 404 <meta name="dct.creator" content="Reschke, J. F."> 405 405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-0 1">406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 407 407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408 408 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the "http" and "https" Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> … … 435 435 </tr> 436 436 <tr> 437 <td class="left">Expires: April 4, 2011</td>437 <td class="left">Expires: April 10, 2011</td> 438 438 <td class="right">HP</td> 439 439 </tr> … … 488 488 <tr> 489 489 <td class="left"></td> 490 <td class="right">October 1, 2010</td>490 <td class="right">October 7, 2010</td> 491 491 </tr> 492 492 </tbody> … … 516 516 in progress”. 517 517 </p> 518 <p>This Internet-Draft will expire on April 4, 2011.</p>518 <p>This Internet-Draft will expire on April 10, 2011.</p> 519 519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520 520 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p2-semantics.html
r1019 r1026 403 403 <meta name="dct.creator" content="Reschke, J. F."> 404 404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2010-10-0 1">405 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 406 406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407 407 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> … … 434 434 </tr> 435 435 <tr> 436 <td class="left">Expires: April 4, 2011</td>436 <td class="left">Expires: April 10, 2011</td> 437 437 <td class="right">HP</td> 438 438 </tr> … … 487 487 <tr> 488 488 <td class="left"></td> 489 <td class="right">October 1, 2010</td>489 <td class="right">October 7, 2010</td> 490 490 </tr> 491 491 </tbody> … … 514 514 in progress”. 515 515 </p> 516 <p>This Internet-Draft will expire on April 4, 2011.</p>516 <p>This Internet-Draft will expire on April 10, 2011.</p> 517 517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518 518 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p3-payload.html
r1019 r1026 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-0 1">404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: April 4, 2011</td>430 <td class="left">Expires: April 10, 2011</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 485 485 <tr> 486 486 <td class="left"></td> 487 <td class="right">October 1, 2010</td>487 <td class="right">October 7, 2010</td> 488 488 </tr> 489 489 </tbody> … … 511 511 in progress”. 512 512 </p> 513 <p>This Internet-Draft will expire on April 4, 2011.</p>513 <p>This Internet-Draft will expire on April 10, 2011.</p> 514 514 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 515 515 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p4-conditional.html
r1019 r1026 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-10-0 1">402 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: April 4, 2011</td>428 <td class="left">Expires: April 10, 2011</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">October 1, 2010</td>485 <td class="right">October 7, 2010</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire on April 4, 2011.</p>511 <p>This Internet-Draft will expire on April 10, 2011.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p5-range.html
r1019 r1026 400 400 <meta name="dct.creator" content="Reschke, J. F."> 401 401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-10-0 1">402 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 403 403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404 404 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> … … 426 426 </tr> 427 427 <tr> 428 <td class="left">Expires: April 4, 2011</td>428 <td class="left">Expires: April 10, 2011</td> 429 429 <td class="right">J. Mogul</td> 430 430 </tr> … … 483 483 <tr> 484 484 <td class="left"></td> 485 <td class="right">October 1, 2010</td>485 <td class="right">October 7, 2010</td> 486 486 </tr> 487 487 </tbody> … … 509 509 in progress”. 510 510 </p> 511 <p>This Internet-Draft will expire on April 4, 2011.</p>511 <p>This Internet-Draft will expire on April 10, 2011.</p> 512 512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513 513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p6-cache.html
r1019 r1026 402 402 <meta name="dct.creator" content="Reschke, J. F."> 403 403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-0 1">404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 405 405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406 406 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: April 4, 2011</td>430 <td class="left">Expires: April 10, 2011</td> 431 431 <td class="right">J. Mogul</td> 432 432 </tr> … … 489 489 <tr> 490 490 <td class="left"></td> 491 <td class="right">October 1, 2010</td>491 <td class="right">October 7, 2010</td> 492 492 </tr> 493 493 </tbody> … … 515 515 in progress”. 516 516 </p> 517 <p>This Internet-Draft will expire on April 4, 2011.</p>517 <p>This Internet-Draft will expire on April 10, 2011.</p> 518 518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519 519 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> -
draft-ietf-httpbis/latest/p7-auth.html
r1019 r1026 397 397 <meta name="dct.creator" content="Reschke, J. F."> 398 398 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 399 <meta name="dct.issued" scheme="ISO8601" content="2010-10-0 1">399 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 400 400 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 401 401 <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 7 of the seven-part specification that defines the protocol referred to as "HTTP/1.1" and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication."> … … 428 428 </tr> 429 429 <tr> 430 <td class="left">Expires: April 4, 2011</td>430 <td class="left">Expires: April 10, 2011</td> 431 431 <td class="right">HP</td> 432 432 </tr> … … 481 481 <tr> 482 482 <td class="left"></td> 483 <td class="right">October 1, 2010</td>483 <td class="right">October 7, 2010</td> 484 484 </tr> 485 485 </tbody> … … 507 507 in progress”. 508 508 </p> 509 <p>This Internet-Draft will expire on April 4, 2011.</p>509 <p>This Internet-Draft will expire on April 10, 2011.</p> 510 510 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 511 511 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 533 533 </ul> 534 534 </li> 535 <li class="tocline0">2. <a href="#access.authentication.framework">Access Authentication Framework</a></li> 535 <li class="tocline0">2. <a href="#access.authentication.framework">Access Authentication Framework</a><ul class="toc"> 536 <li class="tocline1">2.1 <a href="#authentication.scheme.registry">Authentication Scheme Registry</a></li> 537 </ul> 538 </li> 536 539 <li class="tocline0">3. <a href="#status.code.definitions">Status Code Definitions</a><ul class="toc"> 537 540 <li class="tocline1">3.1 <a href="#status.401">401 Unauthorized</a></li> … … 547 550 </li> 548 551 <li class="tocline0">5. <a href="#IANA.considerations">IANA Considerations</a><ul class="toc"> 549 <li class="tocline1">5.1 <a href="#status.code.registration">Status Code Registration</a></li> 550 <li class="tocline1">5.2 <a href="#header.field.registration">Header Field Registration</a></li> 552 <li class="tocline1">5.1 <a href="#authentication.scheme.registration">Authenticaton Scheme Registry</a></li> 553 <li class="tocline1">5.2 <a href="#status.code.registration">Status Code Registration</a></li> 554 <li class="tocline1">5.3 <a href="#header.field.registration">Header Field Registration</a></li> 551 555 </ul> 552 556 </li> … … 668 672 <p id="rfc.section.2.p.15">Proxies <em class="bcp14">MUST</em> be completely transparent regarding user agent authentication by origin servers. That is, they <em class="bcp14">MUST</em> forward the WWW-Authenticate and Authorization headers untouched, and follow the rules found in <a href="#header.authorization" id="rfc.xref.header.authorization.1" title="Authorization">Section 4.1</a>. Both the Proxy-Authenticate and the Proxy-Authorization header fields are hop-by-hop headers (see <a href="p1-messaging.html#end-to-end.and.hop-by-hop.header-fields" title="End-to-end and Hop-by-hop Header Fields">Section 7.1.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>). 669 673 </p> 674 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a> <a id="authentication.scheme.registry" href="#authentication.scheme.registry">Authentication Scheme Registry</a></h2> 675 <p id="rfc.section.2.1.p.1">The HTTP Authentication Scheme Registry defines the name space for the authentication schemes in challenges and credentials.</p> 676 <p id="rfc.section.2.1.p.2">Registrations <em class="bcp14">MUST</em> include the following fields: 677 </p> 678 <ul> 679 <li>Authentication Scheme Name</li> 680 <li>Pointer to specification text</li> 681 </ul> 682 <p id="rfc.section.2.1.p.3">Values to be added to this name space are subject to IETF review (<a href="#RFC5226" id="rfc.xref.RFC5226.1"><cite title="Guidelines for Writing an IANA Considerations Section in RFCs">[RFC5226]</cite></a>, <a href="http://tools.ietf.org/html/rfc5226#section-4.1">Section 4.1</a>). 683 </p> 684 <p id="rfc.section.2.1.p.4">The registry itself is maintained at <<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>>. 685 </p> 670 686 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a> <a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1> 671 687 <div id="rfc.iref.6"></div> … … 751 767 </p> 752 768 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 753 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2> 754 <p id="rfc.section.5.1.p.1">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: 769 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a> <a id="authentication.scheme.registration" href="#authentication.scheme.registration">Authenticaton Scheme Registry</a></h2> 770 <p id="rfc.section.5.1.p.1">The registration procedure for HTTP Authentication Schemes is defined by <a href="#authentication.scheme.registry" title="Authentication Scheme Registry">Section 2.1</a> of this document. 771 </p> 772 <p id="rfc.section.5.1.p.2">The HTTP Method Authentication Scheme shall be created at <<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>>. 773 </p> 774 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a> <a id="status.code.registration" href="#status.code.registration">Status Code Registration</a></h2> 775 <p id="rfc.section.5.2.p.1">The HTTP Status Code Registry located at <<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>> shall be updated with the registrations below: 755 776 </p> 756 777 <div id="rfc.table.1"> … … 780 801 </table> 781 802 </div> 782 <h2 id="rfc.section.5. 2"><a href="#rfc.section.5.2">5.2</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2>783 <p id="rfc.section.5. 2.p.1">The Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>):803 <h2 id="rfc.section.5.3"><a href="#rfc.section.5.3">5.3</a> <a id="header.field.registration" href="#header.field.registration">Header Field Registration</a></h2> 804 <p id="rfc.section.5.3.p.1">The Message Header Field Registry located at <<a href="http://www.iana.org/assignments/message-headers/message-header-index.html">http://www.iana.org/assignments/message-headers/message-header-index.html</a>> shall be updated with the permanent registrations below (see <a href="#RFC3864" id="rfc.xref.RFC3864.1"><cite title="Registration Procedures for Message Header Fields">[RFC3864]</cite></a>): 784 805 </p> 785 806 <div id="rfc.table.2"> … … 826 847 </table> 827 848 </div> 828 <p id="rfc.section.5. 2.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>849 <p id="rfc.section.5.3.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p> 829 850 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a> <a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 830 851 <p id="rfc.section.6.p.1">This section is meant to inform application developers, information providers, and users of the security limitations in HTTP/1.1 … … 885 906 <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References 886 907 </h2> 887 <table> 908 <table> 888 909 <tr> 889 910 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> … … 899 920 <td class="reference"><b id="RFC3864">[RFC3864]</b></td> 900 921 <td class="top"><a href="mailto:GK-IETF@ninebynine.org" title="Nine by Nine">Klyne, G.</a>, <a href="mailto:mnot@pobox.com" title="BEA Systems">Nottingham, M.</a>, and <a href="mailto:JeffMogul@acm.org" title="HP Labs">J. Mogul</a>, “<a href="http://tools.ietf.org/html/rfc3864">Registration Procedures for Message Header Fields</a>”, BCP 90, RFC 3864, September 2004. 922 </td> 923 </tr> 924 <tr> 925 <td class="reference"><b id="RFC5226">[RFC5226]</b></td> 926 <td class="top"><a href="mailto:narten@us.ibm.com" title="IBM">Narten, T.</a> and <a href="mailto:Harald@Alvestrand.no" title="Google">H. Alvestrand</a>, “<a href="http://tools.ietf.org/html/rfc5226">Guidelines for Writing an IANA Considerations Section in RFCs</a>”, BCP 26, RFC 5226, May 2008. 901 927 </td> 902 928 </tr> … … 1026 1052 </li> 1027 1053 </ul> 1054 <p id="rfc.section.B.13.p.2">Partly resolved issues: </p> 1055 <ul> 1056 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/141">http://tools.ietf.org/wg/httpbis/trac/ticket/141</a>>: "should we have an auth scheme registry" 1057 </li> 1058 </ul> 1028 1059 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1029 1060 <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.W">W</a> … … 1032 1063 <ul class="ind"> 1033 1064 <li class="indline0"><a id="rfc.index.4" href="#rfc.index.4"><b>4</b></a><ul class="ind"> 1034 <li class="indline1">401 Unauthorized (status code) <a class="iref" href="#rfc.iref.6"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.401.1">5. 1</a></li>1035 <li class="indline1">407 Proxy Authentication Required (status code) <a class="iref" href="#rfc.iref.7"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.407.1">5. 1</a></li>1065 <li class="indline1">401 Unauthorized (status code) <a class="iref" href="#rfc.iref.6"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.401.1">5.2</a></li> 1066 <li class="indline1">407 Proxy Authentication Required (status code) <a class="iref" href="#rfc.iref.7"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.407.1">5.2</a></li> 1036 1067 </ul> 1037 1068 </li> … … 1039 1070 <li class="indline1"><tt>auth-param</tt> <a class="iref" href="#rfc.iref.a.2"><b>2</b></a></li> 1040 1071 <li class="indline1"><tt>auth-scheme</tt> <a class="iref" href="#rfc.iref.a.1"><b>2</b></a></li> 1041 <li class="indline1">Authorization header <a class="iref" href="#rfc.xref.header.authorization.1">2</a>, <a class="iref" href="#rfc.xref.header.authorization.2">3.1</a>, <a class="iref" href="#rfc.iref.a.3"><b>4.1</b></a>, <a class="iref" href="#rfc.xref.header.authorization.3">5. 2</a></li>1072 <li class="indline1">Authorization header <a class="iref" href="#rfc.xref.header.authorization.1">2</a>, <a class="iref" href="#rfc.xref.header.authorization.2">3.1</a>, <a class="iref" href="#rfc.iref.a.3"><b>4.1</b></a>, <a class="iref" href="#rfc.xref.header.authorization.3">5.3</a></li> 1042 1073 </ul> 1043 1074 </li> … … 1065 1096 <li class="indline1">Headers 1066 1097 <ul class="ind"> 1067 <li class="indline1">Authorization <a class="iref" href="#rfc.xref.header.authorization.1">2</a>, <a class="iref" href="#rfc.xref.header.authorization.2">3.1</a>, <a class="iref" href="#rfc.iref.h.1"><b>4.1</b></a>, <a class="iref" href="#rfc.xref.header.authorization.3">5. 2</a></li>1068 <li class="indline1">Proxy-Authenticate <a class="iref" href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>4.2</b></a>, <a class="iref" href="#rfc.xref.header.proxy-authenticate.2">5. 2</a></li>1069 <li class="indline1">Proxy-Authorization <a class="iref" href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>4.3</b></a>, <a class="iref" href="#rfc.xref.header.proxy-authorization.2">5. 2</a></li>1070 <li class="indline1">WWW-Authenticate <a class="iref" href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>4.4</b></a>, <a class="iref" href="#rfc.xref.header.www-authenticate.2">5. 2</a></li>1098 <li class="indline1">Authorization <a class="iref" href="#rfc.xref.header.authorization.1">2</a>, <a class="iref" href="#rfc.xref.header.authorization.2">3.1</a>, <a class="iref" href="#rfc.iref.h.1"><b>4.1</b></a>, <a class="iref" href="#rfc.xref.header.authorization.3">5.3</a></li> 1099 <li class="indline1">Proxy-Authenticate <a class="iref" href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a class="iref" href="#rfc.iref.h.2"><b>4.2</b></a>, <a class="iref" href="#rfc.xref.header.proxy-authenticate.2">5.3</a></li> 1100 <li class="indline1">Proxy-Authorization <a class="iref" href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a class="iref" href="#rfc.iref.h.3"><b>4.3</b></a>, <a class="iref" href="#rfc.xref.header.proxy-authorization.2">5.3</a></li> 1101 <li class="indline1">WWW-Authenticate <a class="iref" href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a class="iref" href="#rfc.iref.h.4"><b>4.4</b></a>, <a class="iref" href="#rfc.xref.header.www-authenticate.2">5.3</a></li> 1071 1102 </ul> 1072 1103 </li> … … 1085 1116 </ul> 1086 1117 </li> 1087 <li class="indline1">Proxy-Authenticate header <a class="iref" href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a class="iref" href="#rfc.iref.p.1"><b>4.2</b></a>, <a class="iref" href="#rfc.xref.header.proxy-authenticate.2">5. 2</a></li>1088 <li class="indline1">Proxy-Authorization header <a class="iref" href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a class="iref" href="#rfc.iref.p.2"><b>4.3</b></a>, <a class="iref" href="#rfc.xref.header.proxy-authorization.2">5. 2</a></li>1118 <li class="indline1">Proxy-Authenticate header <a class="iref" href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a class="iref" href="#rfc.iref.p.1"><b>4.2</b></a>, <a class="iref" href="#rfc.xref.header.proxy-authenticate.2">5.3</a></li> 1119 <li class="indline1">Proxy-Authorization header <a class="iref" href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a class="iref" href="#rfc.iref.p.2"><b>4.3</b></a>, <a class="iref" href="#rfc.xref.header.proxy-authorization.2">5.3</a></li> 1089 1120 </ul> 1090 1121 </li> … … 1095 1126 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#rfc.xref.RFC2616.2">7</a>, <a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.3">B.1</a></li> 1096 1127 <li class="indline1"><em>RFC2617</em> <a class="iref" href="#rfc.xref.RFC2617.1">1</a>, <a class="iref" href="#rfc.xref.RFC2617.2">1</a>, <a class="iref" href="#RFC2617"><b>8.2</b></a></li> 1097 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">5.2</a>, <a class="iref" href="#RFC3864"><b>8.2</b></a></li> 1128 <li class="indline1"><em>RFC3864</em> <a class="iref" href="#rfc.xref.RFC3864.1">5.3</a>, <a class="iref" href="#RFC3864"><b>8.2</b></a></li> 1129 <li class="indline1"><em>RFC5226</em> <a class="iref" href="#rfc.xref.RFC5226.1">2.1</a>, <a class="iref" href="#RFC5226"><b>8.2</b></a><ul class="ind"> 1130 <li class="indline1"><em>Section 4.1</em> <a class="iref" href="#rfc.xref.RFC5226.1">2.1</a></li> 1131 </ul> 1132 </li> 1098 1133 <li class="indline1"><em>RFC5234</em> <a class="iref" href="#rfc.xref.RFC5234.1">1.2</a>, <a class="iref" href="#rfc.xref.RFC5234.2">1.2</a>, <a class="iref" href="#RFC5234"><b>8.1</b></a><ul class="ind"> 1099 1134 <li class="indline1"><em>Appendix B.1</em> <a class="iref" href="#rfc.xref.RFC5234.2">1.2</a></li> … … 1105 1140 <li class="indline1">Status Codes 1106 1141 <ul class="ind"> 1107 <li class="indline1">401 Unauthorized <a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.401.1">5. 1</a></li>1108 <li class="indline1">407 Proxy Authentication Required <a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.407.1">5. 1</a></li>1142 <li class="indline1">401 Unauthorized <a class="iref" href="#rfc.iref.s.1"><b>3.1</b></a>, <a class="iref" href="#rfc.xref.status.401.1">5.2</a></li> 1143 <li class="indline1">407 Proxy Authentication Required <a class="iref" href="#rfc.iref.s.2"><b>3.2</b></a>, <a class="iref" href="#rfc.xref.status.407.1">5.2</a></li> 1109 1144 </ul> 1110 1145 </li> … … 1112 1147 </li> 1113 1148 <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind"> 1114 <li class="indline1">WWW-Authenticate header <a class="iref" href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a class="iref" href="#rfc.iref.w.1"><b>4.4</b></a>, <a class="iref" href="#rfc.xref.header.www-authenticate.2">5. 2</a></li>1149 <li class="indline1">WWW-Authenticate header <a class="iref" href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a class="iref" href="#rfc.iref.w.1"><b>4.4</b></a>, <a class="iref" href="#rfc.xref.header.www-authenticate.2">5.3</a></li> 1115 1150 </ul> 1116 1151 </li> -
draft-ietf-httpbis/latest/p7-auth.xml
r1019 r1026 406 406 &end-to-end.and-hop-by-hop;). 407 407 </t> 408 409 <section title="Authentication Scheme Registry" anchor="authentication.scheme.registry"> 410 <t> 411 The HTTP Authentication Scheme Registry defines the name space for the 412 authentication schemes in challenges and credentials. 413 </t> 414 <t> 415 Registrations &MUST; include the following fields: 416 <list style="symbols"> 417 <t>Authentication Scheme Name</t> 418 <t>Pointer to specification text</t> 419 </list> 420 </t> 421 <t> 422 Values to be added to this name space are subject to IETF review 423 (<xref target="RFC5226" x:fmt="," x:sec="4.1"/>). 424 </t> 425 <t> 426 The registry itself is maintained at <eref target="http://www.iana.org/assignments/http-authschemes"/>. 427 </t> 428 </section> 429 408 430 </section> 409 431 … … 583 605 584 606 <section title="IANA Considerations" anchor="IANA.considerations"> 607 608 <section title="Authenticaton Scheme Registry" anchor="authentication.scheme.registration"> 609 <t> 610 The registration procedure for HTTP Authentication Schemes is defined by 611 <xref target="authentication.scheme.registry"/> of this document. 612 </t> 613 <t> 614 The HTTP Method Authentication Scheme shall be created at <eref target="http://www.iana.org/assignments/http-authschemes"/>. 615 </t> 616 </section> 585 617 586 618 <section title="Status Code Registration" anchor="status.code.registration"> … … 937 969 </reference> 938 970 971 <reference anchor='RFC5226'> 972 <front> 973 <title>Guidelines for Writing an IANA Considerations Section in RFCs</title> 974 <author initials='T.' surname='Narten' fullname='T. Narten'> 975 <organization>IBM</organization> 976 <address><email>narten@us.ibm.com</email></address> 977 </author> 978 <author initials='H.' surname='Alvestrand' fullname='H. Alvestrand'> 979 <organization>Google</organization> 980 <address><email>Harald@Alvestrand.no</email></address> 981 </author> 982 <date year='2008' month='May' /> 983 </front> 984 <seriesInfo name='BCP' value='26' /> 985 <seriesInfo name='RFC' value='5226' /> 986 </reference> 987 939 988 </references> 940 989 … … 1130 1179 </list> 1131 1180 </t> 1181 <t> 1182 Partly resolved issues: 1183 <list style="symbols"> 1184 <t> 1185 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/141"/>: 1186 "should we have an auth scheme registry" 1187 </t> 1188 </list> 1189 </t> 1132 1190 </section> 1133 1191
Note: See TracChangeset
for help on using the changeset viewer.