In addition to my tcpdump analysis where it does not classify it as http2
I tries haproxy also does not classify it as http2 packet,
haproxy rejects with following line,
use_backend test_backend if { ssl_fc_npn -i h2 }
but works with following line,
default_backend test_backend
this further
Thanks.
On Friday, November 30, 2018 at 6:17:56 AM UTC+5:30, Srini Polavarapu wrote:
>
>
>> What does grpc rely on to for http2 capability? (any tool in os
>> environment or http2 capability is inbuilt in grpc?)
>>
>
> gRPC Python has a built-in HTTP/2 stack.
>
>
> On Thursday, November 29,
Thanks for writing.
Same tool i am using for capturing and viewing 2 dumps, 1 dump it shows
http2 where as this dump it shows application protocol.
Looking at other replies and going thru other documents, i hope grpc cannot
work without http2.
But my issue is at least half of the time, after
>
>
> What does grpc rely on to for http2 capability? (any tool in os
> environment or http2 capability is inbuilt in grpc?)
>
gRPC Python has a built-in HTTP/2 stack.
On Thursday, November 29, 2018 at 10:13:27 AM UTC-8, Josh Humphries wrote:
>
> The main gRPC libraries *only* use HTTP/2. As
The main gRPC libraries *only* use HTTP/2. As you saw, they negotiate the
same protocol during NPN step of TLS handshake: "h2". It is more likely
that whatever analysis tool you used in the first case did not recognize
"h2" as the HTTP/2 protocol, so treated it as an unknown application
protocol.
What language(s) are you using gRPC with? In any case, it will be very hard
for us to help with such an old version; is there any way for you to update
it?
On Wednesday, November 28, 2018 at 6:37:25 AM UTC-8, Pramma wrote:
>
>
> While analysing tcpdump of gRPC comm between our client
