Ignore:
Timestamp:
May 19, 2013, 1:09:53 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) properly target the whitespace requirements to sender or recipient; move the requirement on parsing whitespace sequences to the field parsing section

File:
1 edited

Legend:

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

    r2252 r2253  
    12561256<t anchor="rule.OWS">
    12571257   The OWS rule is used where zero or more linear whitespace octets might
    1258    appear. OWS &SHOULD; either not be generated or be generated as a single
    1259    SP. Multiple OWS octets that occur within field-content &SHOULD; either
    1260    be replaced with a single SP or transformed to all SP octets (each
    1261    octet other than SP replaced with SP) before interpreting the field value
    1262    or forwarding the message downstream.
     1258   appear. For protocol elements where optional whitespace is preferred to
     1259   improve readability, a sender &SHOULD; generate the optional whitespace
     1260   as a single SP; otherwise, a sender &SHOULD-NOT; generate optional
     1261   whitespace except as needed to white-out invalid or unwanted protocol
     1262   elements during in-place message filtering.
    12631263</t>
    12641264<t anchor="rule.RWS">
    1265    RWS is used when at least one linear whitespace octet is required to
    1266    separate field tokens. RWS &SHOULD; be generated as a single SP.
    1267    Multiple RWS octets that occur within field-content &SHOULD; either
    1268    be replaced with a single SP or transformed to all SP octets before
    1269    interpreting the field value or forwarding the message downstream.
     1265   The RWS rule is used when at least one linear whitespace octet is required
     1266   to separate field tokens. A sender &SHOULD; generate RWS as a single SP.
    12701267</t>
    12711268<t anchor="rule.BWS">
    1272    BWS is used where the grammar allows optional whitespace, for historical
    1273    reasons, but it &MUST-NOT; be generated in messages; recipients &MUST;
    1274    accept such bad optional whitespace and remove it before interpreting the
    1275    field value.
     1269   The BWS rule is used where the grammar allows optional whitespace only for
     1270   historical reasons. A sender &MUST-NOT; generate BWS in messages.
     1271   A recipient &MUST; parse for such bad whitespace and remove it before
     1272   interpreting the protocol element.
    12761273</t>
    12771274<t anchor="rule.whitespace">
     
    13061303   field value or after the last non-whitespace octet of the field value
    13071304   is ignored and &SHOULD; be removed before further processing (as this does
    1308    not change the meaning of the header field).
     1305   not change the meaning of the header field).
     1306</t>
     1307<t>
     1308   A recipient of field-content containing multiple sequential octets of
     1309   optional (OWS) or required (RWS) whitespace &SHOULD; either replace the
     1310   sequence with a single SP or transform any non-SP octets in the sequence to
     1311   SP octets before interpreting the field value or forwarding the message
     1312   downstream.
    13091313</t>
    13101314<t>
Note: See TracChangeset for help on using the changeset viewer.