qwzhou89 commented on issue #9823: URL: https://github.com/apache/apisix/issues/9823#issuecomment-1646546624
> sorry I not very unstander "although upstream is not supported, I can still use mtls. " > Sorry, I misspoke. What I meant to say was According to the https://apisix.apache.org/zh/docs/apisix/next/admin-api/#route-request-body-parameters There is no way to set client_cert and client_key inside the upstream in the route. If we use upstream_id then according to https://apisix.apache.org/zh/docs/apisix/next/admin-api/#upstream-body-request-methods I can set tls.client_cert, tls.client_key inside upstream object. So, I am not configuring stream_routes like the https://apisix.apache.org/zh/docs/apisix/next/stream-proxy/#%E4%BB%A3%E7%90%86%E5%88%B0-tls-over-tcp-%E4%B8%8A%E6%B8%B8 configured an upstream object , but rather configured the upstream_id > can you share more detail ? > > ``` > client <- mtls -> apisix <-mtls-> upstream (tcp) > ``` > In stream-proxy ，Inside `apisix <-mtls-> upstream,` how do I configure mtls on the apisix side? -- 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]
