OnHttpRequestBody is not called when calling a `direct_response` route about proxy-wasm-go-sdk HOT 5 CLOSED

AFAIR direct response is actually a filter and hence it avoids the filterchain (hence any other filter). We faced something like that (I think context can be found in corazawaf/coraza-proxy-wasm#172) so I am not sure this is a bug.

from proxy-wasm-go-sdk.

Ah! Ok, then is there somewhere we can document this behaviour? Thankfully for me it's not something that I actually need but it did make me very confused when I was extending one of the examples which use direct_response

from proxy-wasm-go-sdk.

not the issue/bug/documentation matter of this SDK, but it's an expected behavior of Envoy, so closing.

from proxy-wasm-go-sdk.

@mathetake I'm not quite sure why this is expected behaviour as OnHttpRequestHeaders is called and this is using a direct response route action rather than a direct response network filter:

https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-msg-config-route-v3-directresponseaction
https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/network_filters/direct_response_filter

It would make more sense to me if OnHttpRequestHeaders was not called too.

The logs from my example linked above:

[2023-11-06 22:23:37.315][123297][info][wasm] [source/extensions/common/wasm/context.cc:1171] wasm log: OnHttpRequestHeaders
[2023-11-06 22:23:37.315][123297][info][wasm] [source/extensions/common/wasm/context.cc:1171] wasm log: OnHttpResponseHeaders
[2023-11-06 22:23:37.315][123297][info][wasm] [source/extensions/common/wasm/context.cc:1171] wasm log: OnHttpResponseBody

from proxy-wasm-go-sdk.

As I said this is the known behavior of Envoy, nothing to do with SDK.

from proxy-wasm-go-sdk.