[
https://issues.apache.org/jira/browse/THRIFT-5541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514928#comment-17514928
]
Marco Ferrer edited comment on THRIFT-5541 at 3/30/22, 8:27 PM:
----------------------------------------------------------------
If the current definition is viewed as sufficient then I would recommend
explicitly stating how this spec differs from other common specs. It is not
immediately obvious to those not familiar with thrift how far this spec
deviates from other popular specs (http1/2, gRPC). In contrast to thrift, the
grpc specification is deeply detailed on format and content specifics.
was (Author: JIRAUSER287322):
If the current definition is viewed as sufficient then I would recommend
explicitly stating how this spec differs from other common specs. This it not
immediately obvious to those not familiar with thrift how far this spec
deviates from other popular specs (http1/2, gRPC). In contrast to thrift, the
grpc specification is deeply detailed on format and content specifics.
> Header spec is ambiguous about key format
> -----------------------------------------
>
> Key: THRIFT-5541
> URL: https://issues.apache.org/jira/browse/THRIFT-5541
> Project: Thrift
> Issue Type: Documentation
> Reporter: Marco Ferrer
> Priority: Minor
>
> The current header specification does not specify what is considered a valid
> format for keys. Looking at the most common networking protocols (http/http2)
> we see specifics as to what keys characters are allowed and their formatting.
> There is no equivalent definition in thrift.
> The thrift header spec should clarify things like case sensitivity, behavior
> for trailing whitespace and non-ascii characters.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
