Ignore:
Timestamp:
23/10/10 09:17:48 (10 years ago)
Author:
julian.reschke@…
Message:

Back-port clarification of trailer requirements to -12 (see #193 and [1053])

File:
1 edited

Legend:

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

    r1051 r1055  
    20472047     acceptable in the transfer-coding of the  response, as described in
    20482048     <xref target="header.te"/>; or,</t>
    2049 
    2050     <t>the server is the origin server for the response, the trailer
    2051      fields consist entirely of optional metadata, and the recipient
    2052      could use the message (in a manner acceptable to the origin server)
    2053      without receiving this metadata.  In other words, the origin server
    2054      is willing to accept the possibility that the trailer fields might
    2055      be silently discarded along the path to the client.</t>
     2049     
     2050    <t>the trailer fields consist entirely of optional metadata, and the
     2051    recipient could use the message (in a manner acceptable to the server where
     2052    the field originated) without receiving it. In other words, the server that
     2053    generated the header (often but not always the origin server) is willing to
     2054    accept the possibility that the trailer fields might be silently discarded
     2055    along the path to the client.</t>
    20562056  </list>
    20572057</t>
     
    56125612  <list style="symbols">
    56135613    <t>
     5614      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/193"/>:
     5615      "Trailer requirements"
     5616    </t>
     5617    <t>
    56145618      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/204"/>:
    56155619      "Text about clock requirement for caches belongs in p6"
Note: See TracChangeset for help on using the changeset viewer.