-
The current HTTP Wasm filter is there around 4+ years. This issue is going to track and gather info until which state we think it is reasonable to move out of alpha to `stable` based on this [extensio…
-
Originally reported by @teb510
> i can grab the response from headers from a callnode - but the filter seems to bomb with headers that are multiple words connected by a "-" - downcasing/snakecasi…
-
*Title*: Envoy Proxy extension with Hyperlight micro-VMs
*Description*:
>Envoy Proxy allows certain extension points like Go filters, WASM, etc. With the recent release of https://github.com/hyper…
-
### Is this the right place to submit this?
- [X] This is not a security vulnerability or a crashing bug
- [X] This is not a question about how to use Istio
### Bug Description
When Istio pushed wa…
-
*Title*: *Envoy WASM extensions in the present and its future (Proxy-Wasm)*
*Description*:
Envoy current supports WASM extensions via the [WASM filter](https://www.envoyproxy.io/docs/envoy/v1.31…
-
Currently, we only support `Continue` and `Pause` actions, which is quite limiting.
Most notably, we require forwarding HTTP headers before processing HTTP body, which prevents building plugins tha…
-
When expression is something like:
```yaml
expression:
key: "a"
value: "unknown.path"
```
The wasm panics. Envoy's logs show
```
envoy-1 | [2024-11-08 15:00:30.432][61][debug][wasm] […
-
### Describe the issue
I get the following error when using `onnxruntime-web` on Next.js with web workers:
- `Error: no available backend found. ERR: [wasm] TypeError: Failed to fetch, [cpu] Error: …
-
## What is the problem your feature solves, or the need it fulfills?
[Proxy WASM](https://github.com/proxy-wasm/spec) is an spec that allows HTTP filters to be implemented in WASM (supported in Env…
-
### Use case
support web assembly version of tailscale client connect to headscale controller
### Description
wasm tailscale client is from [tailscale/tsconnect](https://github.com/tailscale/tailsc…