Abstract
Add sections about 409 Conflict response status codes to the APP draft. This Pace does not address the response format.
Status
Active. Please direct discussion to the atom-syntax list.
Rationale
Currently, some AtomAPI implementations return status code 400 when they receive a valid Atom representation that conflicts with the state on the server. Status code 400 is reserved for problems arising from
malformed syntax.
Proposal
Atom Publishing Protocol
PostURI
3.1.3 Response The possible status codes from a POST are 201, 303, 400, 401, 404, 409, 410, and 500. 3.1.3.x Status Code 409 The request contained a valid Atom Entry, but it conflicts with state on the server. The response SHOULD contain enough for information for the user to resolve the conflict. [[ more about response body format ]]
EditURI
3.2.x Response to PUT Requests The possible status codes from a PUT are ...409, ... 3.2.x.x Status Code 409 The request contained a valid Atom Entry, but it conflicts with the state of the resource, or other state on the server. For example, a server could signal that client has erred in this manner if it receives a request containing an atom:id element whose value differs from that of the resource found at the requested URI. The response SHOULD contain enough for information for the user to resolve the conflict. [[ more about response body format ]]
Impacts
Atom Publishing Protocol status codes.
