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

Connection header in request is ignored by the http server #3540

Closed
niemeyer opened this issue Apr 16, 2012 · 4 comments
Closed

Connection header in request is ignored by the http server #3540

niemeyer opened this issue Apr 16, 2012 · 4 comments
Milestone

Comments

@niemeyer
Copy link
Contributor

The http package respects the Connection: close header delivered to
the client, but ignores the respective client request.

According to the RFC, this is supposed to be respected by the server:

"""
An HTTP/1.1 server MAY assume that a HTTP/1.1 client intends to
maintain a persistent connection unless a Connection header including
the connection-token "close" was sent in the request.
"""
@niemeyer
Copy link
Contributor Author

Comment 1:

Being handled in http://golang.org/cl/5996044/

@niemeyer
Copy link
Contributor Author

Comment 2:

This issue was closed by revision cc5cbee.

Status changed to Fixed.

@niemeyer
Copy link
Contributor Author

Comment 3:

UnFixed by revert. Windows 64 is unhappy with the fix for apparently unrelated reasons.

Status changed to Started.

@rsc
Copy link
Contributor

rsc commented May 22, 2012

Comment 4:

This issue was closed by revision 3d03ec8.

Status changed to Fixed.

@rsc rsc added this to the Go1.1 milestone Apr 14, 2015
@rsc rsc removed the go1.1 label Apr 14, 2015
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

3 participants