Changeset 1463 for draft-ietf-httpbis/latest/p2-semantics.xml
- Timestamp:
- 31/10/11 02:36:49 (11 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.xml
r1458 r1463 545 545 parameters (for instance, Content-Type, defined in &header-content-type;). 546 546 Allowing both unquoted (token) and quoted (quoted-string) syntax for the 547 parameter value enables recipients to use existing parser components. Also,548 the meaning of a value ought to be independent of the syntax variant used549 for it (for an example, see the notes on parameter handling for media types550 in &media-types;).547 parameter value enables recipients to use existing parser components. When 548 allowing both forms, the meaning of a parameter value ought to be 549 independent of the syntax used for it (for an example, see the notes on 550 parameter handling for media types in &media-types;). 551 551 </t> 552 552 <t> … … 557 557 <t>Whether the field is a single value, or whether it can be a list 558 558 (delimited by commas; see &header-fields;).</t> 559 <t>If it does not use the list syntax, how to treat messages where the 560 header field occurs multiple times (a sensible default would be to ignore 561 the header field, but this might not always be the right choice).</t> 562 <t>Furthermore, intermediaries and software libraries might combine 559 <t>If it does not use the list syntax, document how to treat messages 560 where the header field occurs multiple times (a sensible default would 561 be to ignore the header field, but this might not always be the right 562 choice).</t> 563 <t>Note that intermediaries and software libraries might combine 563 564 multiple header field instances into a single one, despite the header 564 565 field not allowing this. A robust format enables recipients to discover
Note: See TracChangeset
for help on using the changeset viewer.