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

Artifactory throws 500 error instead of 404 for non-existing modules causing go build to fail instead of moving on to next proxy in list

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Done
    • Priority: 4 - Normal
    • Resolution: Done
    • Affects Version/s: 7.6.2
    • Fix Version/s: 7.8.1
    • Component/s: None
    • Labels:

      Description

      Problem description: Artifactory throws 500 error instead of 404 for non-existing modules causing go build to fail instead of moving on to next proxy in list

       

      What is the expected behavior?

      Go supports multiple values for GOPROXY since 1.13. When resolving a module, if a proxy in the list returns a 404, go client moves on to try the next proxy in the list. When Artifactory does not contain a module being searched, a 404 is returned for the @v/list, but a 500 is thrown for the zip url. This causes go build to fail instead of moving on to the next value in list.

        Attachments

          Activity

            People

            Assignee:
            barakh Barak Hacham
            Reporter:
            omerh Omer Haglili
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Sync Status

                Connection: RTFACT Sync
                RTMID-23024 -
                SYNCHRONIZED
                • Last Sync Date: