diff options
| author |  Wenbo Zhu <wenboz@google.com> | 2017-02-06 14:23:03 -0800 |
|---|---|---|
| committer |  GitHub <noreply@github.com> | 2017-02-06 14:23:03 -0800 |
| commit | e5cf8f0ee0d5915e4c37a560106010e9e6f9b396 (patch) | |
| tree | 27085da02c79d7a8c859d6b910022acbc44dba0d /doc/PROTOCOL-WEB.md | |
| parent | d6d2677637fee5d2988dae08cee1b909d822c650 (diff) | |
Update PROTOCOL-WEB.md
1. Clarify about trailer-only responses
2. Switch to http/1.1 header block format for in-body trailer encoding
3. Clarify how compatibility is supported (using U-A and Server headers respectively)
Diffstat (limited to 'doc/PROTOCOL-WEB.md')
| -rw-r--r-- | doc/PROTOCOL-WEB.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/PROTOCOL-WEB.md b/doc/PROTOCOL-WEB.md index 562d5999cf..0fc1899b38 100644 --- a/doc/PROTOCOL-WEB.md +++ b/doc/PROTOCOL-WEB.md @@ -60,14 +60,14 @@ HTTP/2 related behavior (specified in [gRPC over HTTP2](http://www.grpc.io/docs/ Message framing (vs. [http2-transport-mapping](http://www.grpc.io/docs/guides/wire.html#http2-transport-mapping)) 1. Response status encoded as part of the response body - * Key-value pairs encoded in the HTTP/2 [literal header format](https://tools.ietf.org/html/rfc7541#section-6.2) as a single header block. + * Key-value pairs encoded as a HTTP/1 headers block (without the terminating newline). 2. 8th (MSB) bit of the 1st gRPC frame byte * 0: data * 1: trailers 3. Trailers must be the last message of the response, as enforced by the implementation 4. Trailers-only responses: no change to the gRPC protocol spec. -Trailers will be sent together with response headers, with no message +Trailers may be sent together with response headers, with no message in the body. --- |