|Date||Mon, 12 Mar 2007 11:59:11 -0400|
|Subject||[greenstone-users] RE: Unresolved IIS6 issue with gliserver.pl|
Thank you for getting back to me.
Although I cannot be positive that I am doing that correctly, I added what you said to. No matter what the order the errors persist.
In the Hello World page I switched to text/plain and it works just fine.
The troubleshooting may be suffering a bit because I am not versed in Perl nor a web programmer. I am sure an expert can look at the code while simultaneously testing off an IIS server and probably find a tiny error somewhere. It would be fantastic if a developer were to directly test against our server. I am not the best one to be tweaking the code like this.
Thanks for your response.
Your suggestion didn't work. But it did give me an insight into the issue and inspired me to test this in a different way. I found a "Hello World" type script online and I successfully executed it on the server. So the set up of the web server is ok. Here is the script that runs:
print "Content-type: text/html ";
<title>A Simple Perl CGI</title>
<h1>A Simple Perl CGI</h1>
You can execute that at http://188.8.131.52/gsdl/cgi-bin/helloworld.pl
Attempting to execute http://184.108.40.206/gsdl/cgi-bin/gliserver.pl?cmd=check-installation fails.
You may have full access to my web server to help diagnose this issue and provide a solution to the community. I just got an email from another user in my position who is also seeking a fix. Mine is not an isolated incident. Contact me off list and I will be happy to provide you with credentials that will allow access.
From: David Milne [mailto:email@example.com]
Sent: Wednesday, February 28, 2007 8:57 PM
To: Samuel Tyszler
Subject: Re: [greenstone-users] Greenstone on IIS 6?
I dont have an IIS installation so I cant try this out myself.
Could you please have a look at the gliserver.pl script in the cgi-bin directory?
There is a line at the end of the get_script_options method where it outputs the content type. Just before this, try inserting the line:
print STDOUT "Status: 200 OK " ;
then restart the webserver and see how that works. Let me know what happens either way.