the client is probably using a series of range request for large downloads. http.FileServer supports range queries and returns 206 partial content. that means after srv.Shutdown is called, it will only wait for the active range requests and close the connection when it changes into idle state. the client cannot open a new connection because the listener is already closed.

@amkgo, do you have a repro?

@mb0, that is true, but do you have any evidence that this is OP's problem?

@bradfitz no sorry. i tried to reproduce and my assumption was wrong.
the problem is something else and even more obvious in hindsight.

the playground example will return from ListenAndServe and thus exit as soon as the listening socket it closed. if the example does not exit the program right away Shutdown behavior works as expected.

The example code https://play.golang.org/p/LdXUYyzDxY by @mb0 works great.

I think we can close this issue. Thank you all!

I think lots of gophers may encounter this problem and don't aware of it. Because I got the code from the web and the authors maybe Go experts(Speakers). Can you please add some comments to server.Shutdown() to explain how to properly use it. The main function should wait for Shutdown() to finish to make it function properly. Or at least a link to this issue.

Thanks

Sure, file a new bug that's just about documenting Server.Shutdown more.

Title: "net/http: add example for Server.Shutdown"

The example will not reference this issue (we don't link to bugs or commits in Go docs) but your new documentation bug can and should reference this bug.