Skip to content

303 status on ResourceExistsException instead of 409? #28

Open
@namedgraph

Description

@namedgraph

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions