Skip to content
Snippets Groups Projects
Commit 33651387 authored by David G. Quintas's avatar David G. Quintas
Browse files

Changes from PR comments.

parent 0ff9221a
No related branches found
No related tags found
No related merge requests found
...@@ -21,7 +21,7 @@ The following is the general sequence of message atoms in a GRPC request & respo ...@@ -21,7 +21,7 @@ The following is the general sequence of message atoms in a GRPC request & respo
Request-Headers are delivered as HTTP2 headers in HEADERS + CONTINUATION frames. Request-Headers are delivered as HTTP2 headers in HEADERS + CONTINUATION frames.
* **Request-Headers** → Call-Definition *Custom-Metadata * **Request-Headers** → Call-Definition *Custom-Metadata
* **Call-Definition** → Method Scheme Path TE [Authority] [Timeout] [Content-Type] [Message-Type] [Message-Encoding] [User-Agent] * **Call-Definition** → Method Scheme Path TE [Authority] [Timeout] [Content-Type] [Message-Type] [Message-Encoding] [Message-Accept-Encoding] [User-Agent]
* **Method** → “:method POST” * **Method** → “:method POST”
* **Scheme** → “:scheme ” (“http” / “https”) * **Scheme** → “:scheme ” (“http” / “https”)
* **Path** → “:path” {_path identifying method within exposed API_} * **Path** → “:path” {_path identifying method within exposed API_}
...@@ -37,9 +37,9 @@ Request-Headers are delivered as HTTP2 headers in HEADERS + CONTINUATION frames. ...@@ -37,9 +37,9 @@ Request-Headers are delivered as HTTP2 headers in HEADERS + CONTINUATION frames.
* **Microsecond** → “u” * **Microsecond** → “u”
* **Nanosecond** → “n” * **Nanosecond** → “n”
* **Content-Type** → “content-type” “application/grpc” [(“+proto” / “+json” / {_custom_})] * **Content-Type** → “content-type” “application/grpc” [(“+proto” / “+json” / {_custom_})]
* **Message-Encoding** → “grpc-encoding” (“gzip” / “deflate” / “snappy” / {_custom_} ) * **Content-Coding**“gzip” / “deflate” / “snappy” / {_custom_}
* **Message-Accept-Encoding** → “grpc-accept-encoding” {_comma-separated list of * **Message-Encoding** → “grpc-encoding” Content-Coding
zero or more of (“gzip” / “deflate” / “snappy” / {_custom_})} * **Message-Accept-Encoding** → “grpc-accept-encoding” Content-Coding *("," Content-Coding)
* **User-Agent** → “user-agent” {_structured user-agent string_} * **User-Agent** → “user-agent” {_structured user-agent string_}
* **Message-Type** → “grpc-message-type” {_type name for message schema_} * **Message-Type** → “grpc-message-type” {_type name for message schema_}
* **Custom-Metadata** → Binary-Header / ASCII-Header * **Custom-Metadata** → Binary-Header / ASCII-Header
...@@ -69,7 +69,7 @@ For requests, **EOS** (end-of-stream) is indicated by the presence of the END_ST ...@@ -69,7 +69,7 @@ For requests, **EOS** (end-of-stream) is indicated by the presence of the END_ST
###Responses ###Responses
* **Response** → (Response-Headers *Delimited-Message Trailers) / Trailers-Only * **Response** → (Response-Headers *Delimited-Message Trailers) / Trailers-Only
* **Response-Headers** → HTTP-Status [Message-Encoding] Content-Type *Custom-Metadata * **Response-Headers** → HTTP-Status [Message-Encoding] [Message-Accept-Encoding] Content-Type *Custom-Metadata
* **Trailers-Only** → HTTP-Status Content-Type Trailers * **Trailers-Only** → HTTP-Status Content-Type Trailers
* **Trailers** → Status [Status-Message] *Custom-Metadata * **Trailers** → Status [Status-Message] *Custom-Metadata
* **HTTP-Status** → “:status 200” * **HTTP-Status** → “:status 200”
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment