• 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!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Bug in FCGI support via web panel?

A

ash113

Guest
When you enable FCGI support via the panel in Plesk 8.3, it sets up the following in the site's apache conf:

Code:
        <IfModule mod_fcgid.c>
                AddHandler fcgid-script .fcgi
                Options +FollowSymLinks +ExecCGI
        </IfModule>
                Options -Includes -ExecCGI

The problem being that the line at the end, which is presumably the default, immediately turns off ExecCGI that had been turned on one line earlier. Leaving .fcgi files giving 403 errors. This can be fixed by adding a .htaccess that turns it back on, but that seems an unnecessary hoop to jump through. I'd think the right fix is for Plesk to set the default line at the top of the VirtualHost block, not the bottom, so that the various overides that might get turns on work properly.
 
I have tested this functionality on Plesk 8.3.0 with January 31st update installed and noted following configuration change:

<IfModule mod_fcgid.c>
AddHandler fcgid-script .fcgi
Options +FollowSymLinks +ExecCGI
</IfModule>

No line with disabling the option.
 
Back
Top