* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1533


Ignore:
Timestamp:
2012-02-08 00:19:08 (2 years ago)
Author:
julian.reschke@gmx.de
Message:

Note the ambiguity in the Proxy-A and WWW-A ABNF (see #342)

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p7-auth.html

    r1528 r1533  
    460460  }  
    461461  @bottom-center { 
    462        content: "Expires August 10, 2012";  
     462       content: "Expires August 11, 2012";  
    463463  }  
    464464  @bottom-right { 
     
    506506      <meta name="dct.creator" content="Reschke, J. F."> 
    507507      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest"> 
    508       <meta name="dct.issued" scheme="ISO8601" content="2012-02-07"> 
     508      <meta name="dct.issued" scheme="ISO8601" content="2012-02-08"> 
    509509      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    510510      <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 the HTTP Authentication framework."> 
     
    537537            </tr> 
    538538            <tr> 
    539                <td class="left">Expires: August 10, 2012</td> 
     539               <td class="left">Expires: August 11, 2012</td> 
    540540               <td class="right">HP</td> 
    541541            </tr> 
     
    590590            <tr> 
    591591               <td class="left"></td> 
    592                <td class="right">February 7, 2012</td> 
     592               <td class="right">February 8, 2012</td> 
    593593            </tr> 
    594594         </tbody> 
     
    618618         in progress”. 
    619619      </p> 
    620       <p>This Internet-Draft will expire on August 10, 2012.</p> 
     620      <p>This Internet-Draft will expire on August 11, 2012.</p> 
    621621      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    622622      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    933933         header field. 
    934934      </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&nbsp;4.4</a> for details. 
     936      </p> 
    935937      <div id="rfc.iref.p.3"></div> 
    936938      <div id="rfc.iref.h.3"></div> 
     
    966968         "type" and "title", and another one for the "Basic" scheme with a realm value of "simple". 
    967969      </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> 
    968976      <h1 id="rfc.section.5"><a href="#rfc.section.5">5.</a>&nbsp;<a id="IANA.considerations" href="#IANA.considerations">IANA Considerations</a></h1> 
    969977      <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> 
     
    10411049                  <td class="left">http</td> 
    10421050                  <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&nbsp;4.4</a>  
     1051                  <td class="left"> <a href="#header.www-authenticate" id="rfc.xref.header.www-authenticate.3" title="WWW-Authenticate">Section&nbsp;4.4</a>  
    10441052                  </td> 
    10451053               </tr> 
     
    13181326      </ul> 
    13191327      <h2 id="rfc.section.C.20"><a href="#rfc.section.C.20">C.20</a>&nbsp;<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> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/342">http://tools.ietf.org/wg/httpbis/trac/ticket/342</a>&gt;: "WWW-Authenticate ABNF slightly ambiguous" 
     1331         </li> 
     1332      </ul> 
    13211333      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 
    13221334      <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>  
     
    13661378                        <li>Proxy-Authenticate&nbsp;&nbsp;<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> 
    13671379                        <li>Proxy-Authorization&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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> 
    13691381                     </ul> 
    13701382                  </li> 
     
    14221434            </li> 
    14231435            <li><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul> 
    1424                   <li>WWW-Authenticate header field&nbsp;&nbsp;<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&nbsp;&nbsp;<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> 
    14251437               </ul> 
    14261438            </li> 
  • draft-ietf-httpbis/latest/p7-auth.xml

    r1523 r1533  
    676676   Proxy-Authenticate header field. 
    677677</t> 
     678<t> 
     679   Note that the parsing considerations for WWW-Authenticate apply to this 
     680   header field as well; see <xref target="header.www-authenticate"/> for 
     681   details. 
     682</t> 
    678683</section> 
    679684 
     
    737742  This header field contains two challenges; one for the "Newauth" scheme 
    738743  with a realm value of "apps", and two additional parameters "type" and 
    739   "title", and another one for the "Basic" scheme with a realm value of "simple". 
     744  "title", and another one for the "Basic" scheme with a realm value of 
     745  "simple". 
    740746</postamble></figure> 
     747<x:note> 
     748  <t> 
     749    <x:h>Note:</x:h> The challenge grammar production uses the list syntax as  
     750    well. Therefore, a sequence of comma, whitespace, and comma can be 
     751    considered both as applying to the preceding challenge, or to be an 
     752    empty entry in the list of challenges. In practice, this ambiguity 
     753    does not affect the semantics of the header field value and thus is 
     754    harmless. 
     755  </t> 
     756</x:note> 
    741757</section> 
    742758 
     
    14731489<section title="Since draft-ietf-httpbis-p7-auth-18" anchor="changes.since.18"> 
    14741490<t> 
    1475   None yet. 
     1491  Closed issues: 
     1492  <list style="symbols">  
     1493    <t> 
     1494      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/342"/>: 
     1495      "WWW-Authenticate ABNF slightly ambiguous" 
     1496    </t> 
     1497  </list> 
    14761498</t> 
    14771499</section> 
Note: See TracChangeset for help on using the changeset viewer.