diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2011-03-30 12:05:50 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2011-03-30 12:05:50 +1300 |
| commit | f12510d9794c155657e80864529e0198872e7d7d (patch) | |
| tree | 8d393ac81ef8929821e4e587af8fe59bd2d2cba5 /doc-src/ssl.html | |
| parent | 60aa16fc56d67506886315818773d6fedddb2d4f (diff) | |
| download | mitmproxy-f12510d9794c155657e80864529e0198872e7d7d.tar.gz mitmproxy-f12510d9794c155657e80864529e0198872e7d7d.tar.bz2 mitmproxy-f12510d9794c155657e80864529e0198872e7d7d.zip | |
Spell-check docs, setup.py fixes, add missing files to manifest.
Diffstat (limited to 'doc-src/ssl.html')
| -rw-r--r-- | doc-src/ssl.html | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc-src/ssl.html b/doc-src/ssl.html index a8004082..7ee9438e 100644 --- a/doc-src/ssl.html +++ b/doc-src/ssl.html @@ -27,7 +27,7 @@ a browser, just accepting the bogus SSL cert manually is not too much trouble, but there are a number of cases where you will want to configure your testing system or browser to trust the __mitmproxy__ CA as a signing root authority: -- If you are testing non-browser software that checks SSL cert validiy using +- If you are testing non-browser software that checks SSL cert validity using the system certificate store. - You are testing an app that makes non-interactive (JSONP, script src, etc.) requests to SSL resources. Another workaround in this case is to manually visit |