From 6ba920a573da4a7eeec4b47e73104e2bfaff4d5c Mon Sep 17 00:00:00 2001 From: Menghan Li Date: Fri, 24 Apr 2020 09:54:54 -0700 Subject: [PATCH 1/2] doc: clarify that gRPC paths are case-sensitive --- 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 aa0e1aba8f5..a5dbf5f5cfc 100644 --- a/doc/PROTOCOL-HTTP2.md +++ b/doc/PROTOCOL-HTTP2.md @@ -57,7 +57,7 @@ to be overridden, but this functionality is strongly discouraged. gRPC does not go out of its way to break users that are using this kind of override, but we do not actively support it, and some functionality (e.g., service config support) will not work when the path is not of -the form shown above. +the form shown above. Also note that path is case-sensitive. If **Timeout** is omitted a server should assume an infinite timeout. Client implementations are free to send a default minimum timeout based on their deployment requirements. From 5b7aa136ab69d9072d9e58da2ec6e99d585a62fc Mon Sep 17 00:00:00 2001 From: Menghan Li Date: Fri, 24 Apr 2020 18:00:56 -0700 Subject: [PATCH 2/2] move --- doc/PROTOCOL-HTTP2.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/PROTOCOL-HTTP2.md b/doc/PROTOCOL-HTTP2.md index a5dbf5f5cfc..261e76f8509 100644 --- a/doc/PROTOCOL-HTTP2.md +++ b/doc/PROTOCOL-HTTP2.md @@ -52,12 +52,12 @@ Request-Headers are delivered as HTTP2 headers in HEADERS + CONTINUATION frames. HTTP2 requires that reserved headers, ones starting with ":" appear before all other headers. Additionally implementations should send **Timeout** immediately after the reserved headers and they should send the **Call-Definition** headers before sending **Custom-Metadata**. -Some gRPC implementations may allow the **Path** format shown above -to be overridden, but this functionality is strongly discouraged. -gRPC does not go out of its way to break users that are using this kind -of override, but we do not actively support it, and some functionality -(e.g., service config support) will not work when the path is not of -the form shown above. Also note that path is case-sensitive. +**Path** is case-sensitive. Some gRPC implementations may allow the **Path** +format shown above to be overridden, but this functionality is strongly +discouraged. gRPC does not go out of its way to break users that are using this +kind of override, but we do not actively support it, and some functionality +(e.g., service config support) will not work when the path is not of the form +shown above. If **Timeout** is omitted a server should assume an infinite timeout. Client implementations are free to send a default minimum timeout based on their deployment requirements.