Is this an oversight within the DirectAdmin evolution skin?
If a user has CGI disabled - i.e. cgi=OFF in /usr/local/directadmin/data/users/%user%/user.conf - the option to select CGI access is still present in the user's panel.
Logging into the user's panel and clicking Domain Setup -> Add New -> CGI Access is still a check box clickable item in the Options.
Now from what I can tell this doesn't take affect. If the user.conf has cgi=OFF then the line:
ScriptAlias /cgi-bin/ /home/%user%/domains/%domain%/public_html/cgi-bin/
is not added and the line:
Options -ExecCGI -Includes +IncludesNOEXEC
is added to the user's httpd.conf file.
So in that sense, I guess it's working. But should the option to check CGI Access exist here?
The CGI Access checkbox is not present when you go to Modify a domain if cgi=OFF is set.
If a user has CGI disabled - i.e. cgi=OFF in /usr/local/directadmin/data/users/%user%/user.conf - the option to select CGI access is still present in the user's panel.
Logging into the user's panel and clicking Domain Setup -> Add New -> CGI Access is still a check box clickable item in the Options.
Now from what I can tell this doesn't take affect. If the user.conf has cgi=OFF then the line:
ScriptAlias /cgi-bin/ /home/%user%/domains/%domain%/public_html/cgi-bin/
is not added and the line:
Options -ExecCGI -Includes +IncludesNOEXEC
is added to the user's httpd.conf file.
So in that sense, I guess it's working. But should the option to check CGI Access exist here?
The CGI Access checkbox is not present when you go to Modify a domain if cgi=OFF is set.