aboutsummaryrefslogtreecommitdiffstats
path: root/doc-src/features/reverseproxy.html
blob: 1c57f0b23464b35c4e1d1a9d243471ae44733f34 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
In reverse proxy mode, mitmproxy accepts standard HTTP requests and forwards
them to the specified upstream server. This is in contrast to
<a href="@!urlTo("upstreamproxy.html")!@">upstream proxy mode</a>, in which
mitmproxy forwards HTTP proxy requests to an upstream proxy server.

<table class="table">
    <tbody>
        <tr>
            <th width="20%">command-line</th> <td>-R <i>schema</i>://hostname[:port]</td>
        </tr>
    </tbody>
</table>

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