Change https://golang.org/cl/352113 mentions this issue: http2: reset streams when abandoning request body write

Hm, this is trickier than I thought.

I was mistaken about us removing the stream from ClientConn.streams upon receiving a response with a status >=300. We only remove the stream later, usually when Request.Body is closed.

When Request.Body is closed, we send a RST_STREAM if the server hasn't closed its side of the stream. If the server has closed its side of the stream, we forget the stream and send nothing.

If Request.Body is closed when the server has closed its side of the stream and we have not finished writing the request body, we will abandon the stream in a half-closed state. This is true whether we received a >= 300 status or not, but it is more likely to occur in this case because a 300 response halts the body write.

So a client-initiated stream is left unclosed if:

• There is a request body.
• The body is not fully written when Response.Body is closed.
• The server half-closes the stream before Response.Body is closed.

I haven't found a way to demonstrate this condition with the x/net/http2 server, because our server implementation sends a RST_STREAM after sending any frame which half-closes a stream. (See *serverConn.wroteFrame.)