Supporting HTTP/2 for Google Chrome Users
Supporting HTTP/2 for Google Chrome Users table, th, td { border: 1px solid black; } th { background-color: #d3d3d3; align: left; padding-left: 5px; padding-bottom: 2px; padding-top: 2px; line-height: 120%; } td { padding-left: 5px; padding-bottom: 5px; padding-top: 5px; line-height: 120%; } Users of the Google Chrome web browser are seeing some sites that they previously accessed over HTTP/2 falling back to HTTP/1. This is because of a policy change in the most recent update to Chrome, released in late May, which removes support for NPN, one method for upgrading a connection to HTTP/2. The only way Chrome users can continue using HTTP/2 to access these websites is by switching to a different browser. Website administrators can restore HTTP/2 support for Chrome users by upgrading their OpenSSL installation to the recently released 1.0.2 version. Unfortunately, this requires either a major operating system [ more… ]
