aboutsummaryrefslogtreecommitdiffhomepage
path: root/doc/PROTOCOL-WEB.md
diff options
context:
space:
mode:
authorGravatar Craig Tiller <ctiller@google.com>2017-05-30 12:51:19 -0700
committerGravatar Craig Tiller <ctiller@google.com>2017-05-30 12:51:19 -0700
commitaec8f5ecde4a3b31ea8ca12a1b011d140effe4ee (patch)
treecbe79fa8e925318250046e4bd204c378907bbd91 /doc/PROTOCOL-WEB.md
parente54eb13ed715f747272b14537be20622f6f72473 (diff)
parent4ff23545807802f177b2e90c4c4517d8c2cb224e (diff)
Merge github.com:grpc/grpc into selectivity
Diffstat (limited to 'doc/PROTOCOL-WEB.md')
-rw-r--r--doc/PROTOCOL-WEB.md4
1 files changed, 0 insertions, 4 deletions
diff --git a/doc/PROTOCOL-WEB.md b/doc/PROTOCOL-WEB.md
index 10998899c4..912dbe6d8f 100644
--- a/doc/PROTOCOL-WEB.md
+++ b/doc/PROTOCOL-WEB.md
@@ -103,10 +103,6 @@ to security policies with XHR
* While the server runtime will always base64-encode and flush gRPC messages
atomically the client library should not assume base64 padding always
happens at the boundary of message frames. That is, the implementation may send base64-encoded "chunks" with potential padding whenever the runtime needs to flush a byte buffer.
-3. For binary trailers, when the content-type is set to
-application/grpc-web-text, the extra base64 encoding specified
-in [gRPC over HTTP2](http://www.grpc.io/docs/guides/wire.html)
-for binary custom metadata is skipped.
# Other features