joseret

Any news on this? or workaround?

ping. Anyone have some thoughts on this?

Thanks! Yes, that works for me too. But I need the initial on_http_response_body to retrieve some information used on the dispatch call and that is where I am stuck and...

I am issuing thee HTTP dispatch in the on_http_response_body (not in the on_http_request_body so how do I receive the response_body, then do dispatch, and from on_response_call_body modify the response_body going...

Great news, let me try that. I thought I removed the content-length but will make sure and post logs On Wed, Jun 22, 2022 at 7:28 AM Francisco Camenforte Torres...

Great to hear. I thought I remove content header on the response_header but will make suree

This is similar error, there is no content-length header, so set_request_headers fail [2022-06-22 22:52:17.219][516433][critical][wasm] [external/envoy/source/extensions/common/wasm/context.cc:1227] wasm log my_plugin my_root_id my_vm_id: panicked at 'unexpected status: 2', /home/jr/.cargo/registry/src/github.com-1ecc6299db9ec823/proxy-wasm-0.1.4/src/hostcalls.rs:211:23 [2022-06-22 22:52:17.219][516433][error][wasm] [external/envoy/source/extensions/common/wasm/wasm_vm.cc:39] Function:...

[error.log](https://github.com/proxy-wasm/proxy-wasm-rust-sdk/files/8962311/error.log) Here is the trace