| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
forget .md
|
| | |
|
| | |
|
| |
|
| |
Remove the section for b64 encoded trailers. As gRPC-Web uses CRLF to separate the trailers in the trailers frame, a binary trailer need to reserve in a base64 encoded format for their values. This cannot be skipped even base64 is applied on the whole trailers frame per client's request via content-type: application/grpc-web-text.
|
| | |
|
| | |
|
| |
|
| |
Clarify the content type requirement (for message formats).
|
| | |
|
| |
|
| |
Clarify the use of U-A header.
|
| |
|
| |
Remove text-base64 C-T. Will revisit if we ever need support non-default (base64) encoding.
|
| | |
|
| | |
|
| |
|
|
|
| |
Addressed @mwitkow comments.
https://github.com/grpc/grpc-web/issues/57
|
| |
|
| |
Mention the Server header format
|
| |
|
|
|
| |
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)
|
| |
|
| |
Using http/2 literal header format for status.
|
| |
|
otofune
Mehrdad Afshari
Feng Li
Wenbo Zhu
Alexander Polcyn