* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 235


Ignore:
Timestamp:
2008-04-01 07:44:27 (6 years ago)
Author:
julian.reschke@gmx.de
Message:

Deprecate 305 Use Proxy. Relates to #76.

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.html

    r234 r235  
    11641164      <div id="rfc.iref.s.15"></div> 
    11651165      <h3 id="rfc.section.9.3.6"><a href="#rfc.section.9.3.6">9.3.6</a>&nbsp;<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&nbsp;A.2</a>), and is now deprecated. 
     1167      </p> 
    11741168      <div id="rfc.iref.38"></div> 
    11751169      <div id="rfc.iref.s.16"></div> 
     
    17061700      <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>) 
    17071701      </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>. 
    17091703      </p> 
    17101704      <h2 id="rfc.section.A.2"><a href="#rfc.section.A.2">A.2</a>&nbsp;<a id="changes.from.rfc.2616" href="#changes.from.rfc.2616">Changes from RFC 2616</a></h2> 
     
    17141708         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>) 
    17151709      </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&nbsp;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&nbsp;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&nbsp;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 
    17191717         as to when it would not be appropriate. (<a href="#header.location" id="rfc.xref.header.location.3" title="Location">Section&nbsp;10.4</a>) 
    17201718      </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 correctly 
     1719      <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 
    17221720         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&nbsp;10.8</a>) 
    17231721      </p> 
     
    18271825                  <li class="indline1">303 See Other (status code)&nbsp;&nbsp;<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> 
    18281826                  <li class="indline1">304 Not Modified (status code)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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)&nbsp;&nbsp;<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> 
    18301828                  <li class="indline1">306 (Unused) (status code)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.38"><b>9.3.7</b></a></li> 
    18311829                  <li class="indline1">307 Temporary Redirect (status code)&nbsp;&nbsp;<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> 
     
    20152013                  <li class="indline1">Retry-After header&nbsp;&nbsp;<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> 
    20162014                  <li class="indline1"><em>RFC1945</em>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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>&nbsp;&nbsp;<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> 
    20182016                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>14.1</b></a></li> 
    20192017                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<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> 
     
    20422040                        <li class="indline1">303 See Other&nbsp;&nbsp;<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> 
    20432041                        <li class="indline1">304 Not Modified&nbsp;&nbsp;<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&nbsp;&nbsp;<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&nbsp;&nbsp;<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> 
    20452043                        <li class="indline1">306 (Unused)&nbsp;&nbsp;<a class="iref" href="#rfc.iref.s.16"><b>9.3.7</b></a></li> 
    20462044                        <li class="indline1">307 Temporary Redirect&nbsp;&nbsp;<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  
    13051305  <iref primary="true" item="Status Codes" subitem="305 Use Proxy" x:for-anchor=""/> 
    13061306<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. 
    13161309</t> 
    13171310</section> 
     
    26432636  <xref format="counter" target="status.302"/> and 
    26442637  <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"/>) 
    26452645</t> 
    26462646<t> 
Note: See TracChangeset for help on using the changeset viewer.