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

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.