Skip to content

Clarify that Session.verify accepts a string CA bundle path (Fixes #6859) #7119

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

Open
adiOrInder wants to merge 1 commit into
base: main
Choose a base branch
from
+14 −0
Open

Clarify that Session.verify accepts a string CA bundle path (Fixes #6859) #7119

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions docs/user/advanced.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -250,6 +250,20 @@ man-in-the-middle (MitM) attacks. Setting verify to ``False`` may be useful
during local development or testing.

By default, ``verify`` is set to True. Option ``verify`` only applies to host certs.
When using a ``Session`` object, the ``Session.verify`` attribute accepts the same
values as the ``verify`` parameter passed to ``requests.get`` and other request
methods. This means it may be:

* ``True`` – verify the server’s TLS certificate using the system’s CA bundle (default),
* ``False`` – disable TLS certificate verification entirely (INSECURE),
* ``str`` – a filesystem path to a CA bundle file or directory to use instead of
the system defaults.

For example::

s = requests.Session()
s.verify = "/path/to/cacert.pem"
s.get("https://example.com")

Client Side Certificates
------------------------
Expand Down