Troubleshooting Tip: Disabling HTTP/2.0 in the Web browser to avoid bad request response from the server

[nevan]

Description	This article describes and shows the scenario when the HTTP/2.0 must be disabled and how to disable it in web browsers.
Scope	FortiGate, Web browser.
Solution	When the destination server or website does not support the HTTP/2.0 version but the request is generated with this protocol from the originator the server might not recognize the request and the error may appear or some content might get broken. Sometimes the request may show '400 Bad Request' in the web browser but for the broken content, it may not appear. While capturing the packet the error code can be found in the payload and protocol description. To understand the request from the originator or from the user a HAR file can be taken and the POST request HTTP version will show the version of the protocol. To get rid of this problem the user can downgrade the version from the web browser as the server is not supporting the version of the request. The HTTP/2.0 is available in most of the popular browsers and the feature can be disabled in the following way. Chrome: In the URL search field have to type 'chrome://flags'.  Once a new page will return have to search the HTTP/2. On the right side, there is an option to enable/disable the protocol.  Firefox: In the URL search option have to search for 'about:config'.  Once the warning page returns have to accept the risk. After, search with 'network.http.spdy.enabled.http2' The button will appear On the right side to make it 'false' and once done, it will be disabled. Related articles: Troubleshooting Tip: How to collect HAR files HTTP/2 support in proxy mode SSL inspection