diff options
Diffstat (limited to 'doc-src/modes.html')
| -rw-r--r-- | doc-src/modes.html | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc-src/modes.html b/doc-src/modes.html index b5a38696..a878fd82 100644 --- a/doc-src/modes.html +++ b/doc-src/modes.html @@ -149,7 +149,7 @@ this: <h1>Reverse Proxy</h1> </div> -Mitmproxy is usually used with a client that uses the proxy to access the +mitmproxy is usually used with a client that uses the proxy to access the Internet. Using reverse proxy mode, you can use mitmproxy to act like a normal HTTP server: @@ -174,14 +174,14 @@ requests recorded in mitmproxy. - Say you have some toy project that should get SSL support. Simply set up mitmproxy with SSL termination and you're done (<code>mitmdump -p 443 -R -https2http://localhost:80/</code>). There are better tools for this specific +http://localhost:80/</code>). There are better tools for this specific task, but mitmproxy is very quick and simple way to set up an SSL-speaking server. - Want to add a non-SSL-capable compression proxy in front of your server? You -could even spawn a mitmproxy instance that terminates SSL (https2http://...), +could even spawn a mitmproxy instance that terminates SSL (-R http://...), point it to the compression proxy and let the compression proxy point to a -SSL-initiating mitmproxy (http2https://...), which then points to the real +SSL-initiating mitmproxy (-R https://...), which then points to the real server. As you see, it's a fairly flexible thing. Note that mitmproxy supports either an HTTP or an HTTPS upstream server, not |