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

Changeset 577


Ignore:
Timestamp:
2009-05-07 01:47:47 (6 years ago)
Author:
julian.reschke@gmx.de
Message:

PUT and POST requests are not special with respect to Content-Location (related to #80)

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p3-payload.html

    r573 r577  
    478478         <tr> 
    479479            <td class="header left"></td> 
    480             <td class="header right">May 1, 2009</td> 
     480            <td class="header right">May 6, 2009</td> 
    481481         </tr> 
    482482      </table> 
     
    12561256      </p> 
    12571257      <p id="rfc.section.5.7.p.6">If the Content-Location is a relative URI, the relative URI is interpreted relative to the request-target.</p> 
    1258       <p id="rfc.section.5.7.p.7">The meaning of the Content-Location header in PUT or POST requests is undefined; servers are free to ignore it in those cases.</p> 
     1258      <p id="rfc.section.5.7.p.7">The meaning of the Content-Location header in requests is undefined; servers are free to ignore it in those cases.</p> 
    12591259      <div id="rfc.iref.c.5"></div> 
    12601260      <div id="rfc.iref.h.8"></div> 
     
    19231923      </ul> 
    19241924      <h2 id="rfc.section.E.8"><a href="#rfc.section.E.8">E.8</a>&nbsp;<a id="changes.since.06" href="#changes.since.06">Since draft-ietf-httpbis-p3-payload-06</a></h2> 
     1925      <p id="rfc.section.E.8.p.1">Closed issues: </p> 
     1926      <ul> 
     1927         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/80">http://tools.ietf.org/wg/httpbis/trac/ticket/80</a>&gt;: "Content-Location isn't special" 
     1928         </li> 
     1929      </ul> 
    19251930      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 
    19261931      <p class="noprint"><a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.D">D</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.I">I</a> <a href="#rfc.index.L">L</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.U">U</a>  
  • draft-ietf-httpbis/latest/p3-payload.xml

    r573 r577  
    14301430</t> 
    14311431<t> 
    1432    The meaning of the Content-Location header in PUT or POST requests is 
     1432   The meaning of the Content-Location header in requests is 
    14331433   undefined; servers are free to ignore it in those cases. 
    14341434</t> 
     
    29542954<section title="Since draft-ietf-httpbis-p3-payload-06" anchor="changes.since.06"> 
    29552955<t> 
     2956  Closed issues: 
     2957  <list style="symbols">  
     2958    <t> 
     2959      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/80"/>: 
     2960      "Content-Location isn't special" 
     2961    </t> 
     2962  </list> 
    29562963</t> 
    29572964</section> 
Note: See TracChangeset for help on using the changeset viewer.