cancel
Showing results for 
Search instead for 
Did you mean: 

err_http2_protocol_error

Pavan_Dhanushka
Altostratus
Altostratus

One of my client getting subjected error(err_http2_protocol_error) intermittently but When I surfed on internet and I see like this error most related chrome browser. But I couldn't find any F5 article to confirm. Can anyone help me to figure out is this related to BIGIP and Chrome issue ? Or something else I need to check this further in BIGIP side ?

 

Thanks in advance!

4 REPLIES 4

Ivan_Chernenkii
F5 Employee
F5 Employee

Hello Pavan,

 

Where do you see this error in Browser console or in some BIG-IP logs?

If in browser console, then it could be an application and not BIG-IP error.

 

Thanks, Ivan

bradhanson
Altocumulus
Altocumulus

This happens to us all the time. We have been unable to implement http2 as a result. Chrome returns message:

The webpage at https://....... might be temporarily down or it may have moved permanently to a new web address.

ERR_HTTP2_PROTOCOL_ERROR

 

It is a very straightforward virtual server with HTTP2 set only on the client side.

The console shows nothing in response. the request comes in, the error occurs.

 

other HTTP2 sites can work from that same Chrome browser. I don't see it as a Chrome issue. Have a case open with support.

guly
Nimbostratus
Nimbostratus

Hi. Can you share with us what was the response from F5 support about the issue? We encountered very similar issues and I'm trying to find what's the reason for ERR_HTTP2_PROTOCOL_ERROR for lots of clients. Thanks

bradhanson
Altocumulus
Altocumulus

We are still working with it, but they found that responses were exceeding thresholds of maximum number of headers and total header table size. increasing these has helped but still tweaking. Finding RFC violations on the responses from our applications.

 

  1. extending the http profile max-header-count to 80 does not resolve the issue, then it's likely to be the http/2 profile header-table size.
  2. Leave the http profile max-header-count at 80 and increase the http/2 profile header-table-size to 6000 (or more) and test again.