Ignore:
Timestamp:
Nov 15, 2008, 11:52:39 AM (11 years ago)
Author:
julian.reschke@…
Message:

s/white space/whitespace/g

File:
1 edited

Legend:

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

    r400 r401  
    710710      <div id="core.rules">
    711711         <p id="rfc.section.1.2.p.1">                        This specification uses the Augmented Backus-Naur Form (ABNF) notation of <a href="#RFC5234" id="rfc.xref.RFC5234.1"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>. The following core rules are included by reference, as defined in <a href="#RFC5234" id="rfc.xref.RFC5234.2"><cite title="Augmented BNF for Syntax Specifications: ABNF">[RFC5234]</cite></a>, <a href="http://tools.ietf.org/html/rfc5234#section-B.1">Appendix B.1</a>: ALPHA (letters), CR (carriage return), CRLF (CR LF), CTL (controls), DIGIT (decimal 0-9), DQUOTE (double quote), HEXDIG
    712             (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a> character), and WSP (white space).
     712            (hexadecimal 0-9/A-F/a-f), LF (line feed), OCTET (any 8-bit sequence of data), SP (space), VCHAR (any visible <a href="#USASCII" id="rfc.xref.USASCII.1"><cite title="Coded Character Set -- 7-bit American Standard Code for Information Interchange">[USASCII]</cite></a> character), and WSP (whitespace).
    713713         </p>
    714714      </div>
     
    744744         </p>
    745745      </div>
    746       <p id="rfc.section.1.2.2.p.3">The OWS rule is used where zero or more linear white space characters may appear. OWS <em class="bcp14">SHOULD</em> either not be produced or be produced as a single SP character. Multiple OWS characters that occur within field-content <em class="bcp14">SHOULD</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream.
    747       </p>
    748       <p id="rfc.section.1.2.2.p.4">RWS is used when at least one linear white space character is required to separate field tokens. RWS <em class="bcp14">SHOULD</em> be produced as a single SP character. Multiple RWS characters that occur within field-content <em class="bcp14">SHOULD</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream.
     746      <p id="rfc.section.1.2.2.p.3">The OWS rule is used where zero or more linear whitespace characters may appear. OWS <em class="bcp14">SHOULD</em> either not be produced or be produced as a single SP character. Multiple OWS characters that occur within field-content <em class="bcp14">SHOULD</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream.
     747      </p>
     748      <p id="rfc.section.1.2.2.p.4">RWS is used when at least one linear whitespace character is required to separate field tokens. RWS <em class="bcp14">SHOULD</em> be produced as a single SP character. Multiple RWS characters that occur within field-content <em class="bcp14">SHOULD</em> be replaced with a single SP before interpreting the field value or forwarding the message downstream.
    749749      </p>
    750750      <p id="rfc.section.1.2.2.p.5">BWS is used where the grammar allows optional whitespace for historical reasons but senders <em class="bcp14">SHOULD NOT</em> produce it in messages. HTTP/1.1 recipients <em class="bcp14">MUST</em> accept such bad optional whitespace and remove it before interpreting the field value or forwarding the message downstream.
     
    754754      </div>
    755755      <div id="rfc.figure.u.5"></div><pre class="inline"><span id="rfc.iref.g.13"></span><span id="rfc.iref.g.14"></span><span id="rfc.iref.g.15"></span>  <a href="#rule.whitespace" class="smpl">OWS</a>            = *( [ obs-fold ] <a href="#core.rules" class="smpl">WSP</a> )
    756                  ; "optional" white space
     756                 ; "optional" whitespace
    757757  <a href="#rule.whitespace" class="smpl">RWS</a>            = 1*( [ obs-fold ] <a href="#core.rules" class="smpl">WSP</a> )
    758                  ; "required" white space
     758                 ; "required" whitespace
    759759  <a href="#rule.whitespace" class="smpl">BWS</a>            = <a href="#rule.whitespace" class="smpl">OWS</a>
    760                  ; "bad" white space
     760                 ; "bad" whitespace
    761761  <a href="#rule.whitespace" class="smpl">obs-fold</a>       = <a href="#core.rules" class="smpl">CRLF</a>
    762762</pre><div id="rule.token.separators">
     
    11191119      <h2 id="rfc.section.3.4"><a href="#rfc.section.3.4">3.4</a>&nbsp;<a id="product.tokens" href="#product.tokens">Product Tokens</a></h2>
    11201120      <p id="rfc.section.3.4.p.1">Product tokens are used to allow communicating applications to identify themselves by software name and version. Most fields
    1121          using product tokens also allow sub-products which form a significant part of the application to be listed, separated by white
    1122          space. By convention, the products are listed in order of their significance for identifying the application.
     1121         using product tokens also allow sub-products which form a significant part of the application to be listed, separated by whitespace.
     1122         By convention, the products are listed in order of their significance for identifying the application.
    11231123      </p>
    11241124      <div id="rfc.figure.u.25"></div><pre class="inline"><span id="rfc.iref.g.59"></span><span id="rfc.iref.g.60"></span>  <a href="#product.tokens" class="smpl">product</a>         = <a href="#rule.token.separators" class="smpl">token</a> ["/" <a href="#product.tokens" class="smpl">product-version</a>]
     
    11651165         such whitespace <em class="bcp14">MUST</em> be rejected with a response code of 400 (Bad Request) and any such whitespace in a response message <em class="bcp14">MUST</em> be removed.
    11661166      </p>
    1167       <p id="rfc.section.4.2.p.5">The field value <em class="bcp14">MAY</em> be preceded by optional white space; a single SP is preferred. The field-value does not include any leading or trailing white
     1167      <p id="rfc.section.4.2.p.5">The field value <em class="bcp14">MAY</em> be preceded by optional whitespace; a single SP is preferred. The field-value does not include any leading or trailing white
    11681168         space: OWS occurring before the first non-whitespace character of the field-value or after the last non-whitespace character
    11691169         of the field-value is ignored and <em class="bcp14">MAY</em> be removed without changing the meaning of the header field.
     
    24592459      <p id="rfc.section.B.4.p.1">Empty list elements in list productions have been deprecated. (<a href="#notation.abnf" title="ABNF Extension: #rule">Section&nbsp;1.2.1</a>)
    24602460      </p>
    2461       <p id="rfc.section.B.4.p.2">Rules about implicit linear white space between certain grammar productions have been removed; now it's only allowed when
    2462          specifically pointed out in the ABNF. The NUL character is no longer allowed in comment and quoted-string text. The quoted-pair
    2463          rule no longer allows escaping NUL, CR or LF. Non-ASCII content in header fields and reason phrase has been obsoleted and
    2464          made opaque (the TEXT rule was removed) (<a href="#basic.rules" title="Basic Rules">Section&nbsp;1.2.2</a>)
     2461      <p id="rfc.section.B.4.p.2">Rules about implicit linear whitespace between certain grammar productions have been removed; now it's only allowed when specifically
     2462         pointed out in the ABNF. The NUL character is no longer allowed in comment and quoted-string text. The quoted-pair rule no
     2463         longer allows escaping NUL, CR or LF. Non-ASCII content in header fields and reason phrase has been obsoleted and made opaque
     2464         (the TEXT rule was removed) (<a href="#basic.rules" title="Basic Rules">Section&nbsp;1.2.2</a>)
    24652465      </p>
    24662466      <p id="rfc.section.B.4.p.3">Clarify that HTTP-Version is case sensitive. (<a href="#http.version" title="HTTP Version">Section&nbsp;3.1</a>)
Note: See TracChangeset for help on using the changeset viewer.