Ignore:
Timestamp:
08/05/14 08:32:21 (6 years ago)
Author:
julian.reschke@…
Message:

consistently say "US-ASCII" (#553)

File:
1 edited

Legend:

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

    r2655 r2656  
    463463  }
    464464  @bottom-center {
    465        content: "Expires November 8, 2014";
     465       content: "Expires November 9, 2014";
    466466  }
    467467  @bottom-right {
     
    507507      <meta name="dct.creator" content="Reschke, J. F.">
    508508      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    509       <meta name="dct.issued" scheme="ISO8601" content="2014-05-07">
     509      <meta name="dct.issued" scheme="ISO8601" content="2014-05-08">
    510510      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    511511      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    535535            <tr>
    536536               <td class="left">Intended status: Standards Track</td>
    537                <td class="right">May 7, 2014</td>
     537               <td class="right">May 8, 2014</td>
    538538            </tr>
    539539            <tr>
    540                <td class="left">Expires: November 8, 2014</td>
     540               <td class="left">Expires: November 9, 2014</td>
    541541               <td class="right"></td>
    542542            </tr>
     
    567567            in progress”.
    568568         </p>
    569          <p>This Internet-Draft will expire on November 8, 2014.</p>
     569         <p>This Internet-Draft will expire on November 9, 2014.</p>
    570570      </div>
    571571      <div id="rfc.copyrightnotice">
     
    13221322            </p>
    13231323            <p id="rfc.section.4.1.p.6">This specification defines a number of standardized methods that are commonly used in HTTP, as outlined by the following table.
    1324                By convention, standardized methods are defined in all-uppercase ASCII letters.
     1324               By convention, standardized methods are defined in all-uppercase US-ASCII letters.
    13251325            </p>
    13261326            <div id="rfc.table.1">
     
    38413841                  processing, since the prefix would ensure that private names never collide with a newly registered Internet name; see <a href="#BCP178" id="rfc.xref.BCP178.1"><cite title="Deprecating the &#34;X-&#34; Prefix and Similar Constructs in Application Protocols">[BCP178]</cite></a> for further information).
    38423842               </p>
    3843                <p id="rfc.section.8.3.1.p.4">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> as necessary, and are usually constrained to the range of ASCII characters. Header fields needing a greater range of characters
     3843               <p id="rfc.section.8.3.1.p.4">New header field values typically have their syntax defined using ABNF (<a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>), using the extension defined in <a href="p1-messaging.html#abnf.extension" title="ABNF List Extension: #rule">Section 7</a> of <a href="#RFC7230" id="rfc.xref.RFC7230.34"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing">[RFC7230]</cite></a> as necessary, and are usually constrained to the range of US-ASCII characters. Header fields needing a greater range of characters
    38443844                  can use an encoding such as the one defined in <a href="#RFC5987" id="rfc.xref.RFC5987.1"><cite title="Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters">[RFC5987]</cite></a>.
    38453845               </p>
Note: See TracChangeset for help on using the changeset viewer.