Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Refer to current internet standards in docs on proxies #3124

Merged
merged 1 commit into from
Sep 14, 2023
Merged

Refer to current internet standards in docs on proxies #3124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
10 changes: 5 additions & 5 deletions docs/advanced-usage.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -198,31 +198,31 @@ urllib3's behavior will be different depending on your proxy and destination:

* HTTP proxy + HTTP destination
Your request will be forwarded with the `absolute URI
<https://tools.ietf.org/html/rfc7230#section-5.3.2>`_.
<https://datatracker.ietf.org/doc/html/rfc9112#name-absolute-form>`_.

* HTTP proxy + HTTPS destination
A TCP tunnel will be established with a `HTTP
CONNECT <https://tools.ietf.org/html/rfc7231#section-4.3.6>`_. Afterward a
CONNECT <https://datatracker.ietf.org/doc/html/rfc9110#name-connect>`_. Afterward a
TLS connection will be established with the destination and your request
will be sent.

* HTTPS proxy + HTTP destination
A TLS connection will be established to the proxy and later your request
will be forwarded with the `absolute URI
<https://tools.ietf.org/html/rfc7230#section-5.3.2>`_.
<https://datatracker.ietf.org/doc/html/rfc9110#name-connect>`_.

* HTTPS proxy + HTTPS destination
A TLS-in-TLS tunnel will be established. An initial TLS connection will be
established to the proxy, then an `HTTP CONNECT
<https://tools.ietf.org/html/rfc7231#section-4.3.6>`_ will be sent to
<https://datatracker.ietf.org/doc/html/rfc9110#name-connect>`_ will be sent to
establish a TCP connection to the destination and finally a second TLS
connection will be established to the destination. You can customize the
:class:`ssl.SSLContext` used for the proxy TLS connection through the
``proxy_ssl_context`` argument of the :class:`~poolmanager.ProxyManager`
class.

For HTTPS proxies we also support forwarding your requests to HTTPS destinations with
an `absolute URI <https://tools.ietf.org/html/rfc7230#section-5.3.2>`_ if the
an `absolute URI <https://datatracker.ietf.org/doc/html/rfc9112#name-absolute-form>`_ if the
``use_forwarding_for_https`` argument is set to ``True``. We strongly recommend you
**only use this option with trusted or corporate proxies** as the proxy will have
full visibility of your requests.
Expand Down