Changeset 1160


Ignore:
Timestamp:
Mar 10, 2011, 11:50:18 AM (8 years ago)
Author:
julian.reschke@…
Message:

note changes for [1158], in particular update Changes from 2616, see also #79, #102, #103, #104, #112, #180, #267

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p2-semantics.html

    r1158 r1160  
    27252725      <p id="rfc.section.A.p.2">Clarify definition of POST. (<a href="#POST" id="rfc.xref.POST.3" title="POST">Section&nbsp;7.5</a>)
    27262726      </p>
    2727       <p id="rfc.section.A.p.3">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section&nbsp;7.9</a>)
    2728       </p>
    2729       <p id="rfc.section.A.p.4">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
     2727      <p id="rfc.section.A.p.3">Remove requirement to handle all Content-* header fields; ban use of Content-Range with PUT. (<a href="#PUT" id="rfc.xref.PUT.3" title="PUT">Section&nbsp;7.6</a>)
     2728      </p>
     2729      <p id="rfc.section.A.p.4">Take over definition of CONNECT method from <a href="#RFC2817" id="rfc.xref.RFC2817.3"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>. (<a href="#CONNECT" id="rfc.xref.CONNECT.3" title="CONNECT">Section&nbsp;7.9</a>)
     2730      </p>
     2731      <p id="rfc.section.A.p.5">Failed to consider that there are many other request methods that are safe to automatically redirect, and further that the
    27302732         user agent is able to make that determination based on the request method semantics. (Sections <a href="#status.301" id="rfc.xref.status.301.3" title="301 Moved Permanently">8.3.2</a>, <a href="#status.302" id="rfc.xref.status.302.3" title="302 Found">8.3.3</a> and <a href="#status.307" id="rfc.xref.status.307.4" title="307 Temporary Redirect">8.3.8</a>)
    27312733      </p>
    2732       <p id="rfc.section.A.p.5">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
     2734      <p id="rfc.section.A.p.6">Deprecate 305 Use Proxy status code, because user agents did not implement it. It used to indicate that the target resource
    27332735         must be accessed through the proxy given by the Location field. The Location field gave the URI of the proxy. The recipient
    27342736         was expected to repeat this single request via the proxy. (<a href="#status.305" id="rfc.xref.status.305.3" title="305 Use Proxy">Section&nbsp;8.3.6</a>)
    27352737      </p>
    2736       <p id="rfc.section.A.p.6">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section&nbsp;8.4.19</a>)
    2737       </p>
    2738       <p id="rfc.section.A.p.7">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
     2738      <p id="rfc.section.A.p.7">Define status 426 (Upgrade Required) (this was incorporated from <a href="#RFC2817" id="rfc.xref.RFC2817.4"><cite title="Upgrading to TLS Within HTTP/1.1">[RFC2817]</cite></a>). (<a href="#status.426" id="rfc.xref.status.426.3" title="426 Upgrade Required">Section&nbsp;8.4.19</a>)
     2739      </p>
     2740      <p id="rfc.section.A.p.8">Reclassify "Allow" as response header field, removing the option to specify it in a PUT request. Relax the server requirement
    27392741         on the contents of the Allow header field and remove requirement on clients to always trust the header field value. (<a href="#header.allow" id="rfc.xref.header.allow.4" title="Allow">Section&nbsp;9.1</a>)
    27402742      </p>
    2741       <p id="rfc.section.A.p.8">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
     2743      <p id="rfc.section.A.p.9">Correct syntax of Location header field to allow URI references (including relative references and fragments), as referred
    27422744         symbol "absoluteURI" wasn't what was expected, and add some clarifications as to when use of fragments would not be appropriate.
    27432745         (<a href="#header.location" id="rfc.xref.header.location.4" title="Location">Section&nbsp;9.4</a>)
    27442746      </p>
    2745       <p id="rfc.section.A.p.9">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;9.5</a>)
    2746       </p>
    2747       <p id="rfc.section.A.p.10">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>)
    2748       </p>
    2749       <p id="rfc.section.A.p.11">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
     2747      <p id="rfc.section.A.p.10">Restrict Max-Forwards header field to OPTIONS and TRACE (previously, extension methods could have used it as well). (<a href="#header.max-forwards" id="rfc.xref.header.max-forwards.5" title="Max-Forwards">Section&nbsp;9.5</a>)
     2748      </p>
     2749      <p id="rfc.section.A.p.11">Allow Referer field value of "about:blank" as alternative to not specifying it. (<a href="#header.referer" id="rfc.xref.header.referer.3" title="Referer">Section&nbsp;9.6</a>)
     2750      </p>
     2751      <p id="rfc.section.A.p.12">In the description of the Server header field, the Via field was described as a SHOULD. The requirement was and is stated
    27502752         correctly in the description of the Via header field in <a href="p1-messaging.html#header.via" title="Via">Section 9.9</a> of <a href="#Part1" id="rfc.xref.Part1.38"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>. (<a href="#header.server" id="rfc.xref.header.server.4" title="Server">Section&nbsp;9.8</a>)
    27512753      </p>
    … …  
    30713073            in some cases)
    30723074         </li>
     3075         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/79">http://tools.ietf.org/wg/httpbis/trac/ticket/79</a>&gt;: "Content-* vs. PUT"
     3076         </li>
    30733077         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/88">http://tools.ietf.org/wg/httpbis/trac/ticket/88</a>&gt;: "205 Bodies"
    30743078         </li>
     3079         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/102">http://tools.ietf.org/wg/httpbis/trac/ticket/102</a>&gt;: "Understanding Content-* on non-PUT requests"
     3080         </li>
     3081         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/103">http://tools.ietf.org/wg/httpbis/trac/ticket/103</a>&gt;: "Content-*"
     3082         </li>
     3083         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/104">http://tools.ietf.org/wg/httpbis/trac/ticket/104</a>&gt;: "Header type defaulting"
     3084         </li>
     3085         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/112">http://tools.ietf.org/wg/httpbis/trac/ticket/112</a>&gt;: "PUT - 'store under' vs 'store at'"
     3086         </li>
    30753087         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/137">http://tools.ietf.org/wg/httpbis/trac/ticket/137</a>&gt;: "duplicate ABNF for Reason-Phrase"
    30763088         </li>
     3089         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/180">http://tools.ietf.org/wg/httpbis/trac/ticket/180</a>&gt;: "Note special status of Content-* prefix in header registration procedures"
     3090         </li>
    30773091         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/203">http://tools.ietf.org/wg/httpbis/trac/ticket/203</a>&gt;: "Max-Forwards vs extension methods"
    30783092         </li>
    … …  
    30863100         </li>
    30873101         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/225">http://tools.ietf.org/wg/httpbis/trac/ticket/225</a>&gt;: "PUT side effect: invalidation or just stale?"
     3102         </li>
     3103         <li> &lt;<a href="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/267">http://trac.tools.ietf.org/wg/httpbis/trac/ticket/267</a>&gt;: "clarify PUT semantics'"
    30883104         </li>
    30893105         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/275">http://tools.ietf.org/wg/httpbis/trac/ticket/275</a>&gt;: "duplicate ABNF for 'Method'"
    … …  
    32433259                        <li>OPTIONS&nbsp;&nbsp;<a href="#rfc.xref.OPTIONS.1">2.1</a>, <a href="#rfc.iref.m.1"><b>7.2</b></a>, <a href="#rfc.xref.OPTIONS.2">9.5</a>, <a href="#rfc.xref.OPTIONS.3">10.1</a></li>
    32443260                        <li>POST&nbsp;&nbsp;<a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.m.4"><b>7.5</b></a>, <a href="#rfc.xref.POST.2">10.1</a>, <a href="#rfc.xref.POST.3">A</a></li>
    3245                         <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.m.5"><b>7.6</b></a>, <a href="#rfc.xref.PUT.2">10.1</a></li>
     3261                        <li>PUT&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.m.5"><b>7.6</b></a>, <a href="#rfc.xref.PUT.2">10.1</a>, <a href="#rfc.xref.PUT.3">A</a></li>
    32463262                        <li>TRACE&nbsp;&nbsp;<a href="#rfc.xref.TRACE.1">2.1</a>, <a href="#rfc.iref.m.7"><b>7.8</b></a>, <a href="#rfc.xref.TRACE.2">9.5</a>, <a href="#rfc.xref.TRACE.3">10.1</a>, <a href="#rfc.xref.TRACE.4">11.1</a></li>
    32473263                     </ul>
    … …  
    33223338                  </li>
    33233339                  <li>POST method&nbsp;&nbsp;<a href="#rfc.xref.POST.1">2.1</a>, <a href="#rfc.iref.p.1"><b>7.5</b></a>, <a href="#rfc.xref.POST.2">10.1</a>, <a href="#rfc.xref.POST.3">A</a></li>
    3324                   <li>PUT method&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.p.2"><b>7.6</b></a>, <a href="#rfc.xref.PUT.2">10.1</a></li>
     3340                  <li>PUT method&nbsp;&nbsp;<a href="#rfc.xref.PUT.1">2.1</a>, <a href="#rfc.iref.p.2"><b>7.6</b></a>, <a href="#rfc.xref.PUT.2">10.1</a>, <a href="#rfc.xref.PUT.3">A</a></li>
    33253341               </ul>
    33263342            </li>

  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1158 r1160  
    35333533      <organization>Linden Lab</organization>
    35343534    </author>
    3535     <author initials='J.' surname='Snell' fullname='J. Snell'>
    3536       <organization />
    3537     </author>
     3535    <author initials='J.' surname='Snell' fullname='J. Snell' />
    35383536    <date year='2010' month='March' />
    35393537  </front>
    … …  
    35523550  Clarify definition of POST.
    35533551  (<xref target="POST"/>)
     3552</t>
     3553<t>
     3554  Remove requirement to handle all Content-* header fields; ban use of
     3555  Content-Range with PUT.
     3556  (<xref target="PUT"/>)
    35543557</t>
    35553558<t>
    … …  
    41314134    </t>
    41324135    <t>
     4136      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/79"/>:
     4137      "Content-* vs. PUT"
     4138    </t>
     4139    <t>
    41334140      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/88"/>:
    41344141      "205 Bodies"
    41354142    </t>
    41364143    <t>
     4144      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/102"/>:
     4145      "Understanding Content-* on non-PUT requests"
     4146    </t>
     4147    <t>
     4148      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/103"/>:
     4149      "Content-*"
     4150    </t>
     4151    <t>
     4152      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/104"/>:
     4153      "Header type defaulting"
     4154    </t>
     4155    <t>
     4156      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/112"/>:
     4157      "PUT - 'store under' vs 'store at'"
     4158    </t>
     4159    <t>
    41374160      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/137"/>:
    41384161      "duplicate ABNF for Reason-Phrase"
     4162    </t>
     4163    <t>
     4164      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/180"/>:
     4165      "Note special status of Content-* prefix in header registration procedures"
    41394166    </t>
    41404167    <t>
    … …  
    41644191    </t>
    41654192    <t>
     4193      <eref target="http://trac.tools.ietf.org/wg/httpbis/trac/ticket/267"/>:
     4194      "clarify PUT semantics'"
     4195    </t>
     4196    <t>
    41664197      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/275"/>:
    41674198      "duplicate ABNF for 'Method'"
Note: See TracChangeset for help on using the changeset viewer.