Changeset 840 for draft-ietf-httpbis
- Timestamp:
- 09/07/10 09:59:01 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r839 r840 1768 1768 </p> 1769 1769 <h4 id="rfc.section.7.1.3.1"><a href="#rfc.section.7.1.3.1">7.1.3.1</a> <a id="end-to-end.and.hop-by-hop.headers" href="#end-to-end.and.hop-by-hop.headers">End-to-end and Hop-by-hop Headers</a></h4> 1770 <p id="rfc.section.7.1.3.1.p.1"> <span class="comment" id="TODO-end-to-end">[<a href="#TODO-end-to-end" class="smpl">TODO-end-to-end</a>: Restored from <<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-05#section-7.1">http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-05#section-7.1</a>>. See also <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/60">http://tools.ietf.org/wg/httpbis/trac/ticket/60</a>>. --jre]</span> 1771 </p> 1772 <p id="rfc.section.7.1.3.1.p.2">For the purpose of defining the behavior of caches and non-caching proxies, we divide HTTP headers into two categories: </p> 1770 <p id="rfc.section.7.1.3.1.p.1">For the purpose of defining the behavior of caches and non-caching proxies, we divide HTTP headers into two categories: </p> 1773 1771 <ul> 1774 1772 <li>End-to-end headers, which are transmitted to the ultimate recipient of a request or response. End-to-end headers in responses … … 1779 1777 </li> 1780 1778 </ul> 1781 <p id="rfc.section.7.1.3.1.p. 3">The following HTTP/1.1 headers are hop-by-hop headers: </p>1779 <p id="rfc.section.7.1.3.1.p.2">The following HTTP/1.1 headers are hop-by-hop headers: </p> 1782 1780 <ul> 1783 1781 <li>Connection</li> … … 1790 1788 <li>Upgrade</li> 1791 1789 </ul> 1792 <p id="rfc.section.7.1.3.1.p. 4">All other headers defined by HTTP/1.1 are end-to-end headers.</p>1793 <p id="rfc.section.7.1.3.1.p. 5">Other hop-by-hop headers <em class="bcp14">MUST</em> be listed in a Connection header (<a href="#header.connection" id="rfc.xref.header.connection.4" title="Connection">Section 9.1</a>).1790 <p id="rfc.section.7.1.3.1.p.3">All other headers defined by HTTP/1.1 are end-to-end headers.</p> 1791 <p id="rfc.section.7.1.3.1.p.4">Other hop-by-hop headers <em class="bcp14">MUST</em> be listed in a Connection header (<a href="#header.connection" id="rfc.xref.header.connection.4" title="Connection">Section 9.1</a>). 1794 1792 </p> 1795 1793 <h4 id="rfc.section.7.1.3.2"><a href="#rfc.section.7.1.3.2">7.1.3.2</a> <a id="non-modifiable.headers" href="#non-modifiable.headers">Non-modifiable Headers</a></h4> 1796 <p id="rfc.section.7.1.3.2.p.1"> <span class="comment" id="TODO-non-mod-headers">[<a href="#TODO-non-mod-headers" class="smpl">TODO-non-mod-headers</a>: Restored from <<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-05#section-7.2">http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-05#section-7.2</a>>. See also <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/60">http://tools.ietf.org/wg/httpbis/trac/ticket/60</a>>. --jre]</span> 1797 </p> 1798 <p id="rfc.section.7.1.3.2.p.2">Some features of HTTP/1.1, such as Digest Authentication, depend on the value of certain end-to-end headers. A transparent 1794 <p id="rfc.section.7.1.3.2.p.1">Some features of HTTP/1.1, such as Digest Authentication, depend on the value of certain end-to-end headers. A transparent 1799 1795 proxy <em class="bcp14">SHOULD NOT</em> modify an end-to-end header unless the definition of that header requires or specifically allows that. 1800 1796 </p> 1801 <p id="rfc.section.7.1.3.2.p. 3">A transparent proxy <em class="bcp14">MUST NOT</em> modify any of the following fields in a request or response, and it <em class="bcp14">MUST NOT</em> add any of these fields if not already present:1797 <p id="rfc.section.7.1.3.2.p.2">A transparent proxy <em class="bcp14">MUST NOT</em> modify any of the following fields in a request or response, and it <em class="bcp14">MUST NOT</em> add any of these fields if not already present: 1802 1798 </p> 1803 1799 <ul> … … 1807 1803 <li>Last-Modified</li> 1808 1804 </ul> 1809 <p id="rfc.section.7.1.3.2.p. 4">A transparent proxy <em class="bcp14">MUST NOT</em> modify any of the following fields in a response:1805 <p id="rfc.section.7.1.3.2.p.3">A transparent proxy <em class="bcp14">MUST NOT</em> modify any of the following fields in a response: 1810 1806 </p> 1811 1807 <ul> 1812 1808 <li>Expires</li> 1813 1809 </ul> 1814 <p id="rfc.section.7.1.3.2.p. 5">but it <em class="bcp14">MAY</em> add any of these fields if not already present. If an Expires header is added, it <em class="bcp14">MUST</em> be given a field-value identical to that of the Date header in that response.1815 </p> 1816 <p id="rfc.section.7.1.3.2.p. 6">A proxy <em class="bcp14">MUST NOT</em> modify or add any of the following fields in a message that contains the no-transform cache-control directive, or in any request:1810 <p id="rfc.section.7.1.3.2.p.4">but it <em class="bcp14">MAY</em> add any of these fields if not already present. If an Expires header is added, it <em class="bcp14">MUST</em> be given a field-value identical to that of the Date header in that response. 1811 </p> 1812 <p id="rfc.section.7.1.3.2.p.5">A proxy <em class="bcp14">MUST NOT</em> modify or add any of the following fields in a message that contains the no-transform cache-control directive, or in any request: 1817 1813 </p> 1818 1814 <ul> … … 1821 1817 <li>Content-Type</li> 1822 1818 </ul> 1823 <p id="rfc.section.7.1.3.2.p. 7">A non-transparent proxy <em class="bcp14">MAY</em> modify or add these fields to a message that does not include no-transform, but if it does so, it <em class="bcp14">MUST</em> add a Warning 214 (Transformation applied) if one does not already appear in the message (see <a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>).1824 </p> 1825 <div class="note" id="rfc.section.7.1.3.2.p. 8">1819 <p id="rfc.section.7.1.3.2.p.6">A non-transparent proxy <em class="bcp14">MAY</em> modify or add these fields to a message that does not include no-transform, but if it does so, it <em class="bcp14">MUST</em> add a Warning 214 (Transformation applied) if one does not already appear in the message (see <a href="p6-cache.html#header.warning" title="Warning">Section 3.6</a> of <a href="#Part6" id="rfc.xref.Part6.8"><cite title="HTTP/1.1, part 6: Caching">[Part6]</cite></a>). 1820 </p> 1821 <div class="note" id="rfc.section.7.1.3.2.p.7"> 1826 1822 <p> <b>Warning:</b> Unnecessary modification of end-to-end headers might cause authentication failures if stronger authentication mechanisms are 1827 1823 introduced in later versions of HTTP. Such authentication mechanisms <em class="bcp14">MAY</em> rely on the values of header fields not listed here. 1828 1824 </p> 1829 1825 </div> 1830 <p id="rfc.section.7.1.3.2.p. 9">The Content-Length field of a request or response is added or deleted according to the rules in <a href="#message.length" title="Message Length">Section 3.4</a>. A transparent proxy <em class="bcp14">MUST</em> preserve the entity-length (<a href="p3-payload.html#entity.length" title="Entity Length">Section 3.2.2</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) of the entity-body, although it <em class="bcp14">MAY</em> change the transfer-length (<a href="#message.length" title="Message Length">Section 3.4</a>).1826 <p id="rfc.section.7.1.3.2.p.8">The Content-Length field of a request or response is added or deleted according to the rules in <a href="#message.length" title="Message Length">Section 3.4</a>. A transparent proxy <em class="bcp14">MUST</em> preserve the entity-length (<a href="p3-payload.html#entity.length" title="Entity Length">Section 3.2.2</a> of <a href="#Part3" id="rfc.xref.Part3.9"><cite title="HTTP/1.1, part 3: Message Payload and Content Negotiation">[Part3]</cite></a>) of the entity-body, although it <em class="bcp14">MAY</em> change the transfer-length (<a href="#message.length" title="Message Length">Section 3.4</a>). 1831 1827 </p> 1832 1828 <h3 id="rfc.section.7.1.4"><a href="#rfc.section.7.1.4">7.1.4</a> <a id="persistent.practical" href="#persistent.practical">Practical Considerations</a></h3> -
draft-ietf-httpbis/latest/p1-messaging.xml
r839 r840 2371 2371 2372 2372 <section title="End-to-end and Hop-by-hop Headers" anchor="end-to-end.and.hop-by-hop.headers"> 2373 < t>2373 <!--<t> 2374 2374 <cref anchor="TODO-end-to-end" source="jre"> 2375 2375 Restored from <eref target="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-05#section-7.1"/>. 2376 2376 See also <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/60"/>. 2377 2377 </cref> 2378 </t> 2378 </t>--> 2379 2379 <t> 2380 2380 For the purpose of defining the behavior of caches and non-caching … … 2414 2414 2415 2415 <section title="Non-modifiable Headers" anchor="non-modifiable.headers"> 2416 < t>2416 <!--<t> 2417 2417 <cref anchor="TODO-non-mod-headers" source="jre"> 2418 2418 Restored from <eref target="http://tools.ietf.org/html/draft-ietf-httpbis-p6-cache-05#section-7.2"/>. 2419 2419 See also <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/60"/>. 2420 2420 </cref> 2421 </t> 2421 </t>--> 2422 2422 <t> 2423 2423 Some features of HTTP/1.1, such as Digest Authentication, depend on the
Note: See TracChangeset
for help on using the changeset viewer.