aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/features/passthrough.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc-src/features/passthrough.html')
-rw-r--r--doc-src/features/passthrough.html8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc-src/features/passthrough.html b/doc-src/features/passthrough.html
index 15e36434..7b377c82 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.