Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Preventing external requests #39253

ghost opened this issue May 26, 2020 · 1 comment

Preventing external requests #39253

ghost opened this issue May 26, 2020 · 1 comment


Copy link

@ghost ghost commented May 26, 2020

What version of Go are you using (go version)?


Does this issue reproduce with the latest release?


What operating system and processor architecture are you using (go env)?

Windows & Mac 64-bit each

What did you do?

tried to set all the environment variables I could think of

What did you expect to see?

To not reach externally

What did you see instead?

To reach only internally

I'm working at a company where we are trying to bring GoLang in. One of the requirements by security is that it cannot reach externally to sites like,, etc. when users request for new modules. Another situation that I've been told to make sure we avoid is users doing just go get and updating to the latest version of go automatically that way. So commands like this:

go get

Should not pull in the module from The request is that it pulls in the resource from an internal repository instance that we have setup.

I've tried to setup the variables GOPROXY, GONOPROXY, and GOPRIVATE, but none are working unless I specifically put the modules in the go.mod file.

In summary, how can I setup go get to only ever point to the internal repository 100% of the time, and return a 404 when a specific module supplied does not exist? Note: we cannot rely on the .gitconfig file since there's never a guarantee that only and are where the resources are pulled from.

Copy link

@andybons andybons commented May 26, 2020

Hi there,

Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.

For asking questions, see:

Please ask the question on one of the above forums.

(Quoted from

@andybons andybons closed this May 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.