Allow setting SkipTLSVerify Option value #448
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
…n TokenAllowed and TokenValid Signed-off-by: Mohamedh Fazal <[email protected]>
Signed-off-by: Mohamedh Fazal <[email protected]>
Signed-off-by: Mohamedh Fazal <[email protected]>
This allows one to set value from another source such as a configuration file, which is not known ahead of time. Variadic parameters are there for backwards compatibility reasons, so that `SkipTLSVerify()` alone still works.
|
Thanks! |
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.
Allow setting the value of TLS verification option to given value. This allows one to set value from another source such as a configuration file, which is not known ahead of time.
Variadic parameters are there for backwards compatibility reasons, so that
SkipTLSVerify()alone still works.