![(please configure the [header_logo] section in trac.ini)](https://www.ietf.org/images/ietflogotrans.gif)
Changeset 235 for draft-ietf-httpbis
- Timestamp:
- 01/04/08 14:44:27 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
-
p2-semantics.html (modified) (6 diffs)
-
p2-semantics.xml (modified) (2 diffs)
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r234 r235 1164 1164 <div id="rfc.iref.s.15"></div> 1165 1165 <h3 id="rfc.section.9.3.6"><a href="#rfc.section.9.3.6">9.3.6</a> <a id="status.305" href="#status.305">305 Use Proxy</a></h3> 1166 <p id="rfc.section.9.3.6.p.1">The requested resource <em class="bcp14">MUST</em> be accessed through the proxy given by the Location field. The Location field gives the URI of the proxy. The recipient is 1167 expected to repeat this single request via the proxy. 305 responses <em class="bcp14">MUST</em> only be generated by origin servers. 1168 </p> 1169 <dl class="empty"> 1170 <dd> <b>Note:</b> <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a> was not clear that 305 was intended to redirect a single request, and to be generated by origin servers only. Not observing 1171 these limitations has significant security consequences. 1172 </dd> 1173 </dl> 1166 <p id="rfc.section.9.3.6.p.1">The 305 status was defined in a previous version of this specification (see <a href="#changes.from.rfc.2616" title="Changes from RFC 2616">Appendix A.2</a>), and is now deprecated. 1167 </p> 1174 1168 <div id="rfc.iref.38"></div> 1175 1169 <div id="rfc.iref.s.16"></div> … … 1706 1700 <p id="rfc.section.A.1.p.5">Clean up confusion between 403 and 404 responses. (Section <a href="#status.403" id="rfc.xref.status.403.2" title="403 Forbidden">9.4.4</a>, <a href="#status.404" id="rfc.xref.status.404.2" title="404 Not Found">9.4.5</a>, and <a href="#status.410" id="rfc.xref.status.410.2" title="410 Gone">9.4.11</a>) 1707 1701 </p> 1708 <p id="rfc.section.A.1.p.6">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="#RFC2068" id="rfc.xref.RFC2068. 3"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>.1702 <p id="rfc.section.A.1.p.6">The PATCH<span id="rfc.iref.p.3"></span><span id="rfc.iref.m.10"></span>, LINK<span id="rfc.iref.l.2"></span><span id="rfc.iref.m.11"></span>, UNLINK<span id="rfc.iref.u.2"></span><span id="rfc.iref.m.12"></span> methods were defined but not commonly implemented in previous versions of this specification. See <a href="#RFC2068" id="rfc.xref.RFC2068.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>. 1709 1703 </p> 1710 1704 <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a> <a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> … … 1714 1708 user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.2" title="301 Moved Permanently">9.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.2" title="302 Found">9.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.2" title="307 Temporary Redirect">9.3.8</a>) 1715 1709 </p> 1716 <p id="rfc.section.A.2.p.3">Reclassify Allow header as response header, removing the option to specify it in a PUT request. (<a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section 10.1</a>) 1717 </p> 1718 <p id="rfc.section.A.2.p.4">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications 1710 <p id="rfc.section.A.2.p.3">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the requested resource 1711 must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient 1712 was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.2" title="305 Use Proxy">Section 9.3.6</a>) 1713 </p> 1714 <p id="rfc.section.A.2.p.4">Reclassify Allow header as response header, removing the option to specify it in a PUT request. (<a href="#header.allow" id="rfc.xref.header.allow.3" title="Allow">Section 10.1</a>) 1715 </p> 1716 <p id="rfc.section.A.2.p.5">Correct syntax of Location header to allow fragment, as referred symbol wasn't what was expected, and add some clarifications 1719 1717 as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section 10.4</a>) 1720 1718 </p> 1721 <p id="rfc.section.A.2.p. 5">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly1719 <p id="rfc.section.A.2.p.6">In the description of the Server header, the Via field was described as a SHOULD. The requirement was and is stated correctly 1722 1720 in the description of the Via header in <a href="p1-messaging.html#header.via" title="Via">Section 8.9</a> of <a href="#Part1" id="rfc.xref.Part1.25"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.3" title="Server">Section 10.8</a>) 1723 1721 </p> … … 1827 1825 <li class="indline1">303 See Other (status code) <a class="iref" href="#rfc.xref.status.303.1">5</a>, <a class="iref" href="#rfc.iref.35"><b>9.3.4</b></a></li> 1828 1826 <li class="indline1">304 Not Modified (status code) <a class="iref" href="#rfc.xref.status.304.1">5</a>, <a class="iref" href="#rfc.iref.36"><b>9.3.5</b></a></li> 1829 <li class="indline1">305 Use Proxy (status code) <a class="iref" href="#rfc.xref.status.305.1">5</a>, <a class="iref" href="#rfc.iref.37"><b>9.3.6</b></a> </li>1827 <li class="indline1">305 Use Proxy (status code) <a class="iref" href="#rfc.xref.status.305.1">5</a>, <a class="iref" href="#rfc.iref.37"><b>9.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">A.2</a></li> 1830 1828 <li class="indline1">306 (Unused) (status code) <a class="iref" href="#rfc.iref.38"><b>9.3.7</b></a></li> 1831 1829 <li class="indline1">307 Temporary Redirect (status code) <a class="iref" href="#rfc.xref.status.307.1">5</a>, <a class="iref" href="#rfc.iref.39"><b>9.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">A.2</a></li> … … 2015 2013 <li class="indline1">Retry-After header <a class="iref" href="#rfc.xref.header.retry-after.1">6</a>, <a class="iref" href="#rfc.iref.r.2"><b>10.7</b></a></li> 2016 2014 <li class="indline1"><em>RFC1945</em> <a class="iref" href="#rfc.xref.RFC1945.1">9.3.3</a>, <a class="iref" href="#RFC1945"><b>14.2</b></a></li> 2017 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">9.3.3</a>, <a class="iref" href="# rfc.xref.RFC2068.2">9.3.6</a>, <a class="iref" href="#RFC2068"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.3">A.1</a></li>2015 <li class="indline1"><em>RFC2068</em> <a class="iref" href="#rfc.xref.RFC2068.1">9.3.3</a>, <a class="iref" href="#RFC2068"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2068.2">A.1</a></li> 2018 2016 <li class="indline1"><em>RFC2119</em> <a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li> 2019 2017 <li class="indline1"><em>RFC2616</em> <a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>14.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li> … … 2042 2040 <li class="indline1">303 See Other <a class="iref" href="#rfc.xref.status.303.1">5</a>, <a class="iref" href="#rfc.iref.s.13"><b>9.3.4</b></a></li> 2043 2041 <li class="indline1">304 Not Modified <a class="iref" href="#rfc.xref.status.304.1">5</a>, <a class="iref" href="#rfc.iref.s.14"><b>9.3.5</b></a></li> 2044 <li class="indline1">305 Use Proxy <a class="iref" href="#rfc.xref.status.305.1">5</a>, <a class="iref" href="#rfc.iref.s.15"><b>9.3.6</b></a> </li>2042 <li class="indline1">305 Use Proxy <a class="iref" href="#rfc.xref.status.305.1">5</a>, <a class="iref" href="#rfc.iref.s.15"><b>9.3.6</b></a>, <a class="iref" href="#rfc.xref.status.305.2">A.2</a></li> 2045 2043 <li class="indline1">306 (Unused) <a class="iref" href="#rfc.iref.s.16"><b>9.3.7</b></a></li> 2046 2044 <li class="indline1">307 Temporary Redirect <a class="iref" href="#rfc.xref.status.307.1">5</a>, <a class="iref" href="#rfc.iref.s.17"><b>9.3.8</b></a>, <a class="iref" href="#rfc.xref.status.307.2">A.2</a></li> -
draft-ietf-httpbis/latest/p2-semantics.xml
r234 r235 1305 1305 <iref primary="true" item="Status Codes" subitem="305 Use Proxy" x:for-anchor=""/> 1306 1306 <t> 1307 The requested resource &MUST; be accessed through the proxy given by 1308 the Location field. The Location field gives the URI of the proxy. 1309 The recipient is expected to repeat this single request via the 1310 proxy. 305 responses &MUST; only be generated by origin servers. 1311 <list><t> 1312 <x:h>Note:</x:h> <xref target="RFC2068"/> was not clear that 305 was intended to redirect a 1313 single request, and to be generated by origin servers only. Not 1314 observing these limitations has significant security consequences. 1315 </t></list> 1307 The 305 status was defined in a previous version of this specification 1308 (see <xref target="changes.from.rfc.2616"/>), and is now deprecated. 1316 1309 </t> 1317 1310 </section> … … 2643 2636 <xref format="counter" target="status.302"/> and 2644 2637 <xref format="counter" target="status.307"/>) 2638 </t> 2639 <t> 2640 Deprecate 305 Use Proxy status code, because user agents did not implement it. 2641 It used to indicate that the requested resource must be accessed through the 2642 proxy given by the Location field. The Location field gave the URI of the 2643 proxy. The recipient was expected to repeat this single request via the proxy. 2644 (<xref target="status.305"/>) 2645 2645 </t> 2646 2646 <t>
Note: See TracChangeset
for help on using the changeset viewer.
