Page 1 of 1

Difference in phpinfo on two different IIS servers

Posted: Mon Jul 25, 2005 1:41 pm
by Visslik
Forgive me for having little to no PHP experience, but hopefully someone can lend a hand.

I currently have a IIS server running PHP 4.3.0, and a new server running 5.0.4. When running a test PHP script on the 4.3.0 server, the output can be seen as so:

http://wtfe1.acd.net/test.php

Nice, simple layout, and what I expect to see in a phpinfo script.

However, if I place the same test.php on the new server, I get different output:

http://wtfe2.acd.net/test.php

Is this simply a difference between the two versions, or is there something I've not set up correctly? The contents of php.ini look identical as far as I can determine. I would think the fact that the test.php obtained the PHP info at all should tell me that PHP is working fine, but I would like to know before I put any sites on the server. Thanks in advance.


Joe

Posted: Mon Jul 25, 2005 2:00 pm
by timvw
php.ini default_mimetype = "text/html"

Posted: Mon Jul 25, 2005 2:24 pm
by Visslik
php.ini on both boxes has that value set as the default. :/ One thing I have found is that on wtfe1.acd.net the server API is listed as CGI/FastCGI, while on the new server it's listed as Command Line Interpreter. I found fastcgi.impersonate=1, which was commented out in the php.ini on wtfe2. I uncommented it but it still lists as Command Line Interpreter in the test.php script. On wtfe1 I have .php files mapped to "D:\PHP\php.exe %s %s". On wtfe2 I have them mapped to "C:\PHP\php.exe %s %s".

Posted: Mon Jul 25, 2005 3:27 pm
by timvw
Well, meaby the CGI config is not configured well...

Because, the 2nd doesn't output headers..

Posted: Mon Aug 08, 2005 1:54 pm
by Visslik
timvw wrote:Well, meaby the CGI config is not configured well...

Because, the 2nd doesn't output headers..
I'm not sure what to look at then. CGI scripts do work on both servers. I'm sure this is what my problem is, as Mozilla prompts you to choose something to open the file with rather than opening the script in the browser window like IE does.