用apache就不用iis了 Installing PHP on Windows with Apache 1.3.x There are two ways to set up PHP to work with Apache 1.3.x on Windows. One is to use the CGI binary (php.exe), the other is to use the Apache module dll. In either case you need to stop the Apache server, and edit your srm.conf or httpd.conf to configure Apache to work with PHP. Although there can be a few variations of configuring PHP under Apache, these are simple enough to be used by the newcomer. Please consult the Apache Docs for further configuration directives. Now that version 4.1 introduces a safer sapi module, we recommend that you configure PHP as a module in Apache. To do this, you should move php4ts.dll to the windows/system (for Windows 9x/Me) or winnt/system32 (for Windows NT/2000/XP) directory, overwriting any older file. Then you should add the following three lines to your Apache conf file: (swap c:/php/ for your PHP install path) LoadModule php4_module c:/php/sapi/php4apache.dll AddModule mod_php4.c AddType application/x-httpd-php .phpIf you wish to install PHP as a CGI binary, (the sapi is much better) you need to enable the apache security fix in your php.ini by setting cgi.force_redirect = 1. Then, insert these lines to your conf file: ScriptAlias /php/ "c:/php/" AddType application/x-httpd-php .php Action application/x-httpd-php "/php/php.exe" Please note that you cannot use php-cli.exe with your webserver. You have to use php.exe which can be found in the sapi directory of your PHP distribution. As a further precaution, we recommend you change the "/php/" ScriptAlias to something more random, to prevent any attempts to call your binary (like the Code Red scripts) for returning a response other than 404.
Remember when you have finished to restart the server, for example, NET STOP APACHE followed by NET START APACHE To use the source code highlighting feature, add the following line to your apache httpd.conf file: AddType application/x-httpd-php-source .phps Note, this will only work when you install php as a sapi module. If you wish to use this feature with the cgi binary, create a new file, and use the show_source("path/to/original_file.php"); function. On Win-Apache all backslashes in a path statement such as: "c:\directory\file.ext", must be converted to forward slashes.
对,IIS的端口号用默认的80不变,而APACHE可改为8080 IIS和APACHE可以并存
TO : phpteam(Fanny) 你怎么保存着那么多的资料呵? 还有,我现在也开始试着回答网友的一些问题,呵呵!
with iisInstalling PHP on Windows with IIS/PWS This section contains notes and hints specific to IIS (Microsoft Internet Information Server). Installing PHP for PWS/IIS 3 and PWS/IIS 4 or newer versions. Windows and PWS/IIS 3 - including PWS on Win 9x/ME The recommended method for configuring these servers is to use the REG file incuded with the distribution (pws-php4cgi.reg). You may want to edit this file and make sure the extensions and PHP install directories match your configuration - once you have done this, just double click on the file and it will update your registry. Alternatively, you can follow the steps below to do it manually. WARNING: These steps involve working directly with the Windows registry. One error here can leave your system in an unstable state. We highly recommend that you back up your registry first. The PHP Development team will not be held responsible if you damage your registry. Run Regedit. Navigate to: HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/W3Svc/Parameters/ScriptMap 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\sapi\php.exe Repeat these steps for each extension you wish to associate with PHP scripts. Please note that you cannot use php-cli.exe with your webserver, you need to use php.exe which can be found in the sapi directory of your PHP distribution. The following steps do not affect the web server installation and only apply if you want your php scripts to be executed when they are run from the command line (ex. run c:\myscripts\test.php) or by double clicking on them in a directory viewer window. You may wish to skip this step as you might prefer the php files to load into a text editor when you double click on them. Now navigate to: HKEY_CLASSES_ROOT On the edit menu select: New->Key Name the key to the extension you setup in the previous section. ex: .php Highlight the new key and in the right side pane, double click the "default value" and enter phpfile. Repeat the last step for each extension you set up in the previous section. Now create another New->Key under HKEY_CLASSES_ROOT and name it phpfile Highlight the new key 'phpfile' and in the right side pane, double click the "default value" and enter PHP Script. Right click on the 'phpfile' key and select New->Key, name it Shell. Right click on the 'Shell' key and select New->Key, name it open. Right click on the 'open' key and select New->Key, name it command. Highlight the new key 'command' and in the right side pane, double click the "default value" and enter the path to php.exe ex: c:\php\php.exe -q %1 (don't forget the '%1'). Exit Regedit. If using PWS on Windows, reboot to reload the registry. PWS and IIS 3 users now have a fully operational system. IIS 3 users can use a nifty tool available at http://www.genusa.com/iis/iiscfg.html from Steven Genusa to configure their script maps. Windows NT/2000/XP and IIS 4 or newer and PWS 4 on NT Workstation or W2K non server editions To install PHP on an NT/2000/XP Server running IIS 4 or newer, follow these instructions. You have two options to set up PHP, using the CGI binary (php.exe) or with the ISAPI module. In either case, you need to start the Microsoft Management Console (may appear as 'Internet Services Manager', either in your Windows NT 4.0 Option Pack branch or the Control Panel=>Administrative Tools under Windows 2000). Then right click on your Web server node (this will most probably appear as 'Default Web Server'), and select 'Properties'. If you want to use the CGI binary, do the following: Under 'Home Directory', 'Virtual Directory', or 'Directory', click on the 'Configuration' button, and then enter the App Mappings tab. Click Add, and in the Executable box, type: c:\php\sapi\php.exe (assuming that you have unzipped PHP in c:\php\). Please note that you cannot use php-cli.exe with your webserver, you need to use php.exe which can be found in the sapi directory of your PHP distribution. 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. (.php is recommended. although .phtml and .php3 may be required for legacy applications.) Set up the appropriate security. (This is done in Internet Service Manager), and if your NT Server uses NTFS file system, add execute rights for I_USR_ to the directory that contains php.exe To use the ISAPI module, do the following: If you don't want to perform HTTP Authentication using PHP, you can (and should) skip this step. Under ISAPI Filters, add a new ISAPI filter. Use PHP as the filter name, and supply a path to the php4isapi.dll. Under 'Home Directory', click on the 'Configuration' button. Add a new entry to the Application Mappings. Use the path to the php4isapi.dll as the Executable, supply .php as the extension, leave Method exclusions blank, and check the Script engine checkbox. Stop IIS completely (net stop iisadmin) Start IIS again (net start w3svc)
Installing PHP on Windows with Apache 1.3.x There are two ways to set up PHP to work with Apache 1.3.x
on Windows. One is to use the CGI binary (php.exe),
the other is to use the Apache module dll. In either case
you need to stop the Apache server, and edit your
srm.conf or httpd.conf to configure Apache to work with PHP. Although there can be a few variations of configuring PHP
under Apache, these are simple enough to be used by the
newcomer. Please consult the Apache Docs for further
configuration directives. Now that version 4.1 introduces a safer sapi module, we recommend
that you configure PHP as a module in Apache. To do this, you should move php4ts.dll to the windows/system (for Windows 9x/Me)
or winnt/system32 (for Windows NT/2000/XP) directory, overwriting any
older file. Then you should add the following three lines to your Apache
conf file: (swap c:/php/ for your PHP install path) LoadModule php4_module c:/php/sapi/php4apache.dll
AddModule mod_php4.c
AddType application/x-httpd-php .phpIf you wish to install PHP as a CGI binary, (the sapi is much better)
you need to enable the apache security fix in your php.ini by
setting cgi.force_redirect = 1. Then, insert these lines to your conf file: ScriptAlias /php/ "c:/php/"
AddType application/x-httpd-php .php
Action application/x-httpd-php "/php/php.exe" Please note that you cannot use php-cli.exe with your webserver. You have
to use php.exe which can be found in the sapi directory of your
PHP distribution. As a further precaution, we recommend you change the "/php/"
ScriptAlias to something more random, to prevent any attempts to
call your binary (like the Code Red scripts) for returning a response
other than 404.
Remember when you have finished to restart the server, for example,
NET STOP APACHE
followed by
NET START APACHE To use the source code highlighting feature, add the following
line to your apache httpd.conf file: AddType application/x-httpd-php-source .phps Note, this will only work when you install php as a sapi module.
If you wish to use this feature with the cgi binary, create a new
file, and use the show_source("path/to/original_file.php"); function. On Win-Apache all backslashes in a path statement such
as: "c:\directory\file.ext", must be converted to
forward slashes.
IIS和APACHE可以并存
还有,我现在也开始试着回答网友的一些问题,呵呵!
总是报错
Notice: Undefined index: action in E:\CRM\cn\install\install.php on line 6install源代码:
<?php
include("../common/func.inc.php");
include("../common/lib/adodb.inc.php");
include("install.tools.inc.php");$action = $_REQUEST["action"];
if($action == "showWelcome")
{
showWelcome();
}else if($action == "step1") {
processStep1("");
}else if($action == "step2") {
processStep2("");
}else if($action == "step3") {
processStep3("");
}else {
showWelcome();
}
?>
呵呵,那要恭喜你了呀!
http://www.china-channel.com/template3_index.asp
error_reporting = E_ALL & ~E_NOTICE
Internet Information Server). Installing PHP for PWS/IIS 3 and
PWS/IIS 4 or newer versions. Windows and PWS/IIS 3 - including PWS on Win 9x/ME The recommended method for configuring these servers is to use
the REG file incuded with the distribution (pws-php4cgi.reg).
You may want to edit this file and make sure the extensions and PHP
install directories match your configuration - once you have done
this, just double click on the file and it will update your registry.
Alternatively, you can follow the steps below to do it manually. WARNING:
These steps involve working directly with the Windows
registry. One error here can leave your system in an unstable
state. We highly recommend that you back up your registry
first. The PHP Development team will not be held responsible if
you damage your registry. Run Regedit.
Navigate to:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/W3Svc/Parameters/ScriptMap
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\sapi\php.exe
Repeat these steps for each extension you wish to associate
with PHP scripts.
Please note that you cannot use php-cli.exe with your webserver, you need
to use php.exe which can be found in the sapi directory of your PHP
distribution. The following steps do not affect the web server installation and only
apply if you want your php scripts to be executed when they are run
from the command line (ex. run c:\myscripts\test.php) or by double
clicking on them in a directory viewer window. You may wish to skip
this step as you might prefer the php files to load into a text
editor when you double click on them. Now navigate to: HKEY_CLASSES_ROOT
On the edit menu select: New->Key
Name the key to the extension you setup in the previous
section. ex: .php
Highlight the new key and in the right side pane, double click
the "default value" and enter phpfile.
Repeat the last step for each extension you set up in the
previous section.
Now create another New->Key under
HKEY_CLASSES_ROOT and name it phpfile
Highlight the new key 'phpfile' and in the
right side pane, double click the "default value" and enter
PHP Script.
Right click on the 'phpfile' key and select
New->Key, name it Shell.
Right click on the 'Shell' key and select
New->Key, name it open.
Right click on the 'open' key and select
New->Key, name it command.
Highlight the new key 'command' and in the
right side pane, double click the "default value" and enter
the path to php.exe ex: c:\php\php.exe -q %1
(don't forget the '%1').
Exit Regedit.
If using PWS on Windows, reboot to reload the registry.
PWS and IIS 3 users now have a fully operational system. IIS 3
users can use a nifty tool available at
http://www.genusa.com/iis/iiscfg.html
from Steven Genusa to configure their script maps. Windows NT/2000/XP and IIS 4 or newer and PWS 4 on NT Workstation or W2K non server editions To install PHP on an NT/2000/XP Server running IIS 4 or newer,
follow these instructions. You have two options to set up
PHP, using the CGI binary (php.exe) or with the ISAPI module. In either case, you need to start the Microsoft Management
Console (may appear as 'Internet Services Manager', either
in your Windows NT 4.0 Option Pack branch or the Control
Panel=>Administrative Tools under Windows 2000). Then
right click on your Web server node (this will most probably
appear as 'Default Web Server'), and select 'Properties'. If you want to use the CGI binary, do the following:
Under 'Home Directory', 'Virtual Directory', or
'Directory', click on the 'Configuration' button,
and then enter the App Mappings tab. Click Add, and in the Executable box, type:
c:\php\sapi\php.exe (assuming that you have unzipped PHP in c:\php\). Please note that you cannot use php-cli.exe with your webserver, you need
to use php.exe which can be found in the sapi directory of your PHP
distribution. 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.
(.php is recommended. although .phtml and .php3 may be
required for legacy applications.) Set up the appropriate security. (This is done in Internet
Service Manager), and if your NT Server uses NTFS file system,
add execute rights for I_USR_ to the directory that contains
php.exe To use the ISAPI module, do the following: If you don't want to perform HTTP Authentication using PHP,
you can (and should) skip this step. Under ISAPI Filters,
add a new ISAPI filter. Use PHP as the filter name, and
supply a path to the php4isapi.dll. Under 'Home Directory', click on the 'Configuration' button.
Add a new entry to the Application Mappings. Use the path
to the php4isapi.dll as the Executable, supply .php as the
extension, leave Method exclusions blank, and check the
Script engine checkbox. Stop IIS completely (net stop iisadmin)
Start IIS again (net start w3svc)