Changeset 1343 for draft-ietf-httpbis

Timestamp:

24/07/11 18:27:10 (11 years ago)

Author:

julian.reschke@…

Message:

clarify not about parsing *-Authenticate header fields

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (5 diffs)
• p7-auth.html (modified) (6 diffs)
• p7-auth.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires January 24, 2012"; 
+       content: "Expires January 25, 2012"; 
   } 
   @bottom-right {
@@ -409 +409 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-07-23">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-07-24">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -440 +440 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 24, 2012</td>
+               <td class="left">Expires: January 25, 2012</td>
                <td class="right">HP</td>
             </tr>
@@ -493 +493 @@
             <tr>
                <td class="left"></td>
-               <td class="right">July 23, 2011</td>
+               <td class="right">July 24, 2011</td>
             </tr>
          </tbody>
@@ -522 +522 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 24, 2012.</p>
+      <p>This Internet-Draft will expire on January 25, 2012.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>

draft-ietf-httpbis/latest/p7-auth.html

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires January 19, 2012"; 
+       content: "Expires January 25, 2012"; 
   } 
   @bottom-right {
@@ -404 +404 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-07-18">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-07-24">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -435 +435 @@
             </tr>
             <tr>
-               <td class="left">Expires: January 19, 2012</td>
+               <td class="left">Expires: January 25, 2012</td>
                <td class="right">HP</td>
             </tr>
@@ -488 +488 @@
             <tr>
                <td class="left"></td>
-               <td class="right">July 18, 2011</td>
+               <td class="right">July 24, 2011</td>
             </tr>
          </tbody>
@@ -516 +516 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on January 19, 2012.</p>
+      <p>This Internet-Draft will expire on January 25, 2012.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -641 +641 @@
       <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>
 </pre><div class="note" id="rfc.section.2.p.5"> 
-         <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
-            contains more than one challenge, or if more than one WWW-Authenticate header field is provided, since the contents of a challenge
-            can itself contain a comma-separated list of authentication parameters.
+         <p> <b>Note:</b> User agents will need to take special care in parsing the WWW-Authenticate and Proxy-Authenticate header field values because
+            they can contain more than one challenge, or if more than one of each is provided, since the contents of a challenge can itself
+            contain a comma-separated list of authentication parameters.
          </p> 
       </div>

draft-ietf-httpbis/latest/p7-auth.xml

@@ -317 +317 @@
 <x:note>
   <t>
-   <x:h>Note:</x:h> User agents will need to take special care in parsing the WWW-Authenticate
-   or Proxy-Authenticate header field value if it contains
-   more than one challenge, or if more than one WWW-Authenticate header
-   field is provided, since the contents of a challenge can itself
-   contain a comma-separated list of authentication parameters.
+     <x:h>Note:</x:h> User agents will need to take special care in parsing the
+     WWW-Authenticate and Proxy-Authenticate header field values because they
+     can contain more than one challenge, or if more than one of each is
+     provided, since the contents of a challenge can itself contain a
+     comma-separated list of authentication parameters.
   </t>
 </x:note>
 <x:note>
   <t>
-      <x:h>Note:</x:h> Many browsers fail to parse challenges containing unknown
-      schemes. A workaround for this problem is to list well-supported schemes
-      (such as "basic") first.
+     <x:h>Note:</x:h> Many browsers fail to parse challenges containing unknown
+     schemes. A workaround for this problem is to list well-supported schemes
+     (such as "basic") first.
   </t>
 </x:note>