Changeset 180


Ignore:
Timestamp:
Jan 30, 2008, 3:45:07 AM (12 years ago)
Author:
julian.reschke@…
Message:

Resolve #21: clarify that 201 is only required when a new resource is being created at the Request-URI (closes #21)

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

Legend:

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

    r172 r180  
    889889         already existing resource, the enclosed entity <em class="bcp14">SHOULD</em> be considered as a modified version of the one residing on the origin server. If the Request-URI does not point to an existing
    890890         resource, and that URI is capable of being defined as a new resource by the requesting user agent, the origin server can create
    891          the resource with that URI. If a new resource is created, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
     891         the resource with that URI. If a new resource is created at the Request-URI, the origin server <em class="bcp14">MUST</em> inform the user agent via the 201 (Created) response. If an existing resource is modified, either the 200 (OK) or 204 (No
    892892         Content) response codes <em class="bcp14">SHOULD</em> be sent to indicate successful completion of the request. If the resource could not be created or modified with the Request-URI,
    893893         an appropriate error response <em class="bcp14">SHOULD</em> be given that reflects the nature of the problem. The recipient of the entity <em class="bcp14">MUST NOT</em> ignore any Content-* (e.g. Content-Range) headers that it does not understand or implement and <em class="bcp14">MUST</em> return a 501 (Not Implemented) response in such cases.
     
    17151715      <h2 id="rfc.section.B.3"><a href="#rfc.section.B.3">B.3</a>&nbsp;Since draft-ietf-httpbis-p2-semantics-01
    17161716      </h2>
     1717      <p id="rfc.section.B.3.p.1">Closed issues: </p>
     1718      <ul>
     1719         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/21">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/21</a>&gt;: "PUT side effects"
     1720         </li>
     1721      </ul>
    17171722      <h1><a id="rfc.copyright" href="#rfc.copyright">Full Copyright Statement</a></h1>
    17181723      <p>Copyright © The IETF Trust (2008).</p>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r172 r180  
    757757   capable of being defined as a new resource by the requesting user
    758758   agent, the origin server can create the resource with that URI. If a
    759    new resource is created, the origin server &MUST; inform the user agent
     759   new resource is created at the Request-URI, the origin server &MUST;
     760         inform the user agent
    760761   via the 201 (Created) response. If an existing resource is modified,
    761762   either the 200 (OK) or 204 (No Content) response codes &SHOULD; be sent
     
    26282629<section title="Since draft-ietf-httpbis-p2-semantics-01">
    26292630<t>
     2631  Closed issues:
     2632  <list style="symbols">
     2633    <t>
     2634      <eref target="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/21"/>:
     2635      "PUT side effects"
     2636    </t>
     2637  </list>
    26302638</t>
    26312639</section>
Note: See TracChangeset for help on using the changeset viewer.