Ignore:
Timestamp:
Oct 20, 2011, 1:58:03 AM (8 years ago)
Author:
julian.reschke@…
Message:

param names are case-insensitive (see #231)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1448 r1451  
    524524</artwork></figure>
    525525<t>
    526    Many header fields use a format including named parameters (for instance,
    527    Content-Type, defined in &header-content-type;). Allowing both unquoted
    528    (token) and quoted (quoted-string) syntax for the parameter value enables
    529    recipients to use existing parser components. Also, the meaning of a value
    530    ought to be independent of the syntax variant used for it (for an example,
    531    see the notes on parameter handling for media types in &media-types;).
     526   Many header fields use a format including (case-insensitively) named
     527   parameters (for instance, Content-Type, defined in &header-content-type;).
     528   Allowing both unquoted (token) and quoted (quoted-string) syntax for the
     529   parameter value enables recipients to use existing parser components. Also,
     530   the meaning of a value ought to be independent of the syntax variant used
     531   for it (for an example, see the notes on parameter handling for media types
     532   in &media-types;).
    532533</t>
    533534<t>
Note: See TracChangeset for help on using the changeset viewer.