Piotr Sikora

Did you try `on_log` or `on_done`?

`on_vm_start` is called by the "canary" instance that's instantiating the plugin to check if the configuration is valid, and it's discarded afterwards.

> Is there any way I can differentiate between these two flows in `on_vm_start`? Unfortunately, currently it's not (I agree that's not great). Note that both canary and "regular" plugin...

> Is the `on_configure` called as well in that process? Yes.

The first link serves content again, although with TLS certificate for `*.github.com`. cc @antweiss The second link is updated in https://github.com/proxy-wasm/proxy-wasm-rust-sdk/pull/169.

It possible to make HTTP calls (see: [examples/http_auth_random.rs](https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/master/examples/http_auth_random.rs)), but not using `reqwest::blocking::Client`.

Are you building it against `wasm32-wasi` target?

Is there any reason for using `wasm-pack` in the first place? See the previous discussion: https://github.com/proxy-wasm/proxy-wasm-rust-sdk/issues/149#issuecomment-1200824021.

You could do it in the `on_log` callback.

`on_http_call_response` contains `token_id` which should match the returned `token_id` from `dispatch_http_call`. Is that not the case?