Thanks for the advice Bryan.
Sadly I tried using go mod download but I'm still seeing the same problem. I'm concerned that it might be something environmental.
I tried again but this time with a different module:
Then on a whim I cleaned the cache again and ran "go get" on this new module:
This time all but two of the downloaded modules contained .info files.
I don't get it.
One thing that I did note was that when I go back to using "go get" on the original module, it
caches a number of modules into the but it only *reports* one:
The only .info file that's downloaded is go\pkg\mod\cache\download\
github.com\jung-kurt\gofpdf\@v\
v1.16.2.infoI'm wondering if that's hinting at something?
I'm not interested in the info files per se. It's just that we're using our own module proxy and some of our developers are using GoLand. When GoLand opens a project it seems to run "go list" on all dependencies and reports an http 404 on any .info files that it can't download. Because some of our dependencies don't have .info files, we get the http 404s.
Aside from that the lack of info files doesn't seem to stop us from using GoLand but all the same I'd rather we fixed the errors.