303 status on ResourceExistsException instead of 409?

Open namedgraph opened this issue 4 years ago • 0 comments

When POST requests attempts to construct a resource that already exists, we throw ResourceExistsException which currently maps to a 409 Conflict error response.

HTTP spec seems to say that 303 See Other can be used: https://tools.ietf.org/html/rfc7231#section-4.3.3

Mar 09 '21 21:03 namedgraph