| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
- Fixed Read the Docs links
- Fixed GitHub links
- Fixed PyPI links
|
| | |
|
| |
|
|
|
|
|
| |
OAuth 2 is the authentication protocol underpinning OpenID Connect.
Mention that explicitly for the benefit of folks looking for information on using
requests with OpenID Connect that don't yet know that OAuth 2 is the
relevant underlying authentication protocol.
|
| |
|
|
|
|
|
| |
The previous summary gave the impression that requests-oauthlib only supports
OAuth 1.
This updates makes it clear that it also supports OAuth 2, and links directly to the
use case specific authentication flow guides.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This closes #2062 by clarifying in the docs which auth
header takes precedence:
1st auth=
2nd .netrc
3rd headers=
This precedence order is already tested in test_requests.py,
in the test_basicauth_with_netrc method. Perhaps we should
add further tests for non-basic auth schemes.
|
| |
|
|
| |
Change-Id: Ie38844a40ec7a483e6ce5e56077be344242bcd99
|
| |
|
|
| |
Refs #1471
|
| | |
|
| |
|
|
| |
Signed-off-by: Kwpolska <kwpolska@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The documentation does not make it clear that when the credentials
from netrc are used, Requests authenticates with HTTP Basic Auth.
I just spent ages trying to figure out why it wasn't working, and
it was because although the credentials in the netrc were correct,
the server actually required HTTP Digest Auth.
Add a section in the authentication documentation to make it clear
that HTTP Basic Auth is used.
|
| | |
|
| |
|
|
|
| |
Twitter API v1.1 Streaming now requires OAuth Authentication rather than XAuth.
I believe v1 is being blacked out sometime at the beginning of May.
|
| |
|