diff options
| author | Maximilian Hils <git@maximilianhils.com> | 2015-05-10 20:29:34 +0200 |
|---|---|---|
| committer | Maximilian Hils <git@maximilianhils.com> | 2015-05-10 20:29:34 +0200 |
| commit | a8cb8a01a30ad1432ff5d25ecc183aa54c72815a (patch) | |
| tree | 50c1a31dccba71a134444f170625b9b6910e1774 | |
| parent | 541a506b5fbf0aae477a30733f5060b67787a7d5 (diff) | |
| download | mitmproxy-a8cb8a01a30ad1432ff5d25ecc183aa54c72815a.tar.gz mitmproxy-a8cb8a01a30ad1432ff5d25ecc183aa54c72815a.tar.bz2 mitmproxy-a8cb8a01a30ad1432ff5d25ecc183aa54c72815a.zip | |
docs: add parantheses for ignore parameters.
| -rw-r--r-- | doc-src/features/passthrough.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc-src/features/passthrough.html b/doc-src/features/passthrough.html index 15e36434..3da8692c 100644 --- a/doc-src/features/passthrough.html +++ b/doc-src/features/passthrough.html @@ -62,13 +62,13 @@ Here are some other examples for ignore patterns: # Exempt traffic from the iOS App Store (the regex is lax, but usually just works): --ignore apple.com:443 # "Correct" version without false-positives: ---ignore ^(.+\.)?apple\.com:443$ +--ignore "^(.+\.)?apple\.com:443$" # Ignore example.com, but not its subdomains: ---ignore ^example.com: +--ignore "^example.com:" # Ignore everything but example.com and mitmproxy.org: ---ignore ^(?!example\.com)(?!mitmproxy\.org) +--ignore "^(?!example\.com)(?!mitmproxy\.org)" # Transparent mode: --ignore 17\.178\.96\.59:443 @@ -81,4 +81,4 @@ Here are some other examples for ignore patterns: - [TCP Proxy](@!urlTo("tcpproxy.html")!@) - [Response Streaming](@!urlTo("responsestreaming.html")!@) -[^explicithttp]: This stems from an limitation of explicit HTTP proxying: A single connection can be re-used for multiple target domains - a <code>GET http://example.com/</code> request may be followed by a <code>GET http://evil.com/</code> request on the same connection. If we start to ignore the connection after the first request, we would miss the relevant second one.
\ No newline at end of file +[^explicithttp]: This stems from an limitation of explicit HTTP proxying: A single connection can be re-used for multiple target domains - a <code>GET http://example.com/</code> request may be followed by a <code>GET http://evil.com/</code> request on the same connection. If we start to ignore the connection after the first request, we would miss the relevant second one. |