Changeset 1493 for draft-ietf-httpbis

Timestamp:

Dec 14, 2011, 3:16:37 PM (8 years ago)

Author:

julian.reschke@…

Message:

warn about things that look like quoted-strings but are not (see #329)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (7 diffs)
• p2-semantics.xml (modified) (2 diffs)

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

@@ -359 +359 @@
   } 
   @bottom-center {
-       content: "Expires June 8, 2012"; 
+       content: "Expires June 17, 2012"; 
   } 
   @bottom-right {
@@ -411 +411 @@
       <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-12-06">
+      <meta name="dct.issued" scheme="ISO8601" content="2011-12-15">
       <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.">
@@ -442 +442 @@
             </tr>
             <tr>
-               <td class="left">Expires: June 8, 2012</td>
+               <td class="left">Expires: June 17, 2012</td>
                <td class="right">HP</td>
             </tr>
@@ -495 +495 @@
             <tr>
                <td class="left"></td>
-               <td class="right">December 6, 2011</td>
+               <td class="right">December 15, 2011</td>
             </tr>
          </tbody>
@@ -525 +525 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on June 8, 2012.</p>
+      <p>This Internet-Draft will expire on June 17, 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>
@@ -879 +879 @@
                      "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 (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
+</pre><p id="rfc.section.3.1.p.7">Note that double quote delimiters almost always are used with the quoted-string production; using a different syntax inside
+         double quotes will likely cause unnecessary confusion.
+      </p>
+      <p id="rfc.section.3.1.p.8">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. When allowing both forms, the meaning of a parameter value ought to be independent of the syntax 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>).
       </p>
-      <p id="rfc.section.3.1.p.8">Authors of specifications defining new header fields are advised to consider documenting: </p>
+      <p id="rfc.section.3.1.p.9">Authors of specifications defining new header fields are advised to consider documenting: </p>
       <ul>
          <li>
@@ -3402 +3405 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/312">http://tools.ietf.org/wg/httpbis/trac/ticket/312</a>&gt;: "should there be a permanent variant of 307"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/329">http://tools.ietf.org/wg/httpbis/trac/ticket/329</a>&gt;: "header field considerations: quoted-string vs use of double quotes"
          </li>
       </ul>

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

@@ -544 +544 @@
 </artwork></figure>
 <t>
+   Note that double quote delimiters almost always are used with the
+   quoted-string production; using a different syntax inside double quotes
+   will likely cause unnecessary confusion.
+</t>
+<t>
    Many header fields use a format including (case-insensitively) named
    parameters (for instance, Content-Type, defined in &header-content-type;).
@@ -4702 +4707 @@
       "should there be a permanent variant of 307"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/329"/>:
+      "header field considerations: quoted-string vs use of double quotes"
+    </t>
   </list>
 </t>