Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-19009

API returning http 500 errors user requests bad path

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Resolution: Unresolved
    • Affects Version/s: 6.9.1
    • Fix Version/s: None
    • Component/s: REST API, Web REST API
    • Labels:
    • Severity:
      Medium
    • Requirement Status:

      UNCOVERED

      Description

      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.

       

      Example1:

      Request: https://<artifactory_domain>/artifactory//path/to/artifact.json

      Response: 500, "Repo key cannot be empty..."

      Expected: 400, "Repo key cannot be empty..."

       

      Example2:

      Request: https://<artifactory_domain>/artifactory/repo/path/to

      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.

        Attachments

          Forms

            Activity

                People

                Assignee:
                Unassigned
                Reporter:
                greg.mattson Greg Mattson
                Votes:
                3 Vote for this issue
                Watchers:
                1 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    PagerDuty