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 closeIdleConns called by Shutdown does not close connections in the StateNew state. I read somewhere else that this connection state is extremely rare, but, my Chrome does this with my app. Even closing the tab does not close these extra connections. The only way to terminate the connection is to use Chrome's internal connection management or close the browse.
But, the point is, why wouldn't the server just shutdown (via Shutdown) if all the connections are either StateIdle or StateNew (idle but never used)? I realize the Server code is expecting StateNew connections to become StateActive, but... in Chrome's case, it didn't. https://github.com/golang/go/issues/22682 https://play.golang.org/p/dP4vQZkKdx Kevin -- 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.
