• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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