From f8648db29cd1ebbbf00a0e9d87cfa83f2d7c171e Mon Sep 17 00:00:00 2001 From: shellvon Date: Fri, 25 Apr 2025 18:03:21 +0800 Subject: [PATCH] =?UTF-8?q?docs(fix):=20fix=20broken=20upstream=20certific?= =?UTF-8?q?ate=20sniffing=20link=20in=20how-mitmp=E2=80=A6=20(#7672)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit docs(fix): fix broken upstream certificate sniffing link in how-mitmproxy-works Updated broken link in docs/src/how-mitmproxy-works.md from [/overview/features](/overview/features/#upstream-certificates) to [/concepts/certificates/](/concepts/certificates/#upstream-certificate-sniffing) to point to the correct resource. --- docs/src/content/concepts/how-mitmproxy-works.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/content/concepts/how-mitmproxy-works.md b/docs/src/content/concepts/how-mitmproxy-works.md index 1ce522365..55357c5b9 100644 --- a/docs/src/content/concepts/how-mitmproxy-works.md +++ b/docs/src/content/concepts/how-mitmproxy-works.md @@ -97,7 +97,7 @@ information to initiate the pipe, even though it doesn't reveal the remote hostname. Mitmproxy has a cunning mechanism that smooths this over - [upstream certificate -sniffing]({{< relref "/overview/features#upstream-certificates" >}}). As soon as +sniffing]({{< relref "/concepts/certificates/#upstream-certificate-sniffing" >}}). As soon as we see the CONNECT request, we pause the client part of the conversation, and initiate a simultaneous connection to the server. We complete the TLS handshake with the server, and inspect the certificates it used. Now, we use the Common