diff options
| author |  otofune <otofune@gmail.com> | 2017-12-29 20:16:40 +0000 |
|---|---|---|
| committer | otofune <otofune@gmail.com> | 2017-12-29 20:16:40 +0000 |
| commit | cc57ab5e08c301150fc3d4470c0694043f731e05 (patch) | |
| tree | 2d530b73e34fb5a5c4627fff130edcc66a2f5b47 | |
| parent | 1dfd8746d7a474a60271b7cdc7a8c1b182d03298 (diff) | |
fix PROTOCOL-HTTP2 to PROTOCOL-HTTP2.md
forget .md
| -rw-r--r-- | doc/PROTOCOL-WEB.md | 12 |
1 files changed, 6 insertions, 6 deletions
diff --git a/doc/PROTOCOL-WEB.md b/doc/PROTOCOL-WEB.md index 16ad29321a..c31a048a7c 100644 --- a/doc/PROTOCOL-WEB.md +++ b/doc/PROTOCOL-WEB.md @@ -3,14 +3,14 @@ gRPC-Web provides a JS client library that supports the same API as gRPC-Node to access a gRPC service. Due to browser limitation, the Web client library implements a different protocol than the -[native gRPC protocol](PROTOCOL-HTTP2). +[native gRPC protocol](PROTOCOL-HTTP2.md). This protocol is designed to make it easy for a proxy to translate between the protocols as this is the most likely deployment model. This document lists the differences between the two protocols. To help tracking future revisions, this document describes a delta with the protocol details specified in the -[native gRPC protocol](PROTOCOL-HTTP2). +[native gRPC protocol](PROTOCOL-HTTP2.md). # Design goals @@ -31,7 +31,7 @@ web-specific features such as CORS, XSRF * become optional (in 1-2 years) when browsers are able to speak the native gRPC protocol via the new [whatwg fetch/streams API](https://github.com/whatwg/fetch) -# Protocol differences vs [gRPC over HTTP2](PROTOCOL-HTTP2) +# Protocol differences vs [gRPC over HTTP2](PROTOCOL-HTTP2.md) Content-Type @@ -53,14 +53,14 @@ HTTP wire protocols --- -HTTP/2 related behavior (specified in [gRPC over HTTP2](PROTOCOL-HTTP2)) +HTTP/2 related behavior (specified in [gRPC over HTTP2](PROTOCOL-HTTP2.md)) 1. stream-id is not supported or used 2. go-away is not supported or used --- -Message framing (vs. [http2-transport-mapping](PROTOCOL-HTTP2#http2-transport-mapping)) +Message framing (vs. [http2-transport-mapping](PROTOCOL-HTTP2.md#http2-transport-mapping)) 1. Response status encoded as part of the response body * Key-value pairs encoded as a HTTP/1 headers block (without the terminating newline), per https://tools.ietf.org/html/rfc7230#section-3.2 @@ -86,7 +86,7 @@ in the body. User Agent * Do NOT use User-Agent header (which is to be set by browsers, by default) -* Use X-User-Agent: grpc-web-javascript/0.1 (follow the same format as specified in [gRPC over HTTP2](PROTOCOL-HTTP2)) +* Use X-User-Agent: grpc-web-javascript/0.1 (follow the same format as specified in [gRPC over HTTP2](PROTOCOL-HTTP2.md)) --- |