Ignore:
Timestamp:
Oct 11, 2011, 12:20:37 AM (8 years ago)
Author:
julian.reschke@…
Message:

note the implications of not using the list syntax (see #231)

File:
1 edited

Legend:

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

    r1444 r1446  
    525525   documenting:
    526526  <list style="symbols">
    527     <t>Whether the field is a single value, or whether it can be a list
    528     (delimited by commas; see &header-fields;).</t>
    529     <t>Under what conditions the header field can be used; e.g., only in
     527    <x:lt>
     528      <t>Whether the field is a single value, or whether it can be a list
     529      (delimited by commas; see &header-fields;).</t>
     530      <t>If it does not use the list syntax, how to treat messages where the
     531      header field occurs multiple times (a sensible default would be to ignore
     532      the header field, but this might not always be the right choice).</t>
     533    </x:lt>
     534    <x:lt><t>Under what conditions the header field can be used; e.g., only in
    530535    responses or requests, in all messages, only on responses to a particular
    531     request method.</t>
    532     <t>Whether it is appropriate to list the field-name in the Connection header
    533     (i.e., if the header is to be hop-by-hop, see &header-connection;).</t>
    534     <t>Under what conditions intermediaries are allowed to modify the header
    535     field's value, insert or delete it.</t>
    536     <t>How the header might interact with caching (see <xref target="Part6"/>).</t>
    537     <t>Whether the header field is useful or allowable in trailers (see
    538     &chunked-encoding;).</t>
    539     <t>Whether the header field should be preserved across redirects.</t>
     536    request method.</t></x:lt>
     537    <x:lt><t>Whether it is appropriate to list the field-name in the Connection header
     538    (i.e., if the header is to be hop-by-hop, see &header-connection;).</t></x:lt>
     539    <x:lt><t>Under what conditions intermediaries are allowed to modify the header
     540    field's value, insert or delete it.</t></x:lt>
     541    <x:lt><t>How the header might interact with caching (see <xref target="Part6"/>).</t></x:lt>
     542    <x:lt><t>Whether the header field is useful or allowable in trailers (see
     543    &chunked-encoding;).</t></x:lt>
     544    <x:lt><t>Whether the header field should be preserved across redirects.</t></x:lt>
    540545  </list>
    541546</t>
Note: See TracChangeset for help on using the changeset viewer.