Ignore:
Timestamp:
Oct 23, 2010, 12:33:38 AM (9 years ago)
Author:
julian.reschke@…
Message:

Clarify trailer requirements (see #193)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r1052 r1053  
    20862086     acceptable in the transfer-coding of the  response, as described in
    20872087     <xref target="header.te"/>; or,</t>
    2088 
    2089     <t>the server is the origin server for the response, the trailer
    2090      fields consist entirely of optional metadata, and the recipient
    2091      could use the message (in a manner acceptable to the origin server)
    2092      without receiving this metadata.  In other words, the origin server
    2093      is willing to accept the possibility that the trailer fields might
    2094      be silently discarded along the path to the client.</t>
     2088     
     2089    <t>the trailer fields consist entirely of optional metadata, and the
     2090    recipient could use the message (in a manner acceptable to the server where
     2091    the field originated) without receiving it. In other words, the server that
     2092    generated the header (often but not always the origin server) is willing to
     2093    accept the possibility that the trailer fields might be silently discarded
     2094    along the path to the client.</t>
    20952095  </list>
    20962096</t>
     
    56835683<section title="Since draft-ietf-httpbis-p1-messaging-12" anchor="changes.since.12">
    56845684<t>
    5685   None yet.
     5685  Closed issues:
     5686  <list style="symbols">
     5687    <t>
     5688      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/193"/>:
     5689      "Trailer requirements"
     5690    </t>
     5691  </list>
    56865692</t>
    56875693</section>
Note: See TracChangeset for help on using the changeset viewer.