Changeset 2583


Ignore:
Timestamp:
26/01/14 02:35:18 (6 years ago)
Author:
fielding@…
Message:

(editorial) talk about OWS preceding and/or following a field-value; see #531

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

Legend:

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

    r2582 r2583  
    13561356                  have led to security vulnerabilities in request routing and response handling. A server <em class="bcp14">MUST</em> reject any received request message that contains whitespace between a header field-name and colon with a response code of <a href="p2-semantics.html#status.400" class="smpl">400 (Bad Request)</a>. A proxy <em class="bcp14">MUST</em> remove any such whitespace from a response message before forwarding the message downstream.
    13571357               </p>
    1358                <p id="rfc.section.3.2.4.p.3">A field value is preceded by optional whitespace (OWS); a single SP is preferred. The field value does not include any leading
    1359                   or trailing white space: OWS occurring before the first non-whitespace octet of the field value or after the last non-whitespace
    1360                   octet of the field value ought to be excluded by parsers when extracting the field value from a header field.
     1358               <p id="rfc.section.3.2.4.p.3">A field value might be preceded and/or followed by optional whitespace (OWS); a single SP preceding the field-value is preferred
     1359                  for consistent readability by humans. The field value does not include any leading or trailing white space: OWS occurring
     1360                  before the first non-whitespace octet of the field value or after the last non-whitespace octet of the field value ought to
     1361                  be excluded by parsers when extracting the field value from a header field.
    13611362               </p>
    13621363               <p id="rfc.section.3.2.4.p.4">A recipient of field-content containing multiple sequential octets of optional (OWS) or required (RWS) whitespace <em class="bcp14">SHOULD</em> either replace the sequence with a single SP or transform any non-SP octets in the sequence to SP octets before interpreting
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2582 r2583  
    13561356</t>
    13571357<t>
    1358    A field value is preceded by optional whitespace (OWS); a single SP is
    1359    preferred. The field value does not include any leading or trailing white
    1360    space: OWS occurring before the first non-whitespace octet of the field
    1361    value or after the last non-whitespace octet of the field value ought to be
    1362    excluded by parsers when extracting the field value from a header field.
     1358   A field value might be preceded and/or followed by optional whitespace
     1359   (OWS); a single SP preceding the field-value is preferred for consistent
     1360   readability by humans.
     1361   The field value does not include any leading or trailing white space: OWS
     1362   occurring before the first non-whitespace octet of the field value or after
     1363   the last non-whitespace octet of the field value ought to be excluded by
     1364   parsers when extracting the field value from a header field.
    13631365</t>
    13641366<t>
Note: See TracChangeset for help on using the changeset viewer.