aboutsummaryrefslogtreecommitdiffstats
path: root/docs/features/reverseproxy.rst
diff options
context:
space:
mode:
Diffstat (limited to 'docs/features/reverseproxy.rst')
-rw-r--r--docs/features/reverseproxy.rst3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/features/reverseproxy.rst b/docs/features/reverseproxy.rst
index 87a598ff..77e9327c 100644
--- a/docs/features/reverseproxy.rst
+++ b/docs/features/reverseproxy.rst
@@ -51,6 +51,7 @@ There are two ways to solve this:
1. Modify the hosts file of your OS so that "example.com" resolves to your proxy's IP.
Then, access example.com directly. Make sure that your proxy can still resolve the original IP
or specify an IP in mitmproxy.
-2. Use mitmproxy's :ref:`setheaders` feature to rewrite the host header: ``--setheader :~q:Host:example.com``.
+2. Use mitmproxy's :ref:`setheaders` feature to rewrite the host header:
+ ``--setheader :~q:Host:example.com``.
However, keep in mind that absolute URLs within the returned document or HTTP redirects will
cause the client application to bypass the proxy.