Icx-proxy unknown TLS backend

[cryptoschindler]

hey, those two threads should help:

Could not create HTTP client

I tried to run the icx-proxy but received the following error after a GET request. ❯ icx-proxy version: 0.7.0 Dec 19 13:20:19.319 INFO Log Level: INFO Dec 19 13:20:19.319 INFO Starting server. Listening on http://127.0.0.1:3000/ thread 'tokio-runtime-worker' panicked at 'Could not create HTTP client.: reqwest::Error { kind: Builder, source: "Unknown TLS backend passed to `use_preconfigured_tls`" }', /Users/moritz/.cargo/registry/src/github.com-1ecc6299db9ec823/ic-agent-0.9.0/src/agent/http_tr…

Icx-proxy shipped with dfx?

i read a couple of posts here that suggested to run icx-proxy locally to access for example an asset in an asset canister through the http interface. but it seems like icx-proxy is already running with dfx start as the name of the terminal window suggests and also the fact that one can access assets using this URL format http://localhost:8000/<your_asset_path>?canisterId=<your_canister_id> so my question would be if this is a new change to dfx or if you have any other advantages if you run an…