Changeset 401


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

s/white space/whitespace/g

Location:
draft-ietf-httpbis/latest
Files:
4 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>)
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r400 r401  
    336336   OCTET (any 8-bit sequence of data), SP (space),
    337337   VCHAR (any visible <xref target="USASCII"/> character),
    338    and WSP (white space).
     338   and WSP (whitespace).
    339339</t>
    340340
     
    397397</t>
    398398<t>
    399    The OWS rule is used where zero or more linear white space characters may
     399   The OWS rule is used where zero or more linear whitespace characters may
    400400   appear. OWS &SHOULD; either not be produced or be produced as a single SP
    401401   character. Multiple OWS characters that occur within field-content &SHOULD;
     
    404404</t>
    405405<t>
    406    RWS is used when at least one linear white space character is required to
     406   RWS is used when at least one linear whitespace character is required to
    407407   separate field tokens. RWS &SHOULD; be produced as a single SP character.
    408408   Multiple RWS characters that occur within field-content &SHOULD; be
     
    424424<figure><artwork type="abnf2616"><iref primary="true" item="Grammar" subitem="OWS"/><iref primary="true" item="Grammar" subitem="RWS"/><iref primary="true" item="Grammar" subitem="BWS"/>
    425425  <x:ref>OWS</x:ref>            = *( [ obs-fold ] <x:ref>WSP</x:ref> )
    426                  ; "optional" white space
     426                 ; "optional" whitespace
    427427  <x:ref>RWS</x:ref>            = 1*( [ obs-fold ] <x:ref>WSP</x:ref> )
    428                  ; "required" white space
     428                 ; "required" whitespace
    429429  <x:ref>BWS</x:ref>            = <x:ref>OWS</x:ref>
    430                  ; "bad" white space
     430                 ; "bad" whitespace
    431431  <x:ref>obs-fold</x:ref>       = <x:ref>CRLF</x:ref>
    432432</artwork></figure>
     
    11201120   identify themselves by software name and version. Most fields using
    11211121   product tokens also allow sub-products which form a significant part
    1122    of the application to be listed, separated by white space. By
     1122   of the application to be listed, separated by whitespace. By
    11231123   convention, the products are listed in order of their significance
    11241124   for identifying the application.
     
    12311231</t>
    12321232<t>
    1233    The field value &MAY; be preceded by optional white space; a single SP is
     1233   The field value &MAY; be preceded by optional whitespace; a single SP is
    12341234   preferred. The field-value does not include any leading or trailing white
    12351235   space: OWS occurring before the first non-whitespace character of the
     
    40924092</t>
    40934093<t>
    4094   Rules about implicit linear white space between certain grammar productions
     4094  Rules about implicit linear whitespace between certain grammar productions
    40954095  have been removed; now it's only allowed when specifically pointed out
    40964096  in the ABNF. The NUL character is no longer allowed in comment and quoted-string
  • draft-ietf-httpbis/latest/p6-cache.html

    r399 r401  
    11271127      </p>
    11281128      <p id="rfc.section.8.p.4">The selecting request-headers from two requests are defined to match if and only if the selecting request-headers in the first
    1129          request can be transformed to the selecting request-headers in the second request by adding or removing linear white space
     1129         request can be transformed to the selecting request-headers in the second request by adding or removing linear whitespace
    11301130         (LWS) at places where this is allowed by the corresponding BNF, and/or combining multiple message-header fields with the same
    11311131         field name following the rules about message headers in <a href="p1-messaging.html#message.headers" title="Message Headers">Section 4.2</a> of <a href="#Part1" id="rfc.xref.Part1.18"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
  • draft-ietf-httpbis/latest/p6-cache.xml

    r395 r401  
    12631263   if and only if the selecting request-headers in the first request can
    12641264   be transformed to the selecting request-headers in the second request
    1265    by adding or removing linear white space (LWS) at places where this
     1265   by adding or removing linear whitespace (LWS) at places where this
    12661266   is allowed by the corresponding BNF, and/or combining multiple
    12671267   message-header fields with the same field name following the rules
Note: See TracChangeset for help on using the changeset viewer.