Re: [greenstone-users] Greenstone as applet on IIS

From John R. McPherson
DateThu, 22 Feb 2007 07:08:28 +1300
Subject Re: [greenstone-users] Greenstone as applet on IIS
In-Reply-To (65B0C0E071C62648A240F99B77B42FC1A8F842-RHINO-yuad-uds-yu-edu)
On Wed, Feb 21, 2007 at 11:30:45AM -0500, Samuel Tyszler wrote:
> Regarding this, I am still stuck, but I wonder about something. If I
> switch to using ActiveState Perl would that be a possible solution here?
> How could that be set up? I imagine all that would be required is to
> change the perl.exe path.

>> I checked and double-checked against the page and nothing else looks
>> amiss. I am running IIS 6 and checked the extensions and CGI settings
>> twice. Still the same result. Any other things to check?

it looks like the problem here is that the cgi script does not output
a HTTP status code as its first line of output, and I'm guessing
that the default apache configuration is more forgiving of this
than IIS's default (or the default of your server has changed).

$ export QUERY_STRING='cmd=check-installation'
$ ./

Java found: java version "1.4.2_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_08-b03)
Java HotSpot(TM) Client VM (build 1.4.2_08-b03, mixed mode)

Normally cgi scripts have to output 'Status: 200 Ok' (or output
HTTP/1.0 200 Ok' if the server is set to use "non-parsed headers").
I think it is a configuration setting as to whether a web server
requires this or will add it if it's missing, but I think this is
something that should be fixed in the script itself.