-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
http2: properly discard data received after request/response body is …
…closed A server handler can close an inbound Request.Body to indicate that it is not interested in the remainder of the request body. Equivalently, a client can close a Response.Body indicate that it is not interesed in the remainder of the response body. In both cases, if we receive DATA frames from the peer for the stream, we should return connection-level flow control credit for the discarded data. We do not return stream-level flow control, since we don't want to unblock further sends of data that we're just going to discard. Closing either a Response.Body or an inbound Request.Body results in a pipe.BreakWithError. Reads from a broken pipe fail immediately. Previously, writes to a broken pipe would succeed, discarding the written data and incrementing the pipe's unread count. Silently discarding data written to a broken pipe results in both the Transport and Server failing to detect the condition where data has been discarded. Change pipes to return an error when writing to a broken pipe. Change transportResponseBody.Close to break the response body before returning flow control credit for unread data in the pipe, avoiding a race condition where data is added to the pipe in between the return of flow control credit and the pipe breaking. Change the Server to treat an error writing to the inbound request body as an expected condition (since this only happens when a handler closes the request body), returning connection-level flow control credit for the discarded data. Fixes golang/go#57578 Change-Id: I1ed4ea9865818f9c7d7eb4500edfd7556e3cbcbf Reviewed-on: https://go-review.googlesource.com/c/net/+/475135 Run-TryBot: Damien Neil <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Roland Shoemaker <[email protected]>
- Loading branch information
Showing
5 changed files
with
39 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters