diff options
Diffstat (limited to 'docs/src')
| -rw-r--r-- | docs/src/content/addons-overview.md | 2 | ||||
| -rw-r--r-- | docs/src/content/concepts-certificates.md | 6 |
2 files changed, 4 insertions, 4 deletions
diff --git a/docs/src/content/addons-overview.md b/docs/src/content/addons-overview.md index fea5feb2..bfde7f27 100644 --- a/docs/src/content/addons-overview.md +++ b/docs/src/content/addons-overview.md @@ -64,7 +64,7 @@ Here are a few things to note about the code above: finds into the addons mechanism. - Addons are just objects - in this case our addon is an instance of `Counter`. - The `request` method is an example of an **event**. Addons simply implement a - method for each event they wan to handle. Each event has a signature + method for each event they want to handle. Each event has a signature consisting of arguments that are passed to the method. For `request`, this is an instance of `mitmproxy.http.HTTPFlow`. - Finally, the `ctx` module is a holdall module that exposes a set of standard diff --git a/docs/src/content/concepts-certificates.md b/docs/src/content/concepts-certificates.md index e6586576..d7f53127 100644 --- a/docs/src/content/concepts-certificates.md +++ b/docs/src/content/concepts-certificates.md @@ -143,14 +143,14 @@ mitmproxy --cert *.example.com=cert.pem By default, mitmproxy will use `~/.mitmproxy/mitmproxy-ca.pem` as the certificate authority to generate certificates for all domains for which no custom certificate is provided (see above). You can use your own -certificate authority by passing the `--cadir DIRECTORY` option to +certificate authority by passing the `--set cadir=DIRECTORY` option to mitmproxy. Mitmproxy will then look for `mitmproxy-ca.pem` in the specified directory. If no such file exists, it will be generated automatically. ## Using a client side certificate -You can use a client certificate by passing the `--client-certs DIRECTORY|FILE` +You can use a client certificate by passing the `--set client_certs=DIRECTORY|FILE` option to mitmproxy. Using a directory allows certs to be selected based on hostname, while using a filename allows a single specific certificate to be used for all SSL connections. Certificate files must be in the PEM format and should @@ -158,7 +158,7 @@ contain both the unencrypted private key and the certificate. ### Multiple client certificates -You can specify a directory to `--client-certs`, in which case the matching +You can specify a directory to `--set client_certs=DIRECTORY`, in which case the matching certificate is looked up by filename. So, if you visit example.org, mitmproxy looks for a file named `example.org.pem` in the specified directory and uses this as the client cert. |