Ignore:
Timestamp:
04/01/14 01:46:01 (8 years ago)
Author:
fielding@…
Message:

rephrase [2528] to be more understandable by non-spec-authors; see #540

File:
1 edited

Legend:

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

    r2531 r2533  
    12161216  <x:anchor-alias value="obs-fold"/>
    12171217<t>
    1218    Each HTTP header field consists of a case-insensitive field name
     1218   Each header field consists of a case-insensitive field name
    12191219   followed by a colon (":"), optional leading whitespace, the field value,
    12201220   and optional trailing whitespace.
     
    12361236</t>
    12371237<t>
    1238    Extraction of field-name/field-value pairs from a message is generic and
    1239    thus independent of the actual field name. Consequently, the ABNF specified
    1240    for each header field only defines the syntax of the field-value (not the
    1241    whole header-field, as it was the case in previous revisions of this
    1242    specification).
     1238   Since messages are parsed using a generic algorithm, independent of the
     1239   individual header field names, the contents within a given field-value are
     1240   not parsed until a later stage of message interpretation (usually after the
     1241   message's entire header section has been processed).
     1242   Consequently, this specification does not use specific ABNF rules to define
     1243   each "Field-Name: Field Value" pair, as was done in previous editions.
     1244   Instead, this specification defines each of its header fields using an ABNF
     1245   rule that is named according to the registered field-name and that defines
     1246   only the syntax within the field-value (i.e., after it has been extracted
     1247   from the header section by a generic field parser).
    12431248</t>
    12441249
Note: See TracChangeset for help on using the changeset viewer.