diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2015-06-12 14:15:26 +1200 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2015-06-12 14:15:26 +1200 |
| commit | fcc15581808859b3d6670829c2d5248483660839 (patch) | |
| tree | f85b02a214f94c9591f4bab99005195118764021 | |
| parent | 85e1ae7543e903d7f703e9d07515929513381687 (diff) | |
| download | mitmproxy-fcc15581808859b3d6670829c2d5248483660839.tar.gz mitmproxy-fcc15581808859b3d6670829c2d5248483660839.tar.bz2 mitmproxy-fcc15581808859b3d6670829c2d5248483660839.zip | |
Fix typo in docs - thanks to Jim_Showalter@intuit.com
| -rw-r--r-- | doc-src/howmitmproxy.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc-src/howmitmproxy.html b/doc-src/howmitmproxy.html index f114e145..fabd393a 100644 --- a/doc-src/howmitmproxy.html +++ b/doc-src/howmitmproxy.html @@ -120,8 +120,8 @@ Name](http://en.wikipedia.org/wiki/SubjectAltName) field in the SSL certificate that allows an arbitrary number of alternative domains to be specified. If the expected domain matches any of these, the client will proceed, even though the domain doesn't match the certificate Common Name. The answer here is simple: -when extract the CN from the upstream cert, we also extract the SANs, and add -them to the generated dummy certificate. +when we extract the CN from the upstream cert, we also extract the SANs, and +add them to the generated dummy certificate. ## Complication 3: Server Name Indication |