diff options
| author | Maximilian Hils <git@maximilianhils.com> | 2020-04-26 19:29:02 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-04-26 19:29:02 +0200 |
| commit | e9d5b6d9f590e514f27cc32abf001a694a3e8795 (patch) | |
| tree | 364138d32a3b120ac6e40b5974b1ce1773072633 | |
| parent | cddcc8dfb109367e615b7d56fc8da1225682ffe4 (diff) | |
| download | mitmproxy-e9d5b6d9f590e514f27cc32abf001a694a3e8795.tar.gz mitmproxy-e9d5b6d9f590e514f27cc32abf001a694a3e8795.tar.bz2 mitmproxy-e9d5b6d9f590e514f27cc32abf001a694a3e8795.zip | |
fix typo
| -rw-r--r-- | docs/src/content/concepts-certificates.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/src/content/concepts-certificates.md b/docs/src/content/concepts-certificates.md index 20b03dc6..9b5f1a83 100644 --- a/docs/src/content/concepts-certificates.md +++ b/docs/src/content/concepts-certificates.md @@ -65,7 +65,7 @@ SSL sites that your client visits. Since your browser won't trust the mitmproxy CA out of the box, you will see an SSL certificate warning every time you visit a new SSL domain through mitmproxy. When you are testing a single site through a browser, just accepting the bogus SSL cert manually is not too much trouble, but -there are a many circumstances where you will want to configure your testing +there are many circumstances where you will want to configure your testing system or browser to trust the mitmproxy CA as a signing root authority. For security reasons, the mitmproxy CA is generated uniquely on the first start and is not shared between mitmproxy installations on different devices. |