CGI Web Application Problem

[Dr. Know]

Greetings,

I run a small web server and am attempting to get a CGI (compiled
Win32 executable) application to work properly. I have pounded my
head on this for 4 hours, and have been unsuccessful.

The problem arises when the application attempts to write to a
configuration file and the log file.

The directory and children have execute permissions. The app is
called from the Web Page, but returns an error that it does not have
write access. I have granted all execute, file and directory
permissions to "Web Applications".

I even tried the Unix trick of creating a user account, assigning it
the owner of both the ap and the directories, and explicitly assigning
it read, write, change, and all other permissions, but it STILL
doesn't work.

The CGI is located in the scripts directory, off the root, and is
virtually shared with the individual web site folders.

Arrgg... what am I doing wrong?


Dr. Know

 

[Enno Lenze]

hi!

The CGI is located in the scripts directory, off the root, and is
virtually shared with the individual web site folders.

Can you run any other cgi script? (i.e. the printenv [testscript])?

What does the error log file of the webserver say?

regards, enno

 

[Dr. Know]

Enno Lenze said:

hi!

The CGI is located in the scripts directory, off the root, and is
virtually shared with the individual web site folders.

Can you run any other cgi script? (i.e. the printenv [testscript])?

What does the error log file of the webserver say?

Thanks, Enno,

But I finally figured out the problem.

You have to assign the owner of the log directories as IUSR_SERVERNAME
and allow write, create, modify, execute and delete priveledges. Not
very secure... but it works. You have to make sure that the directory
is compartmentalized to help prevent compromise by hackers.

The IIS Server Error Log said nothing! Probably because the app was
called, and it ran, but it wouldn't complete it's tasks because of the
security restrictions on writing/modifying the log files.

Thanks again,


Dr. Know