Backwards incompatible! HostClient can't switch between protocols #800
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.
HostClient
connects to its host though either HTTP or HTTPS. It should never switch between protocols. This breaks theHostClient
maps insideClient
. There are two maps there:m
is for http HostClientsms
is for https HostClientsUpdating a http
HostClient
to https, while it is still inside map m will make all future requests to the given http host go to https. Since servers can serve different content on both ports this can break things.Thats why from now on
HostClient
will throw and error when it is used outsideClient
and tries to follow a redirect to a different protocol.