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/p1-messaging.html

    r1051 r1055  
    16341634            described in <a href="#header.te" id="rfc.xref.header.te.2" title="TE">Section&nbsp;9.5</a>; or,
    16351635         </li>
    1636          <li>the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the recipient
    1637             could use the message (in a manner acceptable to the origin server) without receiving this metadata. In other words, the origin
    1638             server is willing to accept the possibility that the trailer fields might be silently discarded along the path to the client.
     1636         <li>the trailer fields consist entirely of optional metadata, and the recipient could use the message (in a manner acceptable
     1637            to the server where the field originated) without receiving it. In other words, the server that generated the header (often
     1638            but not always the origin server) is willing to accept the possibility that the trailer fields might be silently discarded
     1639            along the path to the client.
    16391640         </li>
    16401641      </ol>
     
    34553456      <p id="rfc.section.D.13.p.1">Closed issues: </p>
    34563457      <ul>
     3458         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/193">http://tools.ietf.org/wg/httpbis/trac/ticket/193</a>&gt;: "Trailer requirements"
     3459         </li>
    34573460         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/204">http://tools.ietf.org/wg/httpbis/trac/ticket/204</a>&gt;: "Text about clock requirement for caches belongs in p6"
    34583461         </li>
Note: See TracChangeset for help on using the changeset viewer.