Hi all,

I am a little bit confused at what is the expected behaviour for 
GOPROXY="https://proxy.golang.org,direct";. 

On my system when using Go 1.13 beta 1, go env reports that 
GOPROXY="https://proxy.golang.org,direct";. When `go build .` tries to 
access a package hosted on github.com, proxy.golang.org gets involved as 
the proxy. Thanks to the GFW in China, proxy.golang.org is not accessible 
from my machine and I ended up with a timeout error. My question is what 
does that "direct" mean in the GOPROXY setting? I was assuming that direct 
access to where the package is hosted is going to be tried once the 
specified proxy is not accessible, but it seems to me that it doesn't work 
in that way. 

`go help goproxy` doesn't really help on my question above, can someone 
here kindly shed some light on the expected 
GOPROXY="https://proxy.golang.org,direct"; behaviour?  



Cheers,


Lei




-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/a2789e4a-f9b9-46fc-96b1-c22c8886dfd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to