• 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.

How to execute CGIs from anywhere

C

Conor McCarthy

Guest
Is there a way to allow CGIs to be executed from anywhere, not just the cgi-bin, using Plesk?

Cheers
Conor
 
What's the reason for opening this big gate, if i may ask? ;)
 
I've got an existing set of scripts which I want to move to the new server which doesn't separate cgis and html, so it would be difficult to edit all the paths in the scripts.
 
I would try two things.

In /etc/apache2/default-server.conf is a part like this, defining CGI:
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
ScriptAlias /cgi-bin/ "/srv/www/cgi-bin/"

# "/srv/www/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
<Directory "/srv/www/cgi-bin">
AllowOverride None
Options +ExecCGI -Includes
Order allow,deny
Allow from all
</Directory>

And in you Domains' httpd.include you can find "Options -Includes -ExecCGI" disallowing ExecCGI for your DocumentRoot. You could change that to +ExecCGI, then CGI is allowed for the whole DocumentRoot.

Hope this helps.
 
Thanks for the reply Blackbit. Apache isn't my forte.
I can't find any file called default-server.conf (using locate). And there is no /etc/apache2/ directory. Actually, I can find shag all related to apache when I run a locate apache.

Have you any other ideas?
 
See Knowledge base Article ID: 193

Originally posted by Conor McCarthy
Is there a way to allow CGIs to be executed from anywhere, not just the cgi-bin, using Plesk?

Cheers
Conor
 
Thanks.

By default Plesk runs CGI scripts in /cgi-bin/ folder only. To allow CGI scripts be processed from any folder, you should and uncomment the cgi-script AddHandler directive in the main apache configuration file /etc/httpd/conf/httpd.conf:
 
Back
Top