Add HTTPClientResponse.switchProtocol() #945
Merged
Conversation
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
|
Maybe |
Since the response does not have access to the request headers, the expected protocol must be supplied as a parameter. Signed-off-by: Luca Niccoli <[email protected]>
lultimouomo
force-pushed
the
upgradeConnection
branch
from
b6be76f to
77dcff0
Compare
lultimouomo
changed the title
s-ludwig
added a commit
that referenced
this pull request
May 1, 2015
Add HTTPClientResponse.switchProtocol()
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.
Replaces #929 which I accidentally opened on my master branch.
Since the response does not have access to the request headers,
the expected protocol must be supplied as a parameter.
This is needed, for instance, to create client-side websockets.