Changeset 1533 for draft-ietf-httpbis/latest/p7-auth.html
- Timestamp:
- 08/02/12 08:19:08 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p7-auth.html
r1528 r1533 460 460 } 461 461 @bottom-center { 462 content: "Expires August 1 0, 2012";462 content: "Expires August 11, 2012"; 463 463 } 464 464 @bottom-right { … … 506 506 <meta name="dct.creator" content="Reschke, J. F."> 507 507 <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 508 <meta name="dct.issued" scheme="ISO8601" content="2012-02-0 7">508 <meta name="dct.issued" scheme="ISO8601" content="2012-02-08"> 509 509 <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 510 510 <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 the HTTP Authentication framework."> … … 537 537 </tr> 538 538 <tr> 539 <td class="left">Expires: August 1 0, 2012</td>539 <td class="left">Expires: August 11, 2012</td> 540 540 <td class="right">HP</td> 541 541 </tr> … … 590 590 <tr> 591 591 <td class="left"></td> 592 <td class="right">February 7, 2012</td>592 <td class="right">February 8, 2012</td> 593 593 </tr> 594 594 </tbody> … … 618 618 in progress”. 619 619 </p> 620 <p>This Internet-Draft will expire on August 1 0, 2012.</p>620 <p>This Internet-Draft will expire on August 11, 2012.</p> 621 621 <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 622 622 <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> … … 933 933 header field. 934 934 </p> 935 <p id="rfc.section.4.2.p.4">Note that the parsing considerations for WWW-Authenticate apply to this header field as well; see <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.2" title="WWW-Authenticate">Section 4.4</a> for details. 936 </p> 935 937 <div id="rfc.iref.p.3"></div> 936 938 <div id="rfc.iref.h.3"></div> … … 966 968 "type" and "title", and another one for the "Basic" scheme with a realm value of "simple". 967 969 </p> 970 <div class="note" id="rfc.section.4.4.p.6"> 971 <p> <b>Note:</b> The challenge grammar production uses the list syntax as well. Therefore, a sequence of comma, whitespace, and comma can be 972 considered both as applying to the preceding challenge, or to be an empty entry in the list of challenges. In practice, this 973 ambiguity does not affect the semantics of the header field value and thus is harmless. 974 </p> 975 </div> 968 976 <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a> <a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 969 977 <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> … … 1041 1049 <td class="left">http</td> 1042 1050 <td class="left">standard</td> 1043 <td class="left"> <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate. 2" title="WWW-Authenticate">Section 4.4</a>1051 <td class="left"> <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.3" title="WWW-Authenticate">Section 4.4</a> 1044 1052 </td> 1045 1053 </tr> … … 1318 1326 </ul> 1319 1327 <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a> <a id="changes.since.18" href="#changes.since.18">Since draft-ietf-httpbis-p7-auth-18</a></h2> 1320 <p id="rfc.section.C.20.p.1">None yet.</p> 1328 <p id="rfc.section.C.20.p.1">Closed issues: </p> 1329 <ul> 1330 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/342">http://tools.ietf.org/wg/httpbis/trac/ticket/342</a>>: "WWW-Authenticate ABNF slightly ambiguous" 1331 </li> 1332 </ul> 1321 1333 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1322 1334 <p class="noprint"><a href="#rfc.index.4">4</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</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> … … 1366 1378 <li>Proxy-Authenticate <a href="#rfc.xref.header.proxy-authenticate.1">3.2</a>, <a href="#rfc.iref.h.2"><b>4.2</b></a>, <a href="#rfc.xref.header.proxy-authenticate.2">5.3</a></li> 1367 1379 <li>Proxy-Authorization <a href="#rfc.xref.header.proxy-authorization.1">3.2</a>, <a href="#rfc.iref.h.3"><b>4.3</b></a>, <a href="#rfc.xref.header.proxy-authorization.2">5.3</a></li> 1368 <li>WWW-Authenticate <a href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a href="#rfc. iref.h.4"><b>4.4</b></a>, <a href="#rfc.xref.header.www-authenticate.2">5.3</a></li>1380 <li>WWW-Authenticate <a href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a href="#rfc.xref.header.www-authenticate.2">4.2</a>, <a href="#rfc.iref.h.4"><b>4.4</b></a>, <a href="#rfc.xref.header.www-authenticate.3">5.3</a></li> 1369 1381 </ul> 1370 1382 </li> … … 1422 1434 </li> 1423 1435 <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul> 1424 <li>WWW-Authenticate header field <a href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a href="#rfc. iref.w.1"><b>4.4</b></a>, <a href="#rfc.xref.header.www-authenticate.2">5.3</a></li>1436 <li>WWW-Authenticate header field <a href="#rfc.xref.header.www-authenticate.1">3.1</a>, <a href="#rfc.xref.header.www-authenticate.2">4.2</a>, <a href="#rfc.iref.w.1"><b>4.4</b></a>, <a href="#rfc.xref.header.www-authenticate.3">5.3</a></li> 1425 1437 </ul> 1426 1438 </li>
Note: See TracChangeset
for help on using the changeset viewer.