>>What about IIS. This is what the customer is using....and I know d*** about >>IIS. I would assume that there is a similar thing for IIS, but have no idea >>where to even look.
If you are using IIS 3.0 Check out install.txt file which comes with PHP Win32 Binary. It says: > Run Regedit. > Navigate to: > HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/W3Svc/Parameters/Script Map > On the edit menu select: New->String Value. > Type in the extension you wish to use for your php scripts. ex: .php > Double click on the new string value and enter the path to > php.exe in the value data field. > ex: c:\php\php.exe > Repeat these steps for each extension you wish to associate > with PHP scripts. With IIS 4 + Check out the install.txt file again it says: Windows NT/2000/XP and IIS 4 or newer and PWS 4 on NT Workstation or W2K non server editions > In the Extension box, type the file name extension you want > associated with PHP scripts. Leave 'Method exclusions' > blank, and check the Script engine checkbox. You may also > like to check the 'check that file exists' box - for a small > performance penalty, IIS (or PWS) will check that the script > file exists and sort out authentication before firing up php. > This means that you will get sensible 404 style error messages > instead of cgi errors complaing that php did not output any data. > You must repeat from 'Click Add...' for each extension you > want associated with PHP scripts. Do the same for .html extension and you must be OK. Allthough there may be performance hits for normal HTML Files as they will always go to PHP ENgine. Regards, Nikunj Virani Senior System Administrator. -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
