Changeset 257
- Timestamp:
- 02/06/08 14:24:27 (14 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r254 r257 477 477 <tr> 478 478 <td class="header left"></td> 479 <td class="header right">June 1, 2008</td>479 <td class="header right">June 2, 2008</td> 480 480 </tr> 481 481 </table> … … 1920 1920 <h2 id="rfc.section.8.9"><a href="#rfc.section.8.9">8.9</a> <a id="header.via" href="#header.via">Via</a></h2> 1921 1921 <p id="rfc.section.8.9.p.1">The Via general-header field <em class="bcp14">MUST</em> be used by gateways and proxies to indicate the intermediate protocols and recipients between the user agent and the server 1922 on requests, and between the origin server and the client on responses. It is analogous to the "Received" field of <a href="#RFC2822" id="rfc.xref.RFC2822.5"><cite title="Internet Message Format">[RFC2822]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities1922 on requests, and between the origin server and the client on responses. It is analogous to the "Received" field defined in <a href="http://tools.ietf.org/html/rfc2822#section-3.6.7">Section 3.6.7</a> of <a href="#RFC2822" id="rfc.xref.RFC2822.5"><cite title="Internet Message Format">[RFC2822]</cite></a> and is intended to be used for tracking message forwards, avoiding request loops, and identifying the protocol capabilities 1923 1923 of all senders along the request/response chain. 1924 1924 </p> … … 2945 2945 <li class="indline1"><em>Section 2.1</em> <a class="iref" href="#rfc.xref.RFC2822.3">4.2</a></li> 2946 2946 <li class="indline1"><em>Section 3.6.1</em> <a class="iref" href="#rfc.xref.RFC2822.4">8.3</a></li> 2947 <li class="indline1"><em>Section 3.6.7</em> <a class="iref" href="#rfc.xref.RFC2822.5">8.9</a></li> 2947 2948 </ul> 2948 2949 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r254 r257 2799 2799 indicate the intermediate protocols and recipients between the user 2800 2800 agent and the server on requests, and between the origin server and 2801 the client on responses. It is analogous to the "Received" field of2802 <xref target="RFC2822" /> and is intended to be used for tracking message forwards,2801 the client on responses. It is analogous to the "Received" field defined in 2802 <xref target="RFC2822" x:fmt="of" x:sec="3.6.7"/> and is intended to be used for tracking message forwards, 2803 2803 avoiding request loops, and identifying the protocol capabilities of 2804 2804 all senders along the request/response chain.
Note: See TracChangeset
for help on using the changeset viewer.