Containerized version of mitmproxy, an interactive SSL-capable intercepting HTTP proxy.
$ docker run --rm -it [-v ~/.mitmproxy:/home/mitmproxy/.mitmproxy] -p 8080:8080 mitmproxy/mitmproxy
The volume mount is optional: It's to store the generated CA certificates.
Once started, mitmproxy listens as a HTTP proxy on
$ http_proxy=http://localhost:8080/ curl http://example.com/ $ https_proxy=http://localhost:8080/ curl -k https://example.com/
You can also start
mitmdump by just adding that to the end of the command-line:
$ docker run --rm -it -p 8080:8080 mitmproxy/mitmproxy mitmdump
mitmweb, you also need to expose port 8081:
# this makes :8081 accessible to the local machine only $ docker run --rm -it -p 8080:8080 -p 127.0.0.1:8081:8081 mitmproxy/mitmproxy mitmweb
For further details, please consult the mitmproxy documentation.
The available release tags can be seen here.
@jeffreycharles: Fixed, thanks! :)
We don't get notifications for comments here, so please file an issue in the repo if there's something that needs our attention.
latest tagged image appears to be 0.17. I would've expected it to be the latest stable (0.18.2) or master. Also having a
0.18.2 tagged one would be nice.
@iseedeadpeople: We are porting mitmproxy to Python 3 and we will remove Python 2 support from the project with one of the next releases. The last Docker image using Python 2.7 will be 0.17.
Is it me or... You guys recently decided to upgrade Python from 2.7 to 3.5?
If that's the case, is there anyway I can get in touch with mitmproxy:dev (0.18) with python 2.7?