-
Notifications
You must be signed in to change notification settings - Fork 151
OnHttpRequestBody use DispatchHttpCall error #363
Comments
As I suggested, we need "reproducer" including envoy.yaml. Could you add that here including steps to reproduce? |
This comment was marked as duplicate.
This comment was marked as duplicate.
steps to reproduce? (command line curl snippet!) |
also how to compile? how to run envoy? Could you please add the instruction step by step? That's what "reproducer" and "steps to reproduce" mean in software development. |
This comment was marked as off-topic.
This comment was marked as off-topic.
envoy.yml
main.go
tinygo build -o /tmp/envoy_filter_framework.wasm -scheduler=none -target=wasi ./main.go curl -X GET -H "Content-type: application/json" http://localhost:10000/echo -d '{"aaa":"bbb"}' |
|
Yes, the address exists, I am sure that the error block has not been reached |
i have the same problem... |
ok, this is the expected behavior. the same reason as #364:
tldr is that the original upstream only receives the header, and that cannot be avoided by the current design of Proxy-Wasm. This is not our issue, but rather a universal issue in Proxy-Wasm Spec. |
Describe the bug / error
I have two clusters, a and b, and the default request is to cluster a. I want to forward the request to cluster b in OnHttpRequestBody. I call DispatchHttpCall after EndOfStream=true in OnHttpRequestBody, and then I return types. ActionPause, but it seems that the request has not been aborted. Clusters a and b have received the request respectively
What is your Envoy/Istio version?
v1.21.1
What is the SDK version?
v0.16.1
What is your TinyGo version?
tinygo_0.22.0_amd64
URL or snippet of your code including Envoy configuration
Additional context (Optional)
The text was updated successfully, but these errors were encountered: