Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature currently requires accessing the site using the built-in Safari browser.
If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread: CentOS2Alma discussion
I wonder why it takes so long to reply by Plesk. However I expect it does effect any system that uses CGI. In case of Plesk if PHP uses CGI. PHP-fastcgi for example.
Notes:
This fix only works if you use nginx with apachefor PHP(fcgi). If your using NGINX and PHP-FPM this fix will not work and the fix should be done in NGINX.
About NGINX:
But getting it in NGINX is quiet some work. Well the actuall fix is easy for nginx, add: proxy_set_header Proxy "";
in the location / directive of the vhost. Problem is that there There is no way to set the proxy_set_header Proxy directive globaly (to my knowledge). So to get it to work it needs
to be in every vhost config. You either have to make a custom nginx config template for Plesk or you have to wait till Plesk updates the vhost template.
All workarounds, if you want to do this manually, are well described in https://httpoxy.org/
Workarounds for nginx (you are affected only if you use FPM application served by nginx PHP handler) and IIS (Plesk for Windows is affected) will be implemented in Plesk, I hope soon.
Apache (search CVE-2016-5387) is already fixed by all Linux OS vendors:
[...] and IIS (Plesk for Windows is affected) will be implemented in Plesk, I hope soon.
All workarounds, if you want to do this manually, are well described in https://httpoxy.org/
Workarounds for nginx (you are affected only if you use FPM application served by nginx PHP handler) and IIS (Plesk for Windows is affected) will be implemented in Plesk, I hope soon.
I guess Plesk for Windows 12.5, maybe 12.0 will be updated.
I do not think Plesk 11.5 will be updated, because this issue is not critical (there are workarounds). Plesk 11 is now in “Extended Support” phase that means that it continue to receive patches only for critical issues. https://www.plesk.com/support/plesk-lifecycle/