Skip to content
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: client connection close request not echoed in response headers #3663

Closed
bradfitz opened this issue May 22, 2012 · 2 comments
Closed

Comments

@bradfitz
Copy link
Contributor

The fix for issue #3540 has a bug:

Even though the client can now request "Connection: close" and the server now
closes the TCP connection, it doesn't announce that it's doing so in the response
headers.
@bradfitz
Copy link
Contributor Author

Comment 1:

Labels changed: removed priority-triage.

@bradfitz
Copy link
Contributor Author

Comment 2:

This issue was closed by revision e4ed949.

Status changed to Fixed.

@bradfitz bradfitz added the fixed label May 23, 2012
@bradfitz bradfitz self-assigned this May 23, 2012
bradfitz added a commit that referenced this issue May 11, 2015
…client connections

««« backport 4c333000f50b
net/http: fix response Connection: close, close client connections

Fixes #3663
Updates #3540 (fixes it more)
Updates #1967 (fixes it more, re-enables a test)

R=golang-dev, n13m3y3r
CC=golang-dev
https://golang.org/cl/6213064

»»»
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants