22 releases (5 breaking)
|0.7.2||Aug 10, 2023|
|0.7.1||Jul 13, 2023|
|0.7.0||Jun 29, 2023|
|0.6.2||Mar 30, 2023|
|0.2.7||Oct 27, 2022|
#261 in Authentication
1,836 downloads per month
Used in qcs
This crate provides an autogenerated gRPC client for the QCS API, along with helper utilities for automatically loading credentials from a user's QCS config and keeping authentication tokens refreshed.
get_channel: create a
Channelto the given gRPC endpoint with QCS authentication automatically set up, that routes requests through client-side HTTP, HTTPS, or SOCKS5 proxies based on the presence of
wrap_channel: wrap an existing
Channelwith QCS authentication.
See docs.rs for a quick start guide.
get_channel function configures the returned
Channel to route requests through a client proxy
based on the presence of environment variables
HTTP_PROXY. The variable names can be
all-uppercase or all-lowercase, but the all-uppercase variants will take precedence.
Currently, the supported proxy schemes are
There are some caveats to the proxy configuration:
- If both variables are defined, neither can be a
socks5proxy, unless they are both the same value.
- If only one variable is defined, and it is a
socks5proxy, all traffic will routed through it.