2014-09-08 14:02:31 +00:00
|
|
|
"""
|
2020-06-22 23:53:39 +00:00
|
|
|
Host a WSGI app in mitmproxy.
|
|
|
|
|
|
2014-09-08 14:02:31 +00:00
|
|
|
This example shows how to graft a WSGI app onto mitmproxy. In this
|
|
|
|
|
instance, we're using the Flask framework (http://flask.pocoo.org/) to expose
|
|
|
|
|
a single simplest-possible page.
|
|
|
|
|
"""
|
2024-03-06 20:54:11 +00:00
|
|
|
|
2014-09-08 14:02:31 +00:00
|
|
|
from flask import Flask
|
2022-11-29 13:28:41 +00:00
|
|
|
|
2020-08-12 14:27:15 +00:00
|
|
|
from mitmproxy.addons import asgiapp
|
2014-09-08 14:02:31 +00:00
|
|
|
|
|
|
|
|
app = Flask("proxapp")
|
|
|
|
|
|
|
|
|
|
|
2022-04-26 11:53:35 +00:00
|
|
|
@app.route("/")
|
2017-04-28 21:56:14 +00:00
|
|
|
def hello_world() -> str:
|
2022-04-26 11:53:35 +00:00
|
|
|
return "Hello World!"
|
2014-09-08 14:02:31 +00:00
|
|
|
|
2020-01-20 18:47:14 +00:00
|
|
|
|
2020-01-20 18:25:30 +00:00
|
|
|
addons = [
|
2020-04-29 03:35:24 +00:00
|
|
|
# Host app at the magic domain "example.com" on port 80. Requests to this
|
2016-10-18 22:48:51 +00:00
|
|
|
# domain and port combination will now be routed to the WSGI app instance.
|
2022-05-30 14:41:10 +00:00
|
|
|
asgiapp.WSGIApp(app, "example.com", 80),
|
|
|
|
|
# TLS works too, but the magic domain needs to be resolvable from the mitmproxy machine due to mitmproxy's design.
|
|
|
|
|
# mitmproxy will connect to said domain and use its certificate but won't send any data.
|
|
|
|
|
# By using `--set upstream_cert=false` and `--set connection_strategy_lazy` the local certificate is used instead.
|
|
|
|
|
# asgiapp.WSGIApp(app, "example.com", 443),
|
2020-01-20 18:25:30 +00:00
|
|
|
]
|
