Changeset 2533


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

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

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

Legend:

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

    r2531 r2533  
    12721272         <div id="header.fields">
    12731273            <h2 id="rfc.section.3.2"><a href="#rfc.section.3.2">3.2</a>&nbsp;<a href="#header.fields">Header Fields</a></h2>
    1274             <p id="rfc.section.3.2.p.1">Each HTTP header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the
    1275                field value, and optional trailing whitespace.
     1274            <p id="rfc.section.3.2.p.1">Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field
     1275               value, and optional trailing whitespace.
    12761276            </p>
    12771277            <div id="rfc.figure.u.18"></div><pre class="inline"><span id="rfc.iref.g.35"></span><span id="rfc.iref.g.36"></span><span id="rfc.iref.g.37"></span><span id="rfc.iref.g.38"></span><span id="rfc.iref.g.39"></span>  <a href="#header.fields" class="smpl">header-field</a>   = <a href="#header.fields" class="smpl">field-name</a> ":" <a href="#rule.whitespace" class="smpl">OWS</a> <a href="#header.fields" class="smpl">field-value</a> <a href="#rule.whitespace" class="smpl">OWS</a>
     
    12851285               the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field is defined in <a href="p2-semantics.html#header.date" title="Date">Section 7.1.1.2</a> of <a href="#Part2" id="rfc.xref.Part2.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content">[Part2]</cite></a> as containing the origination timestamp for the message in which it appears.
    12861286            </p>
    1287             <p id="rfc.section.3.2.p.4">Extraction of field-name/field-value pairs from a message is generic and thus independent of the actual field name. Consequently,
    1288                the ABNF specified for each header field only defines the syntax of the field-value (not the whole header-field, as it was
    1289                the case in previous revisions of this specification).
     1287            <p id="rfc.section.3.2.p.4">Since messages are parsed using a generic algorithm, independent of the individual header field names, the contents within
     1288               a given field-value are not parsed until a later stage of message interpretation (usually after the message's entire header
     1289               section has been processed). Consequently, this specification does not use specific ABNF rules to define each "Field-Name:
     1290               Field Value" pair, as was done in previous editions. Instead, this specification defines each of its header fields using an
     1291               ABNF rule that is named according to the registered field-name and that defines only the syntax within the field-value (i.e.,
     1292               after it has been extracted from the header section by a generic field parser).
    12901293            </p>
    12911294            <div id="field.extensibility">
  • 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.