Changeset 2061 for draft-ietf-httpbis
- Timestamp:
- 29/12/12 02:18:05 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2060 r2061 2644 2644 <h3 id="rfc.section.6.5.8"><a href="#rfc.section.6.5.8">6.5.8</a> <a id="status.409" href="#status.409">409 Conflict</a></h3> 2645 2645 <p id="rfc.section.6.5.8.p.1">The <dfn>409 (Conflict)</dfn> status code indicates that the request could not be completed due to a conflict with the current state of the resource. This 2646 code is only reasonable in situations where it is expected that the user might be able to resolve the conflict and resubmit 2647 the request. The server <em class="bcp14">SHOULD</em> generate a payload that includes enough information for the user to recognize the source of the conflict. Ideally, the response 2648 would include enough information for the user or user agent to fix the problem; however, that might not be possible and is 2649 not required. 2646 code is used in situations where the user might be able to resolve the conflict and resubmit the request. The server <em class="bcp14">SHOULD</em> generate a payload that includes enough information for a user to recognize the source of the conflict. 2650 2647 </p> 2651 2648 <p id="rfc.section.6.5.8.p.2">Conflicts are most likely to occur in response to a PUT request. For example, if versioning were being used and the representation 2652 being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the server might2653 use the409 response to indicate that it can't complete the request. In this case, the response representation would likely2654 contain a list of the differences between the two versions.2649 being PUT included changes to a resource which conflict with those made by an earlier (third-party) request, the origin server 2650 might use a 409 response to indicate that it can't complete the request. In this case, the response representation would likely 2651 contain information useful for merging the differences based on the revision history. 2655 2652 </p> 2656 2653 <div id="rfc.iref.74"></div> -
draft-ietf-httpbis/latest/p2-semantics.xml
r2060 r2061 3219 3219 The <x:dfn>409 (Conflict)</x:dfn> status code indicates that the request 3220 3220 could not be completed due to a conflict with the current state of the 3221 resource. This code is only reasonable in situations where it is expected 3222 that the user might be able to resolve the conflict and resubmit the 3223 request. The server &SHOULD; generate a payload that includes enough 3224 information for the user to recognize the source of the conflict. Ideally, 3225 the response would include enough information for the user or user agent to 3226 fix the problem; however, that might not be possible and is not required. 3221 resource. This code is used in situations where the user might be able to 3222 resolve the conflict and resubmit the request. The server &SHOULD; generate 3223 a payload that includes enough information for a user to recognize the 3224 source of the conflict. 3227 3225 </t> 3228 3226 <t> … … 3230 3228 example, if versioning were being used and the representation being PUT 3231 3229 included changes to a resource which conflict with those made by an 3232 earlier (third-party) request, the server might use the409 response3233 to indicate that it can't complete the request. In this case, the 3234 re sponse representation would likely contain a list of the differences3235 between the two versions.3230 earlier (third-party) request, the origin server might use a 409 response 3231 to indicate that it can't complete the request. In this case, the response 3232 representation would likely contain information useful for merging the 3233 differences based on the revision history. 3236 3234 </t> 3237 3235 </section>
Note: See TracChangeset
for help on using the changeset viewer.