aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/howmitmproxy.html
diff options
context:
space:
mode:
authorAldo Cortesi <aldo@nullcube.com>2013-06-16 13:59:01 +1200
committerAldo Cortesi <aldo@nullcube.com>2013-06-16 13:59:01 +1200
commitdb43f1ffccfb006c6856888b8f31c0745aacebb4 (patch)
tree209e613b07cdda69239dca59f0029c6c9d0c61fc /doc-src/howmitmproxy.html
parentbef56623657cc12677725acd76e7bee26ece6267 (diff)
downloadmitmproxy-db43f1ffccfb006c6856888b8f31c0745aacebb4.tar.gz
mitmproxy-db43f1ffccfb006c6856888b8f31c0745aacebb4.tar.bz2
mitmproxy-db43f1ffccfb006c6856888b8f31c0745aacebb4.zip
Version bump, doc extension, URLs to github.com/mitmproxy/*
Diffstat (limited to 'doc-src/howmitmproxy.html')
-rw-r--r--doc-src/howmitmproxy.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc-src/howmitmproxy.html b/doc-src/howmitmproxy.html
index 09a69ec2..94afd522 100644
--- a/doc-src/howmitmproxy.html
+++ b/doc-src/howmitmproxy.html
@@ -246,7 +246,7 @@ mechanism has a different way of exposing this data, so this introduces the
second component required for working transparent proxying: a host module that
knows how to retrieve the original destination address from the router. In
mitmproxy, this takes the form of a built-in set of
-[modules](https://github.com/cortesi/mitmproxy/tree/master/libmproxy/platform)
+[modules](https://github.com/mitmproxy/mitmproxy/tree/master/libmproxy/platform)
that know how to talk to each platform's redirection mechanism. Once we have
this information, the process is fairly straight-forward.