Skip to content

/go

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

net/http: make Server.SetKeepAlivesEnabled(false) drop currently-open connections #9478

Closed
bradfitz opened this issue Dec 30, 2014 · 9 comments

Comments

Assignees
No one assigned
Labels
FrozenDueToAge NeedsFix
Projects
None yet
Milestone
  Go1.8Maybe
5 participants
@bradfitz @rsc @tpng @gopherbot @quentinmit
@bradfitz
Copy link
Member

commented Dec 30, 2014

When adjusting the firewall configuration on a GCE instance today, I was confused that I could toggle my new firewall rule and see the changes immediately affect my ability to telnet to the http server, but my browser continued to work fine, regardless of the firewall setting.

What I realized (too slowly) was happening was that once the keep-alive connection was open, the firewall permitted it forever, as designed and documented.

It would be nice of the google.golang.org/cloud/compute/metadata package or similar could listen for metadata changes (the GCE metadata service supports long polling on changes) to see when the firewall or tags change, and then call Server.SetKeepAlivesEnabled(false) to drop existing connections and force them to (try) to reconnect.

Currently Server.SetKeepAlivesEnabled only affects future connections and not active idle ones.

@bradfitz bradfitz added the featurerequest label Dec 30, 2014

@bradfitz bradfitz added this to the Go1.5Maybe milestone Dec 30, 2014

@bradfitz bradfitz added repo-main and removed featurerequest labels Dec 30, 2014

@rsc rsc removed repo-main labels Apr 14, 2015

@rsc

This comment has been minimized.

Sign in to view
Copy link
Contributor

commented Jun 29, 2015

Too late for Go 1.5.

@rsc rsc modified the milestones: Unplanned, Go1.5Maybe Jun 29, 2015

@jbardin jbardin referenced this issue Mar 23, 2016

Closed

net/http: Keepalive connections are not terminated when server returns. #14927

@bradfitz

This comment has been minimized.

Sign in to view
Copy link
Member Author

commented Mar 23, 2016

Related: #4674

@tpng tpng referenced this issue May 9, 2016

Closed

Change in proxy config not reflected by in-process restart (http2 keep-alive connection not closed) #809

@tpng

This comment has been minimized.

Sign in to view
Copy link

commented May 9, 2016

Any plan on fixing this?
Default support for http2 is included in Go 1.6, and browsers supporting http2 are reusing single connection by design.
Server.SetKeepAlivesEnabled(false) only affecting new connection means there are currently no way to close the only connection opened by browsers gracefully.
We can close the connection using the Server.ConnState hook, but it causes Chrome to display a error page before opening a new connection.
And I don't think we have enough info to send a GOAWAY frame inside the Server.ConnState hook.

@bradfitz bradfitz modified the milestones: Go1.8Maybe, Unplanned May 9, 2016

@tpng tpng referenced this issue Jun 7, 2016

Merged

Close idle connections after graceful shutdown timeout #870

@FiloSottile FiloSottile referenced this issue Aug 3, 2016

Closed

net/http: add built-in graceful shutdown support to Server #4674

@quentinmit quentinmit added the NeedsFix label Oct 10, 2016

@bradfitz bradfitz referenced this issue Oct 17, 2016

Closed

x/net/http2: support graceful shutdown of http2 server handlers #15386

@rsc

This comment has been minimized.

Sign in to view
Copy link
Contributor

commented Oct 20, 2016

@bradfitz, too late for Go 1.8, yes?
@bradfitz

This comment has been minimized.

Sign in to view
Copy link
Member Author

commented Oct 25, 2016

A couple of the other issues might make this easy. I'll close this at the end of the week if it doesn't happen, but let's keep it open until then.
@gopherbot

This comment has been minimized.

Sign in to view
Copy link

commented Oct 30, 2016

CL https://golang.org/cl/32329 mentions this issue.

@bradfitz bradfitz referenced this issue Nov 1, 2016

Closed

x/net/http2: if http1 Server's keep-alives are disabled, only do one request #17717

@gopherbot gopherbot closed this in 53fc330 Nov 1, 2016

@bradfitz bradfitz reopened this Nov 3, 2016

@bradfitz

This comment has been minimized.

Sign in to view
Copy link
Member Author

commented Nov 3, 2016

I'm going to reopen this. The solution I have now is okay, but it's not great. It closes all currently-idle conns, but it should mark all conns for death as soon as they become idle. (For both http1 and http2).

I was thinking this before, but the flaky #17754 really drove it home.
@gopherbot

This comment has been minimized.

Sign in to view
Copy link

commented Nov 3, 2016

CL https://golang.org/cl/32587 mentions this issue.

gopherbot pushed a commit that referenced this issue Nov 3, 2016

@bradfitz
net/http: deflake TestServerSetKeepAlivesEnabledClosesConns 
Fixes #17754
Updates #9478 (details in here)

Change-Id: Iae2c1ca05a18ed266b53b2594c22fc57fab33c5e
Reviewed-on: https://go-review.googlesource.com/32587
Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Ian Lance Taylor <iant@golang.org>
be7c50a
@gopherbot

This comment has been minimized.

Sign in to view
Copy link

commented Nov 11, 2016

CL https://golang.org/cl/33141 mentions this issue.

@gopherbot gopherbot closed this in 9f9d834 Nov 11, 2016

@golang golang locked and limited conversation to collaborators Nov 11, 2017

@gopherbot gopherbot added the FrozenDueToAge label Nov 11, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.