Re: [go-nuts] net/http: Server closeIdleConns does not close StateNew connections

2017-11-14 Thread Peter Mogensen
On 2017-11-13 21:16, André Carvalho wrote: > I also ran into this issue recently. I think this is a dup > of https://github.com/golang/go/issues/21204. This issue can be > mitigated if you set some reasonable ReadTimeout on the http.Server, > which causes the http.StateNew connection to timeout (

Re: [go-nuts] net/http: Server closeIdleConns does not close StateNew connections

2017-11-13 Thread André Carvalho
I also ran into this issue recently. I think this is a dup of https://github.com/golang/go/issues/21204. This issue can be mitigated if you set some reasonable ReadTimeout on the http.Server, which causes the http.StateNew connection to timeout (a connection stays in this state until something is r

[go-nuts] net/http: Server closeIdleConns does not close StateNew connections

2017-11-13 Thread Kevin Burge
I recently ran into an issue where Chrome was opening additional connections to my http Server. When I went close to the Go app, instead of just immediately closing after calling server.Shutdown, in lingered until the server was forcefully shutdown by my shutdown context. The issue is that clo