aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/features/upstreamcerts.html
diff options
context:
space:
mode:
authorAldo Cortesi <aldo@nullcube.com>2014-01-22 13:33:02 +1300
committerAldo Cortesi <aldo@nullcube.com>2014-01-22 13:33:02 +1300
commit8f88fcedd601c0033b4469b66626a83011879baf (patch)
tree878b2c737f2483f52e7c222541483773af1c152a /doc-src/features/upstreamcerts.html
parent7ddc941116852b191d80643af70af90a6fd8849c (diff)
downloadmitmproxy-8f88fcedd601c0033b4469b66626a83011879baf.tar.gz
mitmproxy-8f88fcedd601c0033b4469b66626a83011879baf.tar.bz2
mitmproxy-8f88fcedd601c0033b4469b66626a83011879baf.zip
Move the doc tree out into its own repo.
Diffstat (limited to 'doc-src/features/upstreamcerts.html')
-rw-r--r--doc-src/features/upstreamcerts.html21
1 files changed, 0 insertions, 21 deletions
diff --git a/doc-src/features/upstreamcerts.html b/doc-src/features/upstreamcerts.html
deleted file mode 100644
index 8de75ee3..00000000
--- a/doc-src/features/upstreamcerts.html
+++ /dev/null
@@ -1,21 +0,0 @@
-When mitmproxy receives a connection destined for an SSL-protected service, it
-freezes the connection before reading its request data, and makes a connection
-to the upstream server to "sniff" the contents of its SSL certificate. The
-information gained - the __Common Name__ and __Subject Alternative Names__ - is
-then used to generate the interception certificate, which is sent to the client
-so the connection can continue.
-
-This rather intricate little dance lets us seamlessly generate correct
-certificates even if the client has specifed only an IP address rather than the
-hostname. It also means that we don't need to sniff additional data to generate
-certs in transparent mode.
-
-Upstream cert sniffing is on by default, and can optionally be turned off.
-
-<table class="table">
- <tbody>
- <tr>
- <th width="20%">command-line</th> <td>--no-upstream-cert</td>
- </tr>
- </tbody>
-</table>