philip Tue Mar 29 04:03:57 2005 EDT
Modified files:
/phpdoc/en/install/windows iis.xml
Log:
Streamline the install instructions, a little restructure, and added more
information including some specific to Win2003. This officially closes
bug #23907
http://cvs.php.net/diff.php/phpdoc/en/install/windows/iis.xml?r1=1.12&r2=1.13&ty=u
Index: phpdoc/en/install/windows/iis.xml
diff -u phpdoc/en/install/windows/iis.xml:1.12
phpdoc/en/install/windows/iis.xml:1.13
--- phpdoc/en/install/windows/iis.xml:1.12 Tue Mar 29 02:04:03 2005
+++ phpdoc/en/install/windows/iis.xml Tue Mar 29 04:03:51 2005
@@ -1,5 +1,5 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.12 $ -->
+<!-- $Revision: 1.13 $ -->
<sect1 id="install.windows.iis">
<title>Microsoft IIS / PWS</title>
<para>
@@ -72,6 +72,16 @@
<ulink url="&url.php.downloads;">Download PHP files here</ulink>.
</simpara>
</listitem>
+ <listitem>
+ <simpara>
+ When defining the executable, the 'check that file exists' box may also
+ be checked. For a small performance penalty, the IIS (or PWS) will check
+ that the script file exists and sort out authentication before firing up
+ PHP. This means that the web server will provide sensible 404 style
+ error messages instead of CGI errors complaining that PHP did not output
+ any data.
+ </simpara>
+ </listitem>
</itemizedlist>
</para>
</sect2>
@@ -94,36 +104,23 @@
<itemizedlist>
<listitem>
<simpara>
- Under 'Home Directory', 'Virtual Directory', or
- 'Directory', click on the 'Configuration' button,
- and then enter the App Mappings tab.
+ Under 'Home Directory', 'Virtual Directory', or 'Directory', do the
+ following:
</simpara>
</listitem>
<listitem>
<simpara>
- Click Add, and in the Executable box, type:
- <literal>C:\php\php.exe</literal> for PHP 4 or
- <literal>C:\php\php-cgi.exe</literal> for PHP 5 (assuming
- that you have unziped PHP in <filename>c:\php\</filename>).
- </simpara>
+ Change the Execute Permissions to 'Scripts only'
+ </simpara>
</listitem>
<listitem>
<simpara>
- 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 complaining that PHP did not output any data.
- </simpara>
- <simpara>
- You must start over from the previous step for each
- extension you want associated with PHP scripts.
- <literal>.php</literal> and <literal>.phtml</literal>
- are common, although <literal>.php3</literal> may be
- required for legacy applications.
+ Click on the 'Configuration' button, and choose the Application Mappings
+ tab. Click Add and set the Executable path to the appropriate CGI file.
+ An example PHP 5 value is: <filename>C:\php\php-cgi.exe</filename>
+ Supply <literal>.php</literal> as the extension. Leave 'Method
+ exclusions' blank, and check the 'Script engine' checkbox. Now, click
+ OK a few times.
</simpara>
</listitem>
<listitem>
@@ -136,7 +133,6 @@
</listitem>
</itemizedlist>
</para>
-
<para>
To use the ISAPI module, do the following:
<itemizedlist>
@@ -151,12 +147,23 @@
</listitem>
<listitem>
<simpara>
- Under 'Home Directory', click on the 'Configuration' button.
- Add a new entry to the Application Mappings. Use the path
- to the <filename>php4isapi.dll</filename> /
- <filename>php5isapi.dll</filename> as the Executable, supply
- <literal>.php</literal> as the extension, leave 'Method exclusions'
- blank, and check the 'Script engine' checkbox.
+ Under 'Home Directory', 'Virtual Directory', or 'Directory', do the
+ following:
+ </simpara>
+ </listitem>
+ <listitem>
+ <simpara>
+ Change the Execute Permissions to 'Scripts only'
+ </simpara>
+ </listitem>
+ <listitem>
+ <simpara>
+ Click on the 'Configuration' button, and choose the Application Mappings
+ tab. Click Add and set the Executable path to the appropriate ISAPI DLL.
+ An example PHP 5 value is: <filename>C:\php\php5isapi.dll</filename>
+ Supply <literal>.php</literal> as the extension. Leave 'Method
+ exclusions' blank, and check the 'Script engine' checkbox. Now, click
+ OK a few times.
</simpara>
</listitem>
<listitem>
@@ -172,6 +179,27 @@
</itemizedlist>
</para>
<para>
+ With IIS 6 (2003 Server), open up the IIS Manager, go to Web Service
+ Extensions, choose "Add a new Web service extension", enter in a name such
+ as PHP, choose the Add button and for the value browse to either the ISAPI
+ file (<filename>php4isapi.dll</filename> or
+ <filename>php5isapi.dll</filename>) or CGI (<filename>php.exe</filename> or
+ <filename>php-cgi.exe</filename>) then check "Set extension status to
+ Allowed" and click OK.
+ </para>
+ <para>
+ In order to use <filename>index.php</filename> as a default content page,
+ do the following: From within the Documents tab, choose Add. Type in
+ <filename>index.php</filename> and click OK. Adjust the order by choosing
+ Move Up or Move Down. This is similar to setting DirectoryIndex with
+ Apache.
+ </para>
+ <para>
+ The steps above must be repeated for each extension that is to be
+ associated with PHP scripts. <literal>.php</literal> is the most common
+ although <literal>.php3</literal> may be required for legacy applications.
+ </para>
+ <para>
If you experience 100% CPU usage after some time, turn off the IIS
setting <literal>Cache ISAPI Application</literal>.
</para>
