REST: Wrong error handling when deleting multiple components #851
Comments
nam-np
added a commit
to nam-np/sw360
that referenced
this issue
May 28, 2021
…sw360#851 Signed-off-by: Nguyen Phuong Nam <nam1.nguyenphuong@toshiba.co.jp>
1 task
mcjaeger
added a commit
that referenced
this issue
May 30, 2021
…iple-component fix REST: Wrong error handling when deleting multiple components #851 tested-by:kumar.ravindra@siemens.com review-by:kumar.ravindra@siemens.com
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The DELETE method on the components endpoint accepts multiple IDs for the components to be deleted. It returns a multi-status response, so that the caller can find out, which components could be deleted successfully. The current implementation, however, sends a 500 error response as soon as an error occurs when deleting components.
To reproduce, send a request to delete multiple components passing in some existing and at least one non-existing component IDs, e.g.:
DELETE /components/existingID1,existingID2,invalidID,existingID3Response is a 500 error result. The existing components listed before the invalid ID have been deleted.
Expected result is a multi-status response containing success responses for the existing components and error responses for the invalid IDs.
The text was updated successfully, but these errors were encountered: