Skip to content

DELETE /invdelete on primary node should probably throw REQUEST_INVALID instead of INVALID_OR_MISSING_PARM #1

@dmolesUC

Description

@dmolesUC

The deleteObjectNode() method on ReplicationServiceHandler throws TException.INVALID_OR_MISSING_PARM if given a primary storage node, which translates to a 500 Internal Server Error.

Since this is a client (caller) error, rather than a problem with the server state, it would probably be more appropriate to return a 400 Bad Request by throwing TException.REQUEST_INVALID.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions