aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/upstreamcerts.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc-src/upstreamcerts.html')
-rw-r--r--doc-src/upstreamcerts.html15
1 files changed, 0 insertions, 15 deletions
diff --git a/doc-src/upstreamcerts.html b/doc-src/upstreamcerts.html
deleted file mode 100644
index 32a13a9a..00000000
--- a/doc-src/upstreamcerts.html
+++ /dev/null
@@ -1,15 +0,0 @@
-- command-line: _--upstream-cert_
-- mitmproxy shortcut: _o_, then _u_
-
-Normally, mitmproxy uses the target domain specified in a client's proxy
-request to generate an interception certificate. When __upstream-cert__ mode is
-activated a different procedure is followed: a connection is made to the
-specified remote server to retrieve its __Common Name__ and __Subject
-Alternative Names__. This feature is especially useful when the client
-specifies an IP address rather than a host name in the proxy request. If this
-is the case, we can only generate a certificate if we can establish the __CN__
-and __SANs__ from the upstream server.
-
-Note that __upstream-cert__ mode does not work when the remote server relies on
-[Server Name Indication](http://en.wikipedia.org/wiki/Server_Name_Indication).
-Luckily, SNI is still not very widely used.