Source: http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1026
Timestamp: 2014-10-01 04:01:16
Document Index: 105899872

Matched Legal Cases: ['art 1', 'art 1', 'art 2', 'art 2', 'art 3', 'art 3', 'art 4', 'art 4', 'art 5', 'art 5', 'art 6', 'art 6', 'art 7', 'art 7', 'art1', 'art1', 'art 1', 'art1']

Changeset 1026 – httpbis
2010-10-07 08:03:59
404404 <meta name="dct.creator" content="Reschke, J. F."> 405405 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-01"> 406 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 407407 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 408408 <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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> …
435435 </tr> 436436 <tr> 437 <td class="left">Expires: April 4, 2011</td> 437 <td class="left">Expires: April 10, 2011</td> 438438 <td class="right">HP</td> 439439 </tr> …
488488 <tr> 489489 <td class="left"></td> 490 <td class="right">October 1, 2010</td> 490 <td class="right">October 7, 2010</td> 491491 </tr> 492492 </tbody> …
516516 in progress”. 517517 </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> 519519 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 520520 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> draft-ietf-httpbis/latest/p2-semantics.html
403403 <meta name="dct.creator" content="Reschke, J. F."> 404404 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 405 <meta name="dct.issued" scheme="ISO8601" content="2010-10-01"> 405 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 406406 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 407407 <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 &#34;HTTP/1.1&#34; 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."> …
434434 </tr> 435435 <tr> 436 <td class="left">Expires: April 4, 2011</td> 436 <td class="left">Expires: April 10, 2011</td> 437437 <td class="right">HP</td> 438438 </tr> …
487487 <tr> 488488 <td class="left"></td> 489 <td class="right">October 1, 2010</td> 489 <td class="right">October 7, 2010</td> 490490 </tr> 491491 </tbody> …
514514 in progress”. 515515 </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> 517517 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 518518 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> draft-ietf-httpbis/latest/p3-payload.html
402402 <meta name="dct.creator" content="Reschke, J. F."> 403403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-01"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 405405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406406 <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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> …
428428 </tr> 429429 <tr> 430 <td class="left">Expires: April 4, 2011</td> 430 <td class="left">Expires: April 10, 2011</td> 431431 <td class="right">J. Mogul</td> 432432 </tr> …
485485 <tr> 486486 <td class="left"></td> 487 <td class="right">October 1, 2010</td> 487 <td class="right">October 7, 2010</td> 488488 </tr> 489489 </tbody> …
511511 in progress”. 512512 </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> 514514 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 515515 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> draft-ietf-httpbis/latest/p4-conditional.html
400400 <meta name="dct.creator" content="Reschke, J. F."> 401401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-10-01"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 403403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404404 <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 &#34;HTTP/1.1&#34; 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."> …
426426 </tr> 427427 <tr> 428 <td class="left">Expires: April 4, 2011</td> 428 <td class="left">Expires: April 10, 2011</td> 429429 <td class="right">J. Mogul</td> 430430 </tr> …
483483 <tr> 484484 <td class="left"></td> 485 <td class="right">October 1, 2010</td> 485 <td class="right">October 7, 2010</td> 486486 </tr> 487487 </tbody> …
509509 in progress”. 510510 </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> 512512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> draft-ietf-httpbis/latest/p5-range.html
400400 <meta name="dct.creator" content="Reschke, J. F."> 401401 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-10-01"> 402 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 403403 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 404404 <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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> …
509509 in progress”. 510510 </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> 512512 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 513513 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> draft-ietf-httpbis/latest/p6-cache.html
402402 <meta name="dct.creator" content="Reschke, J. F."> 403403 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-01"> 404 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 405405 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 406406 <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 &#34;HTTP/1.1&#34; 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."> …
489489 <tr> 490490 <td class="left"></td> 491 <td class="right">October 1, 2010</td> 491 <td class="right">October 7, 2010</td> 492492 </tr> 493493 </tbody> …
515515 in progress”. 516516 </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> 518518 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 519519 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> draft-ietf-httpbis/latest/p7-auth.html
397397 <meta name="dct.creator" content="Reschke, J. F."> 398398 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 399 <meta name="dct.issued" scheme="ISO8601" content="2010-10-01"> 399 <meta name="dct.issued" scheme="ISO8601" content="2010-10-07"> 400400 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 401401 <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 &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 7 defines HTTP Authentication."> …
428428 </tr> 429429 <tr> 430 <td class="left">Expires: April 4, 2011</td> 430 <td class="left">Expires: April 10, 2011</td> 431431 <td class="right">HP</td> 432432 </tr> …
481481 <tr> 482482 <td class="left"></td> 483 <td class="right">October 1, 2010</td> 483 <td class="right">October 7, 2010</td> 484484 </tr> 485485 </tbody> …
507507 in progress”. 508508 </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> 510510 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 511511 <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> …
533533 </ul> 534534 </li> 535 <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#access.authentication.framework">Access Authentication Framework</a></li> 535 <li class="tocline0">2.&nbsp;&nbsp;&nbsp;<a href="#access.authentication.framework">Access Authentication Framework</a><ul class="toc"> 536 <li class="tocline1">2.1&nbsp;&nbsp;&nbsp;<a href="#authentication.scheme.registry">Authentication Scheme Registry</a></li> 537 </ul> 538 </li> 536539 <li class="tocline0">3.&nbsp;&nbsp;&nbsp;<a href="#status.code.definitions">Status Code Definitions</a><ul class="toc"> 537540 <li class="tocline1">3.1&nbsp;&nbsp;&nbsp;<a href="#status.401">401 Unauthorized</a></li> …
547550 </li> 548551 <li class="tocline0">5.&nbsp;&nbsp;&nbsp;<a href="#IANA.considerations">IANA Considerations</a><ul class="toc"> 549 <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li> 550 <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li> 552 <li class="tocline1">5.1&nbsp;&nbsp;&nbsp;<a href="#authentication.scheme.registration">Authenticaton Scheme Registry</a></li> 553 <li class="tocline1">5.2&nbsp;&nbsp;&nbsp;<a href="#status.code.registration">Status Code Registration</a></li> 554 <li class="tocline1">5.3&nbsp;&nbsp;&nbsp;<a href="#header.field.registration">Header Field Registration</a></li> 551555 </ul> 552556 </li> …
668672 <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&nbsp;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>). 669673 </p> 674 <h2 id="rfc.section.2.1"><a href="#rfc.section.2.1">2.1</a>&nbsp;<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 &lt;<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>&gt;. 685 </p> 670686 <h1 id="rfc.section.3"><a href="#rfc.section.3">3.</a>&nbsp;<a id="status.code.definitions" href="#status.code.definitions">Status Code Definitions</a></h1> 671687 <div id="rfc.iref.6"></div> …
751767 </p> 752768 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<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>&nbsp;<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 &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below: 769 <h2 id="rfc.section.5.1"><a href="#rfc.section.5.1">5.1</a>&nbsp;<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&nbsp;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 &lt;<a href="http://www.iana.org/assignments/http-authschemes">http://www.iana.org/assignments/http-authschemes</a>&gt;. 773 </p> 774 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<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 &lt;<a href="http://www.iana.org/assignments/http-status-codes">http://www.iana.org/assignments/http-status-codes</a>&gt; shall be updated with the registrations below: 755776 </p> 756777 <div id="rfc.table.1"> …
780801 </table> 781802 </div> 782 <h2 id="rfc.section.5.2"><a href="#rfc.section.5.2">5.2</a>&nbsp;<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 &lt;<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>&gt; 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>&nbsp;<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 &lt;<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>&gt; 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>): 784805 </p> 785806 <div id="rfc.table.2"> …
826847 </table> 827848 </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> 829850 <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1> 830851 <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 …
885906 <h2 id="rfc.references.2"><a href="#rfc.section.8.2" id="rfc.section.8.2">8.2</a> Informative References 886907 </h2> 887 <table> 908 <table> 888909 <tr> 889910 <td class="reference"><b id="RFC2616">[RFC2616]</b></td> …
899920 <td class="reference"><b id="RFC3864">[RFC3864]</b></td> 900921 <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&nbsp;90, RFC&nbsp;3864, September&nbsp;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&nbsp;26, RFC&nbsp;5226, May&nbsp;2008. 901927 </td> 902928 </tr> …
10261052 </li> 10271053 </ul> 1054 <p id="rfc.section.B.13.p.2">Partly resolved issues: </p> 1055 <ul> 1056 <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/141">http://tools.ietf.org/wg/httpbis/trac/ticket/141</a>&gt;: "should we have an auth scheme registry" 1057 </li> 1058 </ul> 10281059 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 10291060 <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> …
10321063 <ul class="ind"> 10331064 <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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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> 10361067 </ul> 10371068 </li> …
10391070 <li class="indline1"><tt>auth-param</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.2"><b>2</b></a></li> 10401071 <li class="indline1"><tt>auth-scheme</tt>&nbsp;&nbsp;<a class="iref" href="#rfc.iref.a.1"><b>2</b></a></li> 1041 <li class="indline1">Authorization header&nbsp;&nbsp;<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&nbsp;&nbsp;<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> 10421073 </ul> 10431074 </li> …
10651096 <li class="indline1">Headers&nbsp;&nbsp; 10661097 <ul class="ind"> 1067 <li class="indline1">Authorization&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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> 10711102 </ul> 10721103 </li> …
10851116 </ul> 10861117 </li> 1087 <li class="indline1">Proxy-Authenticate header&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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> 10891120 </ul> 10901121 </li> …
10951126 <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<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> 10961127 <li class="indline1"><em>RFC2617</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5226.1">2.1</a></li> 1131 </ul> 1132 </li> 10981133 <li class="indline1"><em>RFC5234</em>&nbsp;&nbsp;<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"> 10991134 <li class="indline1"><em>Appendix B.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC5234.2">1.2</a></li> …
11051140 <li class="indline1">Status Codes&nbsp;&nbsp; 11061141 <ul class="ind"> 1107 <li class="indline1">401 Unauthorized&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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> 11091144 </ul> 11101145 </li> …
11121147 </li> 11131148 <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&nbsp;&nbsp;<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&nbsp;&nbsp;<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> 11151150 </ul> 11161151 </li> draft-ietf-httpbis/latest/p7-auth.xml
406406 &end-to-end.and-hop-by-hop;). 407407</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 408430</section> 409431 …
583605 584606<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> 585617 586618<section title="Status Code Registration" anchor="status.code.registration"> …
937969</reference> 938970 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 939988</references> 940989 …
11301179 </list> 11311180</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> 11321190</section> 11331191 Note: See TracChangeset