This is a surprising / confusing note. Why does Envoy, the gRPC-web recommended proxy, not support server-side streaming in binary, if Nginx is able to?

Yeah, i can agree.. I was just stating the information i gathered, but not trying to reason if it's "expected" or not.. :)

The phrasing here is still confusing, even if it's true - it says only the text format supports streaming, but also that Nginx actually supports streaming regardless of format. If true it would be clearer to say that streaming conceptually works with both formats but the Envoy implementation specifically only supports streaming with the text format.

Yeah i agree with you.. i didn't call out Envoy specifically because it's not the only proxy that supports grpc web.

Let's get a conclusion on the other comment you have, and then i'll update this text.

Neither of these nginx pages mention gRPC-web - are we sure they are referring to gRPC-web and not gRPC?

Hmm, you're right.. i think that's a very good point.. Somehow i thought they were — I probably misread initially. Maybe they are not..

In any case, there are 2 users reporting grpc-web is working, including the OP and this confirmation, and hence i changed the doc.

Maybe i should wait for one extra confirmation on the binary streaming case, but the OP sounded pretty sure in #1391 so i trusted his judgements :)

I'm pretty suspicious these threads are not consistently distinguishing gRPC traffic from gRPC-web. For example application/grpc is clearly not gRPC-web. Furthermore, it seems unlikely that Nginx has somehow managed to enable streaming support for the gRPC-web binary format when your understanding was the binary format is incapable of supporting server-side streaming.

More to the point, it's impossible for Nginx to have enabled streaming support for the gRPC-web binary format without collaborating with the gRPC-web project, because the protocol spec directly says this is not supported. So if they have implemented some sort of streaming support it's not to spec.

But my bet (especially given the lack of any mention of gRPC-web in their documentation) is Nginx supports gRPC, and people are conflating it with gRPC-web because it's a "web" server that's able to proxy gRPC traffic.

I'm pretty suspicious these threads are not consistently distinguishing gRPC traffic from gRPC-web. For example application/grpc is clearly not gRPC-web.

Yeah i can see your suspicion. I don't deny them.

Furthermore, it seems unlikely that Nginx has somehow managed to enable streaming support for the gRPC-web binary format when your understanding was the binary format is incapable of supporting server-side streaming.

This is a very good point.. thanks for pointing it out :)

More to the point, it's impossible for Nginx to have enabled streaming support for the gRPC-web binary format without collaborating with the gRPC-web project, because the protocol spec directly says this is not supported. So if they have implemented some sort of streaming support it's not to spec.

Yes another very good point.

But my bet (especially given the lack of any mention of gRPC-web in their documentation) is Nginx supports gRPC, and people are conflating it with gRPC-web because it's a "web" server that's able to proxy gRPC traffic.

Yes it's definitely a possibility. Let me loop in the original commenters.

@jmzwcn @zhumazhenis Hi! Thanks for previously participating in the discussion on nginx support.

There's a question now on the validity of the conclusions as above.

Could you help responding to it if there are some misunderstandings?

Thanks in advance!

@sampajano any objection to reverting these notes? At best they're unclear and IMO it would be better to remove them and hash out exactly what is known before re-adding them.

OK! Since the original commenters are not active at this point, i guess we can revert until upon further discussions :)

Do you want to create a PR to revert this one? Or if you prefer i can do it too.

Thanks! :)

Thanks, just cut #1408