Passing metadata through proxy?

[endpress]

I am using grpcwebproxy. My backend server is a node js grpc server. I want pass metadata through grpc-web-client.

  const testRequest = new TestRequest();
  testRequest.setUserId('testuserid');

  grpc.unary(MeetService.testHistory, {
    request: testRequest,
    host: host,
    debug: true,
    metadata: {test_token: 'xxxxxxxxxxx'},
    onEnd: res => {
      const { status, statusMessage, headers, message, trailers } = res;
      if (status === Code.OK && message) {
        // console.log('meetHistory.onEnd.message', message.toObject());
      }
      // console.log('meetHistory.onEnd.trailers', trailers);
    }
  });

But my node server cannot get metadata. It only can get a user-agent metadata.

Metadata { _internal_repr: { 'user-agent': [ 'grpc-go/1.7.0-dev' ] } }
ServerUnaryCall {
  domain: null,
  _events: { error: [Function] },
  _eventsCount: 1,
  _maxListeners: undefined,
  call: Call {},
  cancelled: false,
  metadata: Metadata { _internal_repr: { 'user-agent': [Array] } },
  request: 
   { wrappers_: null,
     messageId_: undefined,
     arrayIndexOffset_: -1,
     array: [ 'testuserid' ],
     pivot_: 1.7976931348623157e+308,
     convertedFloatingPointFields_: {} } }

[endpress]

My grpc-web-client version is "grpc-web-client": "^0.3.1",

[ypoluektovich]

I'm seeing the same problem. The go proxy thing seems to be swallowing metadata/headers.

[suusan2go]

I have the same problem. My backend server is a SpringBoot server(with grpc-java using Kotlin.)

[mwitkow]

Indeed. The previous code of grpc-proxy, that the current grpc-webproxy relies on, relied on the implicit forwarding of metadata inside the context.Context between gRPC-Go calls. This behaviour has changed in gRPC-Go 1.5.

The fix requires a change to upstream grpc-go and is discussed in
mwitkow/grpc-proxy#19

[MarcusLongmuir]

@endpress / @ypoluektovich / @suusan2go: Please re-open if latest master does not fix the issue you're seeing.

[ypoluektovich]

It does for me. Thanks!