Changeset 2534
- Timestamp:
- 04/01/14 02:07:15 (8 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r2533 r2534 1286 1286 </p> 1287 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 header1289 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 an1291 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 ithas been extracted from the header section by a generic field parser).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 ABNF rules to define the "Field-Name: Field Value" 1290 pair, as was done in previous editions. Instead, this specification uses ABNF rules which are named according to each registered 1291 field name, wherein the rule defines the valid grammar for that field's corresponding field values (i.e., after the field-value 1292 has been extracted from the header section by a generic field parser). 1293 1293 </p> 1294 1294 <div id="field.extensibility"> -
draft-ietf-httpbis/latest/p1-messaging.xml
r2533 r2534 1237 1237 <t> 1238 1238 Since messages are parsed using a generic algorithm, independent of the 1239 individual header field names, the contents within a given field -value are1239 individual header field names, the contents within a given field value are 1240 1240 not parsed until a later stage of message interpretation (usually after the 1241 1241 message's entire header section has been processed). 1242 Consequently, this specification does not use specific ABNF rules to define1243 each"Field-Name: Field Value" pair, as was done in previous editions.1244 Instead, this specification defines each of its header fields using an ABNF1245 rule that is named according to the registered field-name and that defines1246 only the syntax within the field-value (i.e., after it has been extracted1247 from the header section by a generic field parser).1242 Consequently, this specification does not use ABNF rules to define the 1243 "Field-Name: Field Value" pair, as was done in previous editions. 1244 Instead, this specification uses ABNF rules which are named according to 1245 each registered field name, wherein the rule defines the valid grammar for 1246 that field's corresponding field values (i.e., after the field-value 1247 has been extracted from the header section by a generic field parser). 1248 1248 </t> 1249 1249
Note: See TracChangeset
for help on using the changeset viewer.