Not getting a proper base64 encoded response, but "content-type:application/x-protobuf" instead about grpc-web

[fengli79]

Could you share us the browser's version? It's possible that the browser filter out the content-transfer-encoding header.
We already noticed that, and it's get resolved by #68 and #71
Please sync to the head and give a try.

[sulliwane]

Here are the browsers I tested (on local Ubuntu 16.04, requesting the remote nginx gateway on Centos7):

• Chromium Version 56.0.2924.76 Built on Ubuntu , running on Ubuntu 16.04 (64-bit) NOT OK
• Chrome Version 57.0.2987.98 (64-bit) NOT OK
• Firefox 52.0.1 (64-bit) OK

Note: I'm not using the docker images (always stuck at compilation time) so I follow the "manual mode" detailed here. This may be the problem, as my git submodules may not be checked out at the proper commit, if the manual guide instructions are not kept in sync with the docker script.

This time, on my remote Centos7 machine, I first executed ./init_submodules.sh and recompiled nginx-gateway, but still the same problem.

thanks for your help

[fengli79]

It's not about the submodules, it's for the grpc/grpc-web itself, did you sync to the head?

[stanley-cheung]

Yes this is a good doc to follow to build the example.

And can you execute this in the root directory of your grpc-web repo? git log -1 --oneline

[sulliwane]

I misunderstood, I thought it was a problem with nginx-gateway.

cd grpc-web
git pull  # my local repo was indeed not up to date
git log -1 --oneline
8230b9b Merge pull request #86 from stanley-cheung/master

So now I just reproduced my JS bundle:

cd javascript/net/grpc/web && make # maybe not needed
protoc -I=. --js_out=import_style=closure,binary:. ./myProto.proto  # JS Messages definitions
protoc -I=. --plugin=protoc-gen-grpc-web=<path to plugin> \
  --grpc-web_out=out=echo.grpc.pb.js,mode=base64:. ./myProto.proto # JS Stub definition
./third_party/closure-library/closure/bin/build/closurebuilder.py # cosurebuilder, with all the roots to the newly generated JS + required libraries

Opening the browser, and testing again against my remote nginx-gateway (which I had recompiled before), bam it worked!!!

But then the problem appeared when hitting my local nginx-gateway. So I recompiled the local nginx-gateway, and it solved the problem. So not only the JS had to be updated, but the nginx-gateway had to be recompiled.

Side note: I noticed that the client service methods naming convention changed (it's now lowercase for the first letter, which makes more sense on the JS standpoint, and is harmonized with the grpc-node naming convention) 👍 .

[stanley-cheung]

Yes, I remember the fix where we lowercase the first letter of the RPC method name. It was quite recent. We have made tons of changes recently, both on the gateway side and the JS client side so yes it's expected that you need to re-compile both the gateway and the JS client.

Glad that it works for you now!