tzssangglass opened a new pull request #6468:
URL: https://github.com/apache/apisix/pull/6468


   Closes #6410
   
   Signed-off-by: tzssangglass <[email protected]>
   
   ### What this PR does / why we need it:
   <!--- Why is this change required? What problem does it solve? -->
   <!--- If it fixes an open issue, please link to the issue here. -->
   
   ### Pre-submission checklist:
   
   <!--
   Please follow the PR manners:
   1. Use Draft if the PR is not ready to be reviewed
   2. Test is required for the feat/fix PR, unless you have a good reason
   3. Doc is required for the feat PR
   4. Use a new commit to resolve review instead of `push -f`
   5. If you need to resolve merge conflicts after the PR is reviewed, please 
merge master but do not rebase
   6. Use "request review" to notify the reviewer once you have resolved the 
review
   7. Only reviewer can click "Resolve conversation" to mark the reviewer's 
review resolved
   -->
   
   * [x] Did you explain what problem does this PR solve? Or what new features 
have been added?
   * [ ] Have you added corresponding test cases?
   * [ ] Have you modified the corresponding document?
   * [ ] Is this PR backward compatible? **If it is not backward compatible, 
please discuss on the [mailing 
list](https://github.com/apache/apisix/tree/master#community) first**
   
   I want to add test cases to prove 
   
   1. the upstream uses self-signed certificate, which is issued by the CA 
certificate set by `proxy_ssl_trusted_certificate`.
   2. when APISIX proxy to upstream, the self-signed certificate is verified 
successfully after `proxy_ssl_trusted_certificate` is turned on, and no error 
like `18: self signed certificate` appears
   
   I need some suggestions.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to