Issue connecting with Google gRPC APIs about tonic

[LucioFranco]

Ok I dug into this and got it working if I change the content type to application/grpc from application/grpc+proto which doesn't make much sense. I will dig in a bit more into this...

[LucioFranco]

@Hirevo just for more debugging purposes by chance could you see what the headers are that gcp returns to you?

So I know we don't quite yet support compression but I am curious if we can disable it.

[LucioFranco]

And also since you have an interceptor does changing it to this work?

        .intercept_headers(|headers| {
            let token = "some-valid-google-oauth-token";
            let value = format!("Bearer {0}", token);
            let value = HeaderValue::from_str(value.as_str()).unwrap();
            headers.insert("authorization", value);
			headers.insert("grpc-accept-encoding", HeaderValue::from_str("identity").unwrap());
        })

The docs are not clear specifically if this will work but pretty much for now we need to tell their grpc server that we don't accept any compression.

[Hirevo]

@LucioFranco Yes, here are the response headers that the Go code received for the gRPC call:

metadata.MD{
    "alt-svc":[]string{
        "quic=\":443\"; ma=2592000; v=\"46,43\",h3-Q048=\":443\"; ma=2592000,h3-Q046=\":443\"; ma=2592000,h3-Q043=\":443\"; ma=2592000"
    },
    "content-disposition":[]string{"attachment"},
    "content-type":[]string{"application/grpc"},
    "date":[]string{"Mon, 28 Oct 2019 21:12:24 GMT"}
}

I have also just tried the additional header you proposed, but the error has not changed, sadly.

Also, I published both the Rust and Go versions of these tests, with the same setup and crate versions that I have:
Rust: https://github.com/Hirevo/rust-gcp-test
Go: https://github.com/Hirevo/go-gcp-test

[peter05010402]

I got the same Err!

[LucioFranco]

@peter05010402 what version of tonic are you using?

[frostRed]

I also had the same Error when using grpc steram rpc. It doesn't have the error at program startup but occurs at many minutes after. Then I re-connect to the grpc server and the error is gone but many minutes it will come again.

The server side is golang. And I tried tonic 0.2 and 0.3.1, not change anything.

[LucioFranco]

@frostRed you are getting the "unexpected compression flag error" after startup? Usually this only happens when you have an incorrectly configured channel. value 60 for this flag isn't even valid iirc.

[frostRed]

No, after startup everything is ok, it only occurs on after running half hour or longer.

[LucioFranco]

Not startup for the process but for the connection? If that is still the issue something that can reproduce this or that we can inspect the frames would be very helpful.

[xiaochuanyu]

I arrived here googling "invalid compression flag: 60" and found out that I get a similar error message if I use the wrong endpoint URL e.g. using pubsub URL for endpoint with firestore client.
Its a stupid mistake while copy pasting from gcp example but error message is a little cryptic.

    const ENDPOINT: &str = "https://pubsub.googleapis.com";  // wrong endpoint
    let token = "some valid token";
    let token_metadata: MetadataValue<_> = format!("Bearer {}", token).parse().unwrap();

    let channel = Channel::from_static(ENDPOINT)
        .connect()
        .await.unwrap();

    let mut client = FirestoreClient::with_interceptor(channel, move |mut req: Request<()>| {
        req.metadata_mut()
            .insert("authorization", token_metadata.clone());
        Ok(req)
    });
    // ...

Response struct I get if I call client.create_document(...):

Status {
code:
  Internal,
  message: "protocol error: received message with invalid compression flag: 60 (valid flags are 0 and 1) while receiving response with status: 404 Not Found",
  metadata: MetadataMap{
    headers: {
      "date": "Sun, 24 Jul 2022 14:57:20 GMT",
      "content-type": "text/html; charset=UTF-8",
      "server": "ESF",
      "content-length": "1605",
      "x-xss-protection": "0",
      "x-frame-options": "SAMEORIGIN",
      "x-content-type-options": "nosniff",
      "alt-svc": "h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000,h3-Q050=\":443\"; ma=2592000,h3-Q046=\":443\"; ma=2592000,h3-Q043=\":443\"; ma=2592000,quic=\":443\"; ma=2592000; v=\"46,43\""
    }
  },
  source: None
}

[LucioFranco]

This is because google's api is talking http3 and not http2. There could be a few reasons but maybe the way alpn is negotated is't working. Not totally sure what they changed and maybe the example doesn't work anymore?