Support https mutil certs #292
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
Codecov Report
@@ Coverage Diff @@
## develop #292 +/- ##
===========================================
- Coverage 33.99% 33.95% -0.05%
===========================================
Files 61 61
Lines 3159 3163 +4
===========================================
Hits 1074 1074
- Misses 1973 1977 +4
Partials 112 112
Continue to review full report at Codecov.
|
ztelur
reviewed
Nov 6, 2021
|
Resolve conflicts then LGTM |
mark4z
approved these changes
Nov 12, 2021
ztelur
approved these changes
Nov 19, 2021
added 4 commits
November 20, 2021 10:27
# Conflicts: # go.mod
bobtthp
pushed a commit
to bobtthp/dubbo-go-pixiu
that referenced
this pull request
Dec 12, 2022
Support https mutil certs
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.
What this PR does:
Support HTTPS multiple certificates.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: