From 981201fc5edc34a518d5c57f3cb3ccd873615f91 Mon Sep 17 00:00:00 2001
From: Eric Anderson <ejona@google.com>
Date: Wed, 4 Nov 2015 15:47:54 -0800
Subject: [PATCH] Content-type is required for requests
This fixes grpc/grpc-common#185
---
doc/PROTOCOL-HTTP2.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/PROTOCOL-HTTP2.md b/doc/PROTOCOL-HTTP2.md
index 510d3cadbd..80754143d5 100644
--- a/doc/PROTOCOL-HTTP2.md
+++ b/doc/PROTOCOL-HTTP2.md
@@ -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** → Call-Definition \*Custom-Metadata
-* **Call-Definition** → Method Scheme Path TE [Authority] [Timeout] [Content-Type] [Message-Type] [Message-Encoding] [Message-Accept-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"
* **Scheme** → ":scheme " ("http" / "https")
* **Path** → ":path" {_path identifying method within exposed API_}
--
GitLab