2014-01-27 01:16:23 +00:00
|
|
|
|
|
|
|
|
In this mode, mitmproxy accepts proxy requests and unconditionally forwards all
|
2014-03-13 23:02:00 +00:00
|
|
|
requests to a specified upstream proxy server. This is in contrast to <a
|
2014-01-27 01:16:23 +00:00
|
|
|
href="@!urlTo("reverseproxy.html")!@">reverse proxy mode</a>, in which
|
|
|
|
|
mitmproxy forwards ordinary HTTP requests to an upstream server.
|
|
|
|
|
|
|
|
|
|
<table class="table">
|
|
|
|
|
<tbody>
|
|
|
|
|
<tr>
|
2014-09-06 22:42:25 +00:00
|
|
|
<th width="20%">command-line</th> <td>-U http://hostname[:port]</td>
|
2014-01-27 01:16:23 +00:00
|
|
|
</tr>
|
|
|
|
|
</tbody>
|
|
|
|
|
</table>
|
2014-10-23 03:13:03 +00:00
|
|
|
|
|
|
|
|
Here, **schema** is one of http, https, http2https or https2http. The latter
|
|
|
|
|
two extended schema specifications control the use of HTTP and HTTPS on
|
|
|
|
|
mitmproxy and the upstream server. You can indicate that mitmproxy should use
|
|
|
|
|
HTTP, and the upstream server uses HTTPS like this:
|
|
|
|
|
|
|
|
|
|
http2https://hostname:port
|
|
|
|
|
|
|
|
|
|
And you can indicate that mitmproxy should use HTTPS while the upstream
|
|
|
|
|
service uses HTTP like this:
|
|
|
|
|
|
|
|
|
|
https2http://hostname:port
|
|
|
|
|
|
|
|
|
|
|
