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: Response.Write has bogus Connection header after auto-ungzipped Content-Length response #15367

Closed
sbadame opened this issue Apr 19, 2016 · 1 comment

Comments

@sbadame
Copy link

@sbadame sbadame commented Apr 19, 2016

Please answer these questions before submitting your issue. Thanks!

  1. What version of Go are you using (go version)?
    go version go1.6 linux/amd64
  2. What did you do?
    I can't use the playground because this requires localhost, which the playground doesn't support.
    https://gist.github.com/sbadame/6672153feb5a5430a0129d40b263d8e9
  3. What did you expect to see?
    Either "Connection: close" or "Connection:keep-alive" and a content length. Or maybe chunk encoding?
  4. What did you see instead?

http.Transport.RoundTrip response: HTTP/1.1 200 OK
Connection: close
Connection: keep-alive
Keep-Alive: timeout=7200

http.DefaultClient.Do Response: HTTP/1.1 200 OK
Connection: close
Connection: keep-alive
Keep-Alive: timeout=7200

@bradfitz

This comment has been minimized.

Copy link
Contributor

@bradfitz bradfitz commented Apr 19, 2016

Dup of #15366

@bradfitz bradfitz closed this Apr 19, 2016
@golang golang locked and limited conversation to collaborators Apr 19, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.