BasicServer handle_delete() returns 500 for a nonexistent entity in an existing table

[jleung51]

Migrated from GitLab.

handle_delete() returns code 500 (Internal server error) for an entity which does not exist in an existing table. This is the status code from Azure, returned directly by the function.

Is this expected behaviour or should we be checking for it in handle_delete() before attempting to delete the entity with Azure? It would be great if we could set this to NotFound.

Discussion from GitLab:

Joshua Wu @jyw27 23 days ago

Not found works, 410 indicates a resource is gone so that may also be a good substitute.

Jeffrey Leung @JYL52 23 days ago

Hm it looks to me like 410 is for something permanently removed:

This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future.

From Wikipedia

So it might not be as appropriate as 404 in my opinion.