Runtime Configuration
Last updated
Was this helpful?
Last updated
Was this helpful?
For major re-configurations or variations from the default behavior of DIDKit, modifying the code and compiling your own binaries is required.
For a short but growing list of minor options, however, runtime configuration of DIDKit behavior and security policies is possible. Feel free to open issues on DIDKit's if you are experimenting with DIDKit and have pain points that would be served by additional runtime configuration options.
For all outbound HTTP requests, DIDKit relies on the upstream library. reqwest
checks the environmental variables in DIDKit's environment for the variables HTTP_PROXY
and HTTPS_PROXY
to route http and https traffic, respectively. If you have set up such a proxy, including a reverse proxy or SOCKS service, you can set the appropriate environmental variable(s) and assume reqwest
will route appropriately.
For more information about how reqwest
handles proxies, see the of the reqwest
docs on docs.rs, the Rust ecosystem documentation repository.