Ignore:
Timestamp:
Jul 24, 2011, 11:27:10 AM (8 years ago)
Author:
julian.reschke@…
Message:

clarify not about parsing *-Authenticate header fields

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1342 r1343  
    359359  }
    360360  @bottom-center {
    361        content: "Expires January 24, 2012";
     361       content: "Expires January 25, 2012";
    362362  }
    363363  @bottom-right {
     
    409409      <meta name="dct.creator" content="Reschke, J. F.">
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-07-23">
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-07-24">
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    413413      <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.">
     
    440440            </tr>
    441441            <tr>
    442                <td class="left">Expires: January 24, 2012</td>
     442               <td class="left">Expires: January 25, 2012</td>
    443443               <td class="right">HP</td>
    444444            </tr>
     
    493493            <tr>
    494494               <td class="left"></td>
    495                <td class="right">July 23, 2011</td>
     495               <td class="right">July 24, 2011</td>
    496496            </tr>
    497497         </tbody>
     
    522522         in progress”.
    523523      </p>
    524       <p>This Internet-Draft will expire on January 24, 2012.</p>
     524      <p>This Internet-Draft will expire on January 25, 2012.</p>
    525525      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    526526      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p7-auth.html

    r1333 r1343  
    359359  }
    360360  @bottom-center {
    361        content: "Expires January 19, 2012";
     361       content: "Expires January 25, 2012";
    362362  }
    363363  @bottom-right {
     
    404404      <meta name="dct.creator" content="Reschke, J. F.">
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    406       <meta name="dct.issued" scheme="ISO8601" content="2011-07-18">
     406      <meta name="dct.issued" scheme="ISO8601" content="2011-07-24">
    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, 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.">
     
    435435            </tr>
    436436            <tr>
    437                <td class="left">Expires: January 19, 2012</td>
     437               <td class="left">Expires: January 25, 2012</td>
    438438               <td class="right">HP</td>
    439439            </tr>
     
    488488            <tr>
    489489               <td class="left"></td>
    490                <td class="right">July 18, 2011</td>
     490               <td class="right">July 24, 2011</td>
    491491            </tr>
    492492         </tbody>
     
    516516         in progress”.
    517517      </p>
    518       <p>This Internet-Draft will expire on January 19, 2012.</p>
     518      <p>This Internet-Draft will expire on January 25, 2012.</p>
    519519      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    520520      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    641641      <div id="rfc.figure.u.3"></div><pre class="inline"><span id="rfc.iref.c.1"></span>  <a href="#access.authentication.framework" class="smpl">challenge</a>   = <a href="#access.authentication.framework" class="smpl">auth-scheme</a> 1*<a href="#notation" class="smpl">SP</a> 1#<a href="#access.authentication.framework" class="smpl">auth-param</a>
    642642</pre><div class="note" id="rfc.section.2.p.5">
    643          <p> <b>Note:</b> User agents will need to take special care in parsing the WWW-Authenticate or Proxy-Authenticate header field value if it
    644             contains more than one challenge, or if more than one WWW-Authenticate header field is provided, since the contents of a challenge
    645             can itself contain a comma-separated list of authentication parameters.
     643         <p> <b>Note:</b> User agents will need to take special care in parsing the WWW-Authenticate and Proxy-Authenticate header field values because
     644            they can contain more than one challenge, or if more than one of each is provided, since the contents of a challenge can itself
     645            contain a comma-separated list of authentication parameters.
    646646         </p>
    647647      </div>
  • draft-ietf-httpbis/latest/p7-auth.xml

    r1328 r1343  
    317317<x:note>
    318318  <t>
    319    <x:h>Note:</x:h> User agents will need to take special care in parsing the WWW-Authenticate
    320    or Proxy-Authenticate header field value if it contains
    321    more than one challenge, or if more than one WWW-Authenticate header
    322    field is provided, since the contents of a challenge can itself
    323    contain a comma-separated list of authentication parameters.
     319     <x:h>Note:</x:h> User agents will need to take special care in parsing the
     320     WWW-Authenticate and Proxy-Authenticate header field values because they
     321     can contain more than one challenge, or if more than one of each is
     322     provided, since the contents of a challenge can itself contain a
     323     comma-separated list of authentication parameters.
    324324  </t>
    325325</x:note>
    326326<x:note>
    327327  <t>
    328       <x:h>Note:</x:h> Many browsers fail to parse challenges containing unknown
    329       schemes. A workaround for this problem is to list well-supported schemes
    330       (such as "basic") first.
     328     <x:h>Note:</x:h> Many browsers fail to parse challenges containing unknown
     329     schemes. A workaround for this problem is to list well-supported schemes
     330     (such as "basic") first.
    331331  </t>
    332332</x:note>
Note: See TracChangeset for help on using the changeset viewer.