aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMaximilian Hils <git@maximilianhils.com>2017-02-14 17:45:54 +0100
committerGitHub <noreply@github.com>2017-02-14 17:45:54 +0100
commit5acdd78b15ac85c6727f03e71d843d4b20e1a8d2 (patch)
treee70fad1a2a8832034cc32d254c84f819c1403d20
parent75a0a4c09276ef2aa479c9ae9feab97f7803ed6d (diff)
downloadmitmproxy-5acdd78b15ac85c6727f03e71d843d4b20e1a8d2.tar.gz
mitmproxy-5acdd78b15ac85c6727f03e71d843d4b20e1a8d2.tar.bz2
mitmproxy-5acdd78b15ac85c6727f03e71d843d4b20e1a8d2.zip
fix typo
-rw-r--r--examples/complex/dns_spoofing.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/examples/complex/dns_spoofing.py b/examples/complex/dns_spoofing.py
index 1fb59f74..c6d46b66 100644
--- a/examples/complex/dns_spoofing.py
+++ b/examples/complex/dns_spoofing.py
@@ -1,5 +1,5 @@
"""
-This inline scripts makes it possible to use mitmproxy in scenarios where IP spoofing has been used to redirect
+This script makes it possible to use mitmproxy in scenarios where IP spoofing has been used to redirect
connections to mitmproxy. The way this works is that we rely on either the TLS Server Name Indication (SNI) or the
Host header of the HTTP request.
Of course, this is not foolproof - if an HTTPS connection comes without SNI, we don't