Changeset 1451 for draft-ietf-httpbis/latest

Timestamp:

Oct 20, 2011, 1:58:03 AM (8 years ago)

Author:

julian.reschke@…

Message:

param names are case-insensitive (see #231)

Location:

draft-ietf-httpbis/latest

Files:

• p1-messaging.html (modified) (5 diffs)
• p2-semantics.html (modified) (6 diffs)
• p2-semantics.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p1-messaging.html

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires April 20, 2012"; 
+       content: "Expires April 22, 2012"; 
   } 
   @bottom-right {
@@ -408 +408 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2011-10-18">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-10-20">
       <meta name="dct.replaces" content="urn:ietf:rfc:2145">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
@@ -440 +440 @@
             </tr>
             <tr>
-               <td class="left">Expires: April 20, 2012</td>
+               <td class="left">Expires: April 22, 2012</td>
                <td class="right">HP</td>
             </tr>
@@ -493 +493 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 18, 2011</td>
+               <td class="right">October 20, 2011</td>
             </tr>
          </tbody>
@@ -526 +526 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 20, 2012.</p>
+      <p>This Internet-Draft will expire on April 22, 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/p2-semantics.html

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires April 18, 2012"; 
+       content: "Expires April 22, 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-10-16">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-10-20">
       <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, hypertext 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: April 18, 2012</td>
+               <td class="left">Expires: April 22, 2012</td>
                <td class="right">HP</td>
             </tr>
@@ -493 +493 @@
             <tr>
                <td class="left"></td>
-               <td class="right">October 16, 2011</td>
+               <td class="right">October 20, 2011</td>
             </tr>
          </tbody>
@@ -523 +523 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on April 18, 2012.</p>
+      <p>This Internet-Draft will expire on April 22, 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>
@@ -867 +867 @@
                      "http://without-a-comma.example.com/"
   Example-Date-Field: "Sat, 04 May 1996", "Wed, 14 Sep 2005"
-</pre><p id="rfc.section.3.1.p.7">Many header fields use a format including named parameters (for instance, Content-Type, defined in <a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
+</pre><p id="rfc.section.3.1.p.7">Many header fields use a format including (case-insensitively) named parameters (for instance, Content-Type, defined in <a href="p3-payload.html#header.content-type" title="Content-Type">Section 6.8</a> of <a href="#Part3" id="rfc.xref.Part3.1"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>). Allowing both unquoted (token) and quoted (quoted-string) syntax for the parameter value enables recipients to use existing
          parser components. Also, the meaning of a value ought to be independent of the syntax variant used for it (for an example,
          see the notes on parameter handling for media types in <a href="p3-payload.html#media.types" title="Media Types">Section 2.3</a> of <a href="#Part3" id="rfc.xref.Part3.2"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>).

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

@@ -524 +524 @@
 </artwork></figure>
 <t>
-   Many header fields use a format including named parameters (for instance,
-   Content-Type, defined in &header-content-type;). Allowing both unquoted
-   (token) and quoted (quoted-string) syntax for the parameter value enables
-   recipients to use existing parser components. Also, the meaning of a value
-   ought to be independent of the syntax variant used for it (for an example,
-   see the notes on parameter handling for media types in &media-types;).
+   Many header fields use a format including (case-insensitively) named
+   parameters (for instance, Content-Type, defined in &header-content-type;).
+   Allowing both unquoted (token) and quoted (quoted-string) syntax for the
+   parameter value enables recipients to use existing parser components. Also,
+   the meaning of a value ought to be independent of the syntax variant used
+   for it (for an example, see the notes on parameter handling for media types
+   in &media-types;).
 </t>
 <t>