On Tuesday, April 18, 2017 at 8:19:06 AM UTC-7, Peter Mogensen wrote:
>
> > and even if one was
> > still open, I'm making a new http.Client object, too!
>
> Yes. But you don't make a new Transport.
> Both your clients use DefaultTransport - which has the connection pool.
>
> /Peter
>
>
Bingo.
On Tuesday, April 18, 2017 at 5:51:40 AM UTC-7, Yuwei Ba wrote:
>
> Disabling the HTTP connection keep-alive may help for this situation by
> calling: `srv.SetKeepAlivesEnabled(false)` and get the expected output
> **sometimes**
>
> $ go run a.go
> In handler wrapper, f = 0xc4200111a0
> 1
> In ha
On Monday, April 17, 2017 at 10:30:43 PM UTC-7, Peter Mogensen wrote:
>
> However... If you call net/http.Server.Close() between the two calls you
> get the expected result... which indicates you might be struggling with
> the client side connection pool still having a keepalive HTTP connection
Hello golang-nuts!
I have some code that creates a short-lived HTTP server, and I'm trying to
write tests for it. I'm hitting a case where HTTP handlers seem to stick
around even though I'm creating a brand new `http.ServeMux`, `http.Server`,
and `net.Listener` objects. How do I get rid of ol
