Re: [go-nuts] net/http: get does not work

Is any of the following set `HTTPS_PROXY', `HTTP_PROXY' ? The DefaultTransport pays attention to those env vars to decide whether to use a proxy or not. If that's not the case, what is the error that you're getting ? cheers, -js yyq2...@gmail.com writes: > http.Get doesn't work with default tr

[go-nuts]

-- 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. For more options, visit https://groups.google.com/d/optout.

[go-nuts] using go modules replace with old repos

Hi all, Is there a way to use the go module `replace' directive for packages that don't have go.mod yet ? I tried doing that and I get the following error: > go: parsing ../pkg/go.mod: open /path/to/pkg/go.mod: no such file or > directory According to https://github.com/golang/go/issues/24110 it

Re: [go-nuts] Re: Is the go 1.11 godoc tool 'module-aware'?

e same. Great, thanks! > > On Friday, 31 August 2018 02:16:54 UTC+5:30, John Shahid wrote: >> >> >> Agniva De Sarker > writes: >> >> > Also - note that godoc cli mode is going to go away. So "godoc -links=0 >> > -html domain.com/group/project/

[go-nuts] Re: using go modules replace with old repos

Ping. John Shahid writes: > Hi all, > > Is there a way to use the go module `replace' directive for packages > that don't have go.mod yet ? I tried doing that and I get the following > error: > >> go: parsing ../pkg/go.mod: open /path/to/pkg/go.mod: no such

[go-nuts] SSH Server maximum number of attempts

Hi all, I was wondering if there is a way to limit the maximum number of failed authentication attempts in an ssh server. looks like the serverAuthenticate method won’t exit unless the authenticatio

[go-nuts] go1.8 and json.NewDecoder(resp.Body)

Hi all, Some background, we (CloudFoundry) noticed some weird behavior after upgrading from go1.7.4 to go1.8.1. An http client that was polling 260 servers started showing more timeouts after the upgrade. After investigating the issue we realized that the following pattern combined with tls connec