mirror of
https://github.com/Grasscutters/mitmproxy.git
synced 2024-11-25 18:03:50 +00:00
67885320c0
This commit replaces our WSGI implementation with a new ASGI one,
which then uses `asgiref`'s compatibility mode to still support WSGI applications.
The ASGI implementation is a bit bare-bone, but good enough for our purposes.
The major changes are:
- We now support ASGI apps.
- Instead of taking connections out of mitmproxy's normal processing,
we now just set flow.response and let things continue as usual.
This allows users to see responses in mitmproxy, use the response hook
to modify app responses, etc. Also important for us,
this makes the new implementation work for shenanigans like sans-io.
28 lines
908 B
Python
28 lines
908 B
Python
"""
|
|
Host a WSGI app in mitmproxy.
|
|
|
|
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.
|
|
"""
|
|
from flask import Flask
|
|
from mitmproxy.addons import asgiapp
|
|
|
|
app = Flask("proxapp")
|
|
|
|
|
|
@app.route('/')
|
|
def hello_world() -> str:
|
|
return 'Hello World!'
|
|
|
|
|
|
addons = [
|
|
# Host app at the magic domain "example.com" on port 80. Requests to this
|
|
# domain and port combination will now be routed to the WSGI app instance.
|
|
asgiapp.WSGIApp(app, "example.com", 80)
|
|
# SSL 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 serve its certificate (unless --no-upstream-cert is set)
|
|
# but won't send any data.
|
|
# mitmproxy.ctx.master.apps.add(app, "example.com", 443)
|
|
]
|