Ignore:
Timestamp:
Oct 16, 2011, 5:32:05 AM (8 years ago)
Author:
julian.reschke@…
Message:

add advice on parameter syntax (token/quoted-string) (see #231)

File:
1 edited

Legend:

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

    r1446 r1448  
    4949  <!ENTITY header-content-location    "<xref target='Part3' x:rel='#header.content-location' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5050  <!ENTITY header-content-range       "<xref target='Part5' x:rel='#header.content-range' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     51  <!ENTITY header-content-type        "<xref target='Part3' x:rel='#header.content-type' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5152  <!ENTITY header-etag                "<xref target='Part4' x:rel='#header.etag' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    5253  <!ENTITY header-expires             "<xref target='Part6' x:rel='#header.expires' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    6869  <!ENTITY header-warning             "<xref target='Part6' x:rel='#header.warning' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    6970  <!ENTITY header-www-authenticate    "<xref target='Part7' x:rel='#header.www-authenticate' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     71  <!ENTITY media-types                "<xref target='Part3' x:rel='#media.types' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7072  <!ENTITY message-body               "<xref target='Part1' x:rel='#message.body' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
    7173  <!ENTITY product-tokens             "<xref target='Part1' x:rel='#product.tokens' xmlns:x='http://purl.org/net/xml2rfc/ext'/>">
     
    522524</artwork></figure>
    523525<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;).
     532</t>
     533<t>
    524534   Authors of specifications defining new header fields are advised to consider
    525535   documenting:
Note: See TracChangeset for help on using the changeset viewer.