mirror of
https://github.com/ipfs/kubo.git
synced 2026-02-22 10:57:42 +08:00
6fe85496f5
Once the server is asked to shut down, we stop accepting new connections, but the 'manners' graceful shutdown will wait for all existing connections closed to close before finishing. For keep-alive connections this will never happen unless the client detects that the server is shutting down through the ipfs API itself, and closes the connection in response. This is a problem e.g. with the webui's connections visualization, which polls the swarm/peers endpoint once a second, and never detects that the API server was shut down. We can mitigate this by telling the server to disable keep-alive, which will add a 'Connection: close' header to the next HTTP response on the connection. A well behaving client should then treat that correspondingly by closing the connection. Unfortunately this doesn't happen immediately in all cases, presumably depending on the keep-alive timeout of the browser that set up the connection, but it's at least a step in the right direction. |
||
|---|---|---|
| .. | ||
| commands | ||
| corehttp | ||
| corenet | ||
| corerepo | ||
| corerouting | ||
| coreunix | ||
| .gitignore | ||
| bootstrap_test.go | ||
| bootstrap.go | ||
| builder.go | ||
| core_test.go | ||
| core.go | ||
| mock.go | ||
| pathresolver.go | ||