tedli
tedli
@gggin If you use the microhttpd backend (mhd_), you are already bound to 0.0.0.0. However if you want to bind it to a specific IP address rather than 0.0.0.0, I...
> @tedli could you please rebase this on master or release-1.15? Hi craigbox, Thanks for reply. I cherry-picked this to master and release-1.15. Please have a look. https://github.com/istio/istio.io/pull/11892 https://github.com/istio/istio.io/pull/11891
`go.mod` is not been committed. Still waiting `mosn.io/pkg` be merged.
~~Up to now, my code confirmed works. It has to add code in router, because there could access decode invocation.~~ ~~I wrote a [memo](https://lz8888.gitee.io/post/envoy-dubbo-tracing), describing the problem I'm facing.~~ ~~I...
**Demo:** ```yaml node: id: dev cluster: dev admin: address: socket_address: protocol: TCP address: 127.0.0.1 port_value: 15000 static_resources: listeners: - name: dubbo address: socket_address: address: 0.0.0.0 port_value: 30880 filter_chains: - filters:...
> Thanks for you contribution. But if I miss something? Where is the new proto API for the dubbo tracing? > > And there are some exist tracers which are...
> 1. IMO, it's OK to resue the `HttpConnectionManager.Tracing` for learning or private extension, because it just work. But if we want make this extension be part of core envoy,...
> Looks like this still needs a format fix. > > /wait Yes. It's unfinished, I forget to convert to draft. As [wbpcode](https://github.com/wbpcode) said, it's better to introduce a tracing...