From 90e83cd618669f67bc584f6c8817e4da2d1663e3 Mon Sep 17 00:00:00 2001 From: Wenbo Zhu Date: Fri, 31 Jul 2020 15:07:47 -0700 Subject: [PATCH] Update browser-features.md --- doc/browser-features.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/browser-features.md b/doc/browser-features.md index 956d50d..6f1ef45 100644 --- a/doc/browser-features.md +++ b/doc/browser-features.md @@ -6,10 +6,10 @@ The difference between the gRPC-Web protocol and the HTTP/2 based gRPC protocol is specified in the core gRPC repo as [PROTOCOL-WEB](https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-WEB.md). In addition to the wire-transport spec, gRPC-Web also supports features that are unique to browser (HTML) clients. -This document is the official spec for those features. As the Web platform evolves, +This document serves as the official spec for those features. As the Web platform evolves, we expect some of those features will evolve too or become deprecated. -On the server-side, [Envoy](https://www.envoyproxy.io/) is the official proxy with out-of-box gRPC-Web support. New features will be implemented in Envoy first. For [in-process gRPC-Web support](https://github.com/grpc/grpc-web/blob/master/doc/in-process-proxy.md), we recommend the gRPC-Web module implement only a minimum set of features, e.g. to enable local development. Those features are identified as mandatory features in this doc. +On the server-side, [Envoy](https://www.envoyproxy.io/) is the official proxy with built-in gRPC-Web support. New features will be implemented in Envoy first. For [in-process gRPC-Web support](https://github.com/grpc/grpc-web/blob/master/doc/in-process-proxy.md), we recommend that the gRPC-Web module implement only a minimum set of features, e.g. to enable local development. Those features are identified as mandatory features in this doc. # CORS support