diff options
| author | Aldo Cortesi <aldo@nullcube.com> | 2014-10-23 16:13:03 +1300 |
|---|---|---|
| committer | Aldo Cortesi <aldo@nullcube.com> | 2014-10-23 16:13:03 +1300 |
| commit | 6bed0764609029e9d01b1d28b7826fb37ab20d3e (patch) | |
| tree | 6de10b2b56d5bc5447b38bf364468318389d0b18 /doc-src | |
| parent | 6aa05df944add1fe7b681ae6e7d6336f2ff3ae55 (diff) | |
| download | mitmproxy-6bed0764609029e9d01b1d28b7826fb37ab20d3e.tar.gz mitmproxy-6bed0764609029e9d01b1d28b7826fb37ab20d3e.tar.bz2 mitmproxy-6bed0764609029e9d01b1d28b7826fb37ab20d3e.zip | |
Document http2https and https2http
Diffstat (limited to 'doc-src')
| -rw-r--r-- | doc-src/features/reverseproxy.html | 17 | ||||
| -rw-r--r-- | doc-src/features/upstreamproxy.html | 14 |
2 files changed, 30 insertions, 1 deletions
diff --git a/doc-src/features/reverseproxy.html b/doc-src/features/reverseproxy.html index ea91fe1f..1c57f0b2 100644 --- a/doc-src/features/reverseproxy.html +++ b/doc-src/features/reverseproxy.html @@ -7,7 +7,22 @@ mitmproxy forwards HTTP proxy requests to an upstream proxy server. <table class="table"> <tbody> <tr> - <th width="20%">command-line</th> <td>-R http[s]://hostname[:port]</td> + <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 + + + diff --git a/doc-src/features/upstreamproxy.html b/doc-src/features/upstreamproxy.html index bb354cd3..47bc115d 100644 --- a/doc-src/features/upstreamproxy.html +++ b/doc-src/features/upstreamproxy.html @@ -11,3 +11,17 @@ mitmproxy forwards ordinary HTTP requests to an upstream server. </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 + + |