How does Chromium/Chrome decide to use wether http/2 or http/1.1

Viewed 566

we encountered a weird problem in which we work on a SAP server that has HTTP/2 enabled. If we try to access the system (e.g. a BSP), different Browsers show different protocols.

  • Firefox 84.0.2 - HTTP/2
  • Internet Explorer 11 - HTTP/2
  • Chrome 87.0.4280.141 - HTTP/1.1
  • Edge 87.0.664.75 - HTTP/1.1

As of right now we cannot think of a reason for this behaviour. It seems like Chrome/Chromium behaves different to the other browser. This made us think about the mechanism Chrome/Chromium uses to select the protocol version.

Does anyone have any insight into that mechanism? I could not anything.

Thank you!

1 Answers
Related