romenskiy2012/curl
1
0
Fork 0
mirror of https://github.com/curl/curl.git synced 2026-08-25 06:53:31 +03:00
Code Issues Projects Releases Packages Wiki Activity

tidy-up: typos, comment nits

Browse source 
Closes #22294
This commit is contained in:
Viktor Szakats 2026-06-26 22:57:40 +02:00
parent 5c5334f831
commit b093d88447
No known key found for this signature in database
35 changed files with 91 additions and 90 deletions
Download patch file Download diff file Expand all files Collapse all files

6
docs/internals/CREDENTIALS.md
View file

@ -12,7 +12,7 @@ Authorization credentials are kept in `struct Curl_creds`. This contains:
* `passwd`: the password, maybe the empty string
* `sasl_authzid`: the SASL `authz` value, maybe the empty string
* `oauth_bearer`: the OAUTH bearer token, maybe the empty string
* `source`: where the credentials from
* `source`: where the credentials come from
* `refcount`: a reference counter to link/unlink `creds`
With reference counting, `creds` can be linked in several places.
@ -54,12 +54,12 @@ password and `netrc` is consulted as well (when built in).
### `conn->creds`
Once `data->state.creds` is known, the connection credentials are
determined. For protocols that tie authorization to everything send
determined. For protocols that tie authorization to everything sent
on a connection (protocols without flag `PROTOPT_CREDSPERREQUEST`),
`conn->creds` is linked to `data->state.creds`. Only connections
carrying the same credentials may be reused.
Protocol with flag `PROTOPT_CREDSPERREQUEST` leave `conn->creds` empty,
Protocols with flag `PROTOPT_CREDSPERREQUEST` leave `conn->creds` empty,
as connections for such protocols may be reused with different
credentials.