Comment 1:

Labels changed: added repo-main, release-go1.5.

Comment 2 by Benny.TPNG:

After further investigation, it seems the problem exists for non chunked content as well.
The problem only occurs when the go server is behind the IIS reverse proxy.
Updated repro is attached.
Sample Header (IIS reverse proxy):
HTTP/1.1 200 OK
Date: Wed, 19 Nov 2014 03:02:24 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Type: application/json; charset=utf-8
Date: Wed, 19 Nov 2014 03:02:24 GMT
Content-Length: 85
Via: 1.1 203.80.2.39 (IIRF v2.1)
Sample Header (local):
HTTP/1.1 200 OK
Content-Length: 90
Content-Type: application/json; charset=utf-8
Date: Wed, 19 Nov 2014 03:03:35 GMT

Attachments:

1. main.go (453 bytes)

Comment 3:

The server is misbehaving.
It's replying HTTP/1.1 200 OK (which implies it supports keep-alive connections in the
absence of any indicator to the contrary), and it doesn't have a "Connection: close"
header, but then it just closes the connection immediately.
The Go code meanwhile assumes it's conforming and tries to send another request on that
connection but then it receives the EOF from the peer closing the first request.
Workaround: disable KeepAlives on the http.Transport you're using.
This is a dup of issue #4677

Status changed to Duplicate.

Merged into issue #4677.