# The ExecCGI option in V3

**URL:** <https://forums.interworx.com/t/the-execcgi-option-in-v3/11658>\
**Category:** General Inquries\
**Created:** [June 2, 2007, 9:54am UTC](https://forums.interworx.com/t/the-execcgi-option-in-v3/11658 "2007-06-02T09:54:27Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://forums.interworx.com/uploads/default/original/2X/4/40ab17cc34b792a0172b48ad1333b9ba9299a9a1.png) [@system](https://forums.interworx.com/u/system)\
**Post date:** [June 2, 2007, 9:54am UTC](https://forums.interworx.com/t/the-execcgi-option-in-v3/11658/1 "2007-06-02T09:54:27Z")

</div>

Hi

In V2 I had noticed that the default vhost skel for ExecCGI was not so fine for most of admin  
See this thread : [http://www.interworx.com/forums/showthread.php?t=1332&highlight=ExecCGI](http://www.interworx.com/forums/showthread.php?t=1332&highlight=ExecCGI)

Indeed, generaly we allow CGI-SCRIPTS to be run only in a cgi-bin directory.

Why it is important for a server admin ?  
Because like this it’s most easy to write a script that check which kind of CGI scripts users use !  
If there is CGI Scripts everywhere in the doc\_root it’s more complicated to follow up.

So what’s is new in V3 ?  
You (interworx) changed the vhost-base.conf by setting CGI scripts definitions in a \<location /\> rather than \<Directory \>… Why not…

But you still allow CGI scripts to be run everywhere

> \<Location /\>  
> Options \<\<CGI1\>\>  
> \</Location\>  
> \<\<CGI2\>\>

# end cgi

Which give

> \<Location /\>  
> Options +ExecCGI  
> \</Location\>  
> ScriptAlias /cgi-bin/ /home/account/domain.com/html/cgi-bin/

# end cgi

I know it is possible to change this default config by editing the vhost-base.conf file, but why don’t set the default only like this ?

> ScriptAlias /cgi-bin/ /home/account/domain.com/html/cgi-bin/

Is there a good reasons to let cgi scripts runs everywhere ?

Thanks  
Pascal
