Piotr Sikora

You aren't expected to use `reqwest` (which I suspect is the source of bindgen the issue) to make outgoing calls, this SDK provides dedicated functions to do that (`dispatch_http_call`, see:...

I cannot replicate this issue, everything seems to work fine and the whole header map is replaced with the provided values. Do you have any code snippet or example that...

> @PiotrSikora PTAL. While it's not encouraged but we do have certain traffic contains non UTF-8 header value. Since spec allows it historically, we shouldn't block that. This is actually...

Hi @unleashed! Sorry, I've missed the email notifications for your PRs. Is this only a "style rewrite" of what was already implemented in #34, or am I missing something? In...

> I've also looked a bit in the [spec](https://github.com/proxy-wasm/spec/tree/master/abi-versions/vNEXT#proxy_dispatch_grpc_call), in which the `upstream` argument is called `grpc_service` (hinting the use of formentioned GrpcService message), but in [your PR](https://github.com/proxy-wasm/spec/pull/1#discussion_r473200070), this argument...

Are you testing with latest Envoy? I think you might be hitting the same issue as we discussed in #43, i.e. request body is being processed even when headers are...

> Proxy-Wasm is irrelevant to WASI (at least as of preview1), and this spec repository is only about these Proxy specific functions, etc. How WASI will be exposed to the...

You could have separate singleton background service that fetches and updates data in key-value store, and workers could then read shared data from that key-value store.

Please take a look, I'm sure there are some errors, but it should be fairly complete. I'll wait a week or two before merging this to make sure all mistakes...

> @PiotrSikora any update on when this might be merged? I'll try to wrap this this week.