From 89f5098048940c50f3c8e0fc893d8201fc824008 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E7=90=9A=E8=87=B4=E8=BF=9C=20/=20Zhiyuan=20Ju?= Date: Fri, 24 Mar 2023 14:03:26 +0800 Subject: [PATCH] docs: fix 404 link --- docs/en/latest/mtls.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/latest/mtls.md b/docs/en/latest/mtls.md index eae5a17fe615..1a1180a0978f 100644 --- a/docs/en/latest/mtls.md +++ b/docs/en/latest/mtls.md @@ -163,7 +163,7 @@ Sometimes the upstream requires mTLS. In this situation, the APISIX acts as the When configuring `upstreams`, we could use parameter `tls.client_cert` and `tls.client_key` to configure the client certificate APISIX used to communicate with upstreams. Please refer to [Admin API](./admin-api.md#upstream) for details. -This feature requires APISIX to run on [APISIX-Base](./FAQ/#how-do-i-build-the-apisix-base-environment). +This feature requires APISIX to run on [APISIX-Base](./FAQ.md#how-do-i-build-the-apisix-base-environment). Here is a similar Python script to patch a existed upstream with mTLS (changes admin API url if needed):