Comment 1:

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

Owner changed to @bradfitz.

Status changed to Accepted.

Comment 2:

Looks like Request.Write & transfer.go's WriteBody are fine, and properly return the
error.
Problem seems (at first glance) to be Transport: it writes in one goroutine and sends
the correct error back on a channel (after marking the underlying conn as dead, so it
won't be reused), but meanwhile another goroutine is reading the response, and gets a
valid HTTP response from the server, so we return it.  (And because the server didn't
read the entire request body, it also notes that the connection is to be closed after
the response, since it can't reuse that TCP connection....)
We should also wait to know whether we finished writing the request before we return
success to from the RoundTripper.

Comment 3:

In transfer.go on line 56 if there is an error and n == 0 error is ignored and t.Body is
set to nil.
Attached patch fixes this problem.

Attachments:

1. http_post_bug.patch (1095 bytes)

Comment 4:

Good find. I'll fix it and add a test, unless you want to go through the contribution
process yourself. (We don't do patches on the bug tracker or mailing list).

Comment 5:

I already have a patch and will write some tests tomorrow. I can go through the process .

Comment 6:

This issue was closed by revision 2701dad.

Status changed to Fixed.