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

Changeset 1493


Ignore:
Timestamp:
2011-12-14 15:16:37 (3 years ago)
Author:
julian.reschke@gmx.de
Message:

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

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

Legend:

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

    r1489 r1493  
    359359  }  
    360360  @bottom-center { 
    361        content: "Expires June 8, 2012";  
     361       content: "Expires June 17, 2012";  
    362362  }  
    363363  @bottom-right { 
     
    411411      <meta name="dct.creator" content="Reschke, J. F."> 
    412412      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 
    413       <meta name="dct.issued" scheme="ISO8601" content="2011-12-06"> 
     413      <meta name="dct.issued" scheme="ISO8601" content="2011-12-15"> 
    414414      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    415415      <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."> 
     
    442442            </tr> 
    443443            <tr> 
    444                <td class="left">Expires: June 8, 2012</td> 
     444               <td class="left">Expires: June 17, 2012</td> 
    445445               <td class="right">HP</td> 
    446446            </tr> 
     
    495495            <tr> 
    496496               <td class="left"></td> 
    497                <td class="right">December 6, 2011</td> 
     497               <td class="right">December 15, 2011</td> 
    498498            </tr> 
    499499         </tbody> 
     
    525525         in progress”. 
    526526      </p> 
    527       <p>This Internet-Draft will expire on June 8, 2012.</p> 
     527      <p>This Internet-Draft will expire on June 17, 2012.</p> 
    528528      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    529529      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    879879                     "http://without-a-comma.example.com/" 
    880880  Example-Date-Field: "Sat, 04 May 1996", "Wed, 14 Sep 2005" 
    881 </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 
     881</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 
     882         double quotes will likely cause unnecessary confusion. 
     883      </p> 
     884      <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 
    882885         parser components. When allowing both forms, the meaning of a parameter value ought to be independent of the syntax used for 
    883886         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>). 
    884887      </p> 
    885       <p id="rfc.section.3.1.p.8">Authors of specifications defining new header fields are advised to consider documenting: </p> 
     888      <p id="rfc.section.3.1.p.9">Authors of specifications defining new header fields are advised to consider documenting: </p> 
    886889      <ul> 
    887890         <li> 
     
    34023405         </li> 
    34033406         <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" 
     3407         </li> 
     3408         <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" 
    34043409         </li> 
    34053410      </ul> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1489 r1493  
    544544</artwork></figure> 
    545545<t> 
     546   Note that double quote delimiters almost always are used with the 
     547   quoted-string production; using a different syntax inside double quotes 
     548   will likely cause unnecessary confusion. 
     549</t> 
     550<t> 
    546551   Many header fields use a format including (case-insensitively) named 
    547552   parameters (for instance, Content-Type, defined in &header-content-type;). 
     
    47024707      "should there be a permanent variant of 307" 
    47034708    </t> 
     4709    <t> 
     4710      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/329"/>: 
     4711      "header field considerations: quoted-string vs use of double quotes" 
     4712    </t> 
    47044713  </list> 
    47054714</t> 
Note: See TracChangeset for help on using the changeset viewer.