-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The H2C upgrading stream of a connection closes the stream prematurel…
…y when the response is sent. The HTTP/2 RFC specs mandates the following items - Requests that contain a payload body MUST be sent in their entirety before the client can send HTTP/2 frames. - The HTTP/1.1 request that is sent prior to upgrade is assigned a stream identifier of 1 with default priority values. Stream 1 is implicitly "half-closed" from the client toward the server, since the request is completed as an HTTP/1.1 request. - From the Netty perspective, the stream is seen as half closed remote, since the stream cannot receive anymore frames from the HTTP/2 upgraded channel. - From the Vert.x perspective, the stream is seen as open since the header frame is processed but the stream is not ended e.g the stream can contain a body and we expect content messages. When an application ends the HTTP response, the stream transitions to the close state while the stream can still process content messages. The server should handle specifically the H2C upgrading stream to continue processing HTTP messages even though the stream is considered closed from the Netty perspective.
- Loading branch information
Showing
18 changed files
with
173 additions
and
163 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
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
Oops, something went wrong.