When a user requests a bad path from artifactory such as a path with no Repository Key or a path to a folder instead of a file the request results in an http 500 error suggesting that there is an error on the server. These should be returning http 400 errors telling the user and system administrators that it was a bad request.
Response: 500, "Repo key cannot be empty..."
Expected: 400, "Repo key cannot be empty..."
Response: 500, "Expected a file but found a folder..."
Expected: 400, "Expected a file but found a folder..."
Correctly classifying these as bad requests from a user allows system administrators to be able to correctly investigate and respond to server problems when there are 500 errors.