This commit improves the user experience of the users leveraging rustls.
When building the identity to use for requests, it's now possible to use
also private keys using Elliptic Curve that are encoded with SEC1
standard.
This is the default encoding used by openssl when EC keys are created.
Prior to this commit users had to convert those keys from the SEC1
encoding to the PKCS 8 one, which is something not trivial.
This feature has been recently added to rustls-pemfile crate.
Signed-off-by: Flavio Castelli <fcastelli@suse.com>
serde_urlencoded 0.7.0 has an incorrect serde version dependency.
This causes issues in `cargo update -Z minimal-versions` builds.
It's not noticeable while testing in CI because cookie_store depends
on serde 1.0.126, however because this is an optional dependency
there is a possibility that a project using reqwest won't enable
it.
At least `wrap_stream` it is written in plain text, but adding the visual flag should be better and coherent with `byte_stream` documentation, but nothing is shown for `From<File>` for `Body`.
Co-authored-by: kraktus <kraktus@users.noreply.github.com>
* Updated `cookie_store` dependency
* Bump `cookie_store` version to `0.14.0`
* Add documentation in `cookie` module to direct users to the
new `reqwest_cookie_store` crate for more advanced scenarios.
* update `cookie` dependency to `0.15`
* Update for `cookie_store` `v0.14.1`
* Replace usage of deprecated `cookie_store::CookieStore::get_request_cookies`
for `cookie_store::CookieStore::get_request_values`.
* Update `cookie_store` to `v0.15.0`
The deprecation of `get_request_cookies` should have warranted a
minor version bump.
There are a few ways in which reqwest's handling of NO_PROXY differs from cURL (and other implementations). The biggest issue is that whitespace between entries should be ignored/trimmed, but is not (i.e. "NO_PROXY='a, b'" would never match "b"). In addition, according to cURL's rules, a NO_PROXY entry without a leading dot should match the domain itself as well as any subdomains (reqwest only handles exact matches if there is no leading dot) and entries with a leading dot should only match subdomains (but request allows exact matches). Finally, cURL allows a special entry "*" to match all entries (effectively disabling use of the proxy).
