Hi

I am running Windows 2000 server with iis 5. I have a image resizer dll and
they tell me to put it into my cgi-bin folder. Sorry for being naive but
where is that. i can't see it in the wwwroot directory.

Is it a virtual directory that has to be set up in iis?

Thanks Wilbur

RE: dll files by LeonMayne

LeonMayne
Wed Jun 28 11:01:02 CDT 2006

> I am running Windows 2000 server with iis 5. I have a image resizer dll and
> they tell me to put it into my cgi-bin folder. Sorry for being naive but
> where is that. i can't see it in the wwwroot directory.

A cgi-bin folder is usually a web folder for Apache to use perl, specifying
that perl / c applications can be executed by the webserver in this folder.
You wouldn't normally have a cgi-bin folder in IIS.

You'll either need to put the DLL in your System32 folder or in the same web
folder as the application that is being executed.


Re: dll files by David

David
Wed Jun 28 20:35:43 CDT 2006

Not exactly correct. Leon, I know you mean well, but you are actually saying
very incorrect things about IIS.

Whether you have a cgi-bin folder on a web server depends on the
applications. Apache has applications that require cgi-bin; IIS has similar
applications. All you need to do is create a vdir with appropriate Execution
permissions (either allow "scripts" or "executable ISAPI/CGI" to run), point
the vdir to the files that need to be in cgi-bin, and it's done -- basically
the same functionality as Apache -- a directory where things inside are
allowed to execute.

Where you put the scripts and DLL/EXE binaries is up to you. You do NOT have
to put the DLL in System32 folder nor the same web folder as the application
being executed. You can put it anywhere you want and then properly secure
access to it (while it CAN include those aforementioned places, I wouldn't
do it because those suggestions are insecure and there are better
alternatives - it all depends on how you want to manage the server).

Contrary to what Leon suggests, IIS actually allows *very* flexible cgi-bin
definitions, and with Application Mapping, you can have as many cgi-bin as
you want and NONE of the scripts or DLLs are web-accessible at all and
perfectly secured -- very secure configuration that is easy to maintain.

Yes, it is different from Apache's cgi-bin model, but Windows process
execution model is also different (and richer/more fine-grained/powerful)
than *nix.

For example, here is an advanced example showing how to have a cgi-bin
without even having the scripts nor DLLs be web-accessible.
http://blogs.msdn.com/david.wang/archive/2005/09/14/HOWTO_Use_IIsWebFile_to_Securely_Run_CGI_in_cgi_bin_from_the_root_directory_.aspx

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//

"Leon Mayne" <LeonMayne@discussions.microsoft.com> wrote in message
news:108EADA1-BC0D-4C71-8993-020B80E963E0@microsoft.com...
>> I am running Windows 2000 server with iis 5. I have a image resizer dll
>> and
>> they tell me to put it into my cgi-bin folder. Sorry for being naive but
>> where is that. i can't see it in the wwwroot directory.
>
> A cgi-bin folder is usually a web folder for Apache to use perl,
> specifying
> that perl / c applications can be executed by the webserver in this
> folder.
> You wouldn't normally have a cgi-bin folder in IIS.
>
> You'll either need to put the DLL in your System32 folder or in the same
> web
> folder as the application that is being executed.
>



Re: dll files by LeonMayne

LeonMayne
Thu Jun 29 02:41:01 CDT 2006

Yes that's true, but normally when you see cgi-bin you think of Apache.
I guess they could be referring to a 'Scripts and applications' configured
folder if the DLL is going to be run directly, but I assumed the DLL would
just be a library for the main application, in which case I would keep it out
of the web root (unless it's an ASP.NET application).

I think the OP needs to explain the setup procedure they have been given.