You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The on_http_call_response() callback is sporadically not invoked on requests containing a body. The issue is NOT reproducible on requests WITHOUT body.
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 paused. This was fixed a few days ago in proxy-wasm/proxy-wasm-cpp-host#95 and envoyproxy/envoy#13840.
Summary:
The on_http_call_response() callback is sporadically not invoked on requests containing a body. The issue is NOT reproducible on requests WITHOUT body.
MCVE
Sample envoy configuration (can be reproduced on istio as well)
As the requestbin is not publicly visible you'll have to create your own and update the configuration accordingly.
Steps to reproduce
I'm reproducing it in a docker image (thus the localhost address), but can be done also on k8s with istio.
Make a POST request containing some body. It can be as simple as a single character
Expectation
On envoy side
I expect to see in the logs that both of my callbacks have been invoked. Example:
On requestbin side
All of the
x-wasm-marker
header values are present. Example:What actually happens
On envoy side
Sometimes both callbacks are called, sometimes only the first one and sometimes no callback is invoked:
Note that we can see from the log that the second call was successfully dispatched, but the callback was never called.
On requestbin side
Some/All of the expected
x-wasm-marker
header values are missingWithout a request body
If you make the same request but without the body:
The issue is NOT reproducible and works as expected 100% of the trials
The text was updated successfully, but these errors were encountered: