Allow HTTPS endpoints in client - #338
Merged
Merged
Conversation
chen-anders
force-pushed
the
anders/support-https-endpoints
branch
from
October 25, 2021 05:54
dbf5b1c to
6178848
Compare
miry
approved these changes
Oct 25, 2021
Contributor
|
@chen-anders Pls update Changelog.md as well. |
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
2 participants
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.
There may be times when toxiproxy is behind an TLS-terminated endpoint; we shouldn't stop someone from setting such an endpoint when initializing a new client.