Ignore:
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:
3 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r1450 r1451  
    359359  }
    360360  @bottom-center {
    361        content: "Expires April 20, 2012";
     361       content: "Expires April 22, 2012";
    362362  }
    363363  @bottom-right {
     
    408408      <meta name="dct.creator" content="Reschke, J. F.">
    409409      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    410       <meta name="dct.issued" scheme="ISO8601" content="2011-10-18">
     410      <meta name="dct.issued" scheme="ISO8601" content="2011-10-20">
    411411      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    440440            </tr>
    441441            <tr>
    442                <td class="left">Expires: April 20, 2012</td>
     442               <td class="left">Expires: April 22, 2012</td>
    443443               <td class="right">HP</td>
    444444            </tr>
     
    493493            <tr>
    494494               <td class="left"></td>
    495                <td class="right">October 18, 2011</td>
     495               <td class="right">October 20, 2011</td>
    496496            </tr>
    497497         </tbody>
     
    526526         in progress”.
    527527      </p>
    528       <p>This Internet-Draft will expire on April 20, 2012.</p>
     528      <p>This Internet-Draft will expire on April 22, 2012.</p>
    529529      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    530530      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p2-semantics.html

    r1448 r1451  
    359359  }
    360360  @bottom-center {
    361        content: "Expires April 18, 2012";
     361       content: "Expires April 22, 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-10-16">
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-10-20">
    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, 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.">
     
    440440            </tr>
    441441            <tr>
    442                <td class="left">Expires: April 18, 2012</td>
     442               <td class="left">Expires: April 22, 2012</td>
    443443               <td class="right">HP</td>
    444444            </tr>
     
    493493            <tr>
    494494               <td class="left"></td>
    495                <td class="right">October 16, 2011</td>
     495               <td class="right">October 20, 2011</td>
    496496            </tr>
    497497         </tbody>
     
    523523         in progress”.
    524524      </p>
    525       <p>This Internet-Draft will expire on April 18, 2012.</p>
     525      <p>This Internet-Draft will expire on April 22, 2012.</p>
    526526      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    527527      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    867867                     "http://without-a-comma.example.com/"
    868868  Example-Date-Field: "Sat, 04 May 1996", "Wed, 14 Sep 2005"
    869 </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
     869</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
    870870         parser components. Also, the meaning of a value ought to be independent of the syntax variant used for it (for an example,
    871871         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

    r1448 r1451  
    524524</artwork></figure>
    525525<t>
    526    Many header fields use a format including named parameters (for instance,
    527    Content-Type, defined in &header-content-type;). Allowing both unquoted
    528    (token) and quoted (quoted-string) syntax for the parameter value enables
    529    recipients to use existing parser components. Also, the meaning of a value
    530    ought to be independent of the syntax variant used for it (for an example,
    531    see the notes on parameter handling for media types in &media-types;).
     526   Many header fields use a format including (case-insensitively) named
     527   parameters (for instance, Content-Type, defined in &header-content-type;).
     528   Allowing both unquoted (token) and quoted (quoted-string) syntax for the
     529   parameter value enables recipients to use existing parser components. Also,
     530   the meaning of a value ought to be independent of the syntax variant used
     531   for it (for an example, see the notes on parameter handling for media types
     532   in &media-types;).
    532533</t>
    533534<t>
Note: See TracChangeset for help on using the changeset viewer.