code

Another interesting thing is the old version "https://github.com/hedronvision/bazel-compile-commands-extractor/archive/dc36e462a2468bd79843fe5176542883b8ce4abe.tar.gz" could generate a compile_commands.json. Although even I pre-build the lib/binnary, there are still some files are missing and make the clangd connot...

@PiotrSikora I personally think automatic clearing is not a good choice in practice. We may change the host, path, headers in a filter because various reasons (for example, rewrite the...

> > The correct way is to clear the route cache only when it's required explicitly. (Most envoy filters work as this way, except wasm and lua now.) > >...

@leonm1 yeah, you are right 👍

Basically, I think keep the same default behavior with envoy is good enough. But at least a control flag is better than no control anyway.

I will try to remove the automatic refresh in the Envoy's implementation and add the foreign functions to clear the route cache. By this way, the wasm plugin could get...

If we hope the wasm extension has similar experience with the native one, then the framework shouldn't provide any automatical refresh. It should only be decided by the plugin configuration...

Is it possible to bring the `proxy_clear_route_cache` back? And we can also add the stop iteration support back. All these changes could be placed in a new ABI version? Or...

> If you look at those two, then Lua always clears route cache when HTTP headers are modified (same as Wasm), and ext_proc is clearing it by default (again, same...

We will disable the auto route clear after the abi 0.3.0