Repository navigation
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #31.
Lets a 101 to an HTTP/1.1 request carrying
upgrade, or a 2xx to a CONNECT request on any version, switch the exchange to a tunnel. The host never hands over the connection: the newNsgiRequest::read_tunneldelivers the bytes the client sends after the request message, and the switching response'sread_bodysupplies the bytes sent back. Each direction closes on its own, and the host defersnsgi_free_responseuntilread_tunnelreports a terminal status.NsgiRequest::protocolcarries the:protocolof an extended CONNECT request.The request body keeps the request's own content, so an application that reads the whole body before responding does not block on a tunnel.
NsgiInformrejects a 101, and the host answers 500 in place of a 101 that does not switch.