• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved HTTP2 already enabled, Apache still using 1.0 in few requests

othmaqsa

Regular Pleskian
Server operating system version
20.04.4 LTS
Plesk version and microupdate number
18.0.45 Update #1
Hello,

HTTP/2 is already activated, however, I notice in the LOG requests that go through HTTP/1.

I checked on this site (HTTP/2 Test - Verify HTTP/2 Support | KeyCDN Tools) and the output is as follows:

HTTP/2 protocol is supported.
ALPN extension is supported.


Another information: I use the proxy mode.

Any idea why this happens?
 
I guess what you are seeing are HTTP/1.0 requests in the Apache log files (access_ssl_log). That's normal: nginx is the frontend server which is supporting HTTP/2 (as confirmed by your tests) but is using HTTP/1.0 internally to proxy the connection to Apache.

So short version: Nothing to worry about, it's expected behaviour.
 
Back
Top