5 ms·
Nifty. I assume this still means using some combination of Envoy + Nginx to "downgrade" to 1.1 in a traditional web service environment if the client defaults t
by languagehacker 5y ago
Nifty. I assume this still means using some combination of Envoy + Nginx to "downgrade" to 1.1 in a traditional web service environment if the client defaults to HTTP/2. Is that right?
- no_circuit 5y agogRPC is HTTP/2. I'd say its more of a situation that you need to "upgrade" 1.1 clients. See https://www.envoyproxy.io/docs/envoy/v1.17.4/configuration/http/http_filters/grpc_json_transcoder_filter#config-http-filters-grpc-json-transcoder https://www.envoyproxy.io/docs/envoy/v1.17.4/configuration/h.... NGINX isn't necessary unless you need it in addition for some connection handling / performance concerns. Otherwise the gRPC handling I believe is best with just Envoy alone.
- __alexs 5y agoI don't think there is actually a good solution for connecting a regular H2 gRPC client to a gRPC-Web server currently. Envoy's gRPC-Web filter only seems to go the other way. I haven't tested it but the old HTTP/1.1 reverse bridge might work. [0] [0] https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_http1_reverse_bridge_filter https://www.envoyproxy.io/docs/envoy/latest/configuration/ht...