Stanley Cheung

Have you added your custom header to your `envoy.yaml` file like this? https://github.com/grpc/grpc-web/blob/master/net/grpc/gateway/examples/echo/envoy.yaml#L34 (and L32). By default, browsers don't allow custom headers to be accessed unless the header is explicitly...

Can you give us more information please? There is not enough information to go on.

Would help if there's a simple reproducible test case that I can clone, launch a docker image or something and reproduce the error. Or is there a special situation that...

Perhaps these examples may help? https://github.com/salrashid123/grpc_web_with_gke https://github.com/salrashid123/gcegrpc/

One reason why your Python server might not be receiving the requests could be because of how we set up the basic example. So here https://github.com/grpc/grpc-web/tree/master/net/grpc/gateway/examples/echo#run-the-envoy-proxy, you will notice that,...

In that case, when you run the Envoy container, did you try adding `--network=host` to the `docker run` command? So you are saying that this `envoy.yaml` file works fine when...

If your example works end-to-end with a Node server, then it seems that your Envoy instance (and the forwarding) is done correctly. So it seems that the issue may be...

The `host.docker.internal` address to be used inside a docker container is my understanding too. So you seem to be doing the correct thing here. I am at a loss here...

Just shooting in the dark here: if you are also swapping the service, perhaps you also have to match these lines? https://github.com/grpc/grpc-web/blob/master/net/grpc/gateway/examples/echo/envoy.yaml#L24-L26 Is the Envoy cluster name also matching up...

For this one, you probably need to modify the unit test to expect this new header too https://github.com/grpc/grpc-web/blob/master/javascript/net/grpc/web/grpcwebclientbase_test.js#L34-L39