PHP
downloads | documentation | faq | getting help | mailing lists | reporting bugs | php.net sites | links | conferences | my php.net

search for in the

Sun, iPlanet and Netscape servers on Microsoft Windows> <Apache 1.3.x on Microsoft Windows
Last updated: Fri, 15 Aug 2008

view this page in

Apache 2.0.x on Microsoft Windows

This section contains notes and hints specific to Apache 2.0.x installs of PHP on Microsoft Windows systems. We also have instructions and notes for Apache 1.3.x users on a separate page.

Note: You should read the manual installation steps first!

Note: Apache 2.2.x Support
Users of Apache 2.2.x may use the documentation below except the appropriate DLL file is named php5apache2_2.dll and it only exists as of PHP 5.2.0. See also » http://snaps.php.net/

Warning

We do not recommend using a threaded MPM in production with Apache 2. Use the prefork MPM instead, or use Apache 1. For information on why, read the related FAQ entry on using Apache2 with a threaded MPM

You are highly encouraged to take a look at the » Apache Documentation to get a basic understanding of the Apache 2.0.x Server. Also consider to read the » Windows specific notes for Apache 2.0.x before reading on here.

Note: PHP and Apache 2.0.x compatibility notes
The following versions of PHP are known to work with the most recent version of Apache 2.0.x:

These versions of PHP are compatible to Apache 2.0.40 and later.
Apache 2.0 SAPI-support started with PHP 4.2.0. PHP 4.2.3 works with Apache 2.0.39, don't use any other version of Apache with PHP 4.2.3. However, the recommended setup is to use PHP 4.3.0 or later with the most recent version of Apache2.
All mentioned versions of PHP will work still with Apache 1.3.x.

Warning

Apache 2.0.x is designed to run on Windows NT 4.0, Windows 2000 or Windows XP. At this time, support for Windows 9x is incomplete. Apache 2.0.x is not expected to work on those platforms at this time.

Download the most recent version of » Apache 2.0.x and a fitting PHP version. Follow the Manual Installation Steps and come back to go on with the integration of PHP and Apache.

There are two ways to set up PHP to work with Apache 2.0.x on Windows. One is to use the CGI binary the other is to use the Apache module DLL. In either case you need to edit your httpd.conf to configure Apache to work with PHP and then restart the server.

Note: Remember that when adding path values in the Apache configuration files on Windows, all backslashes such as c:\directory\file.ext must be converted to forward slashes: c:/directory/file.ext. A trailing slash may also be necessary for directories.

Installing as a CGI binary

You need to insert these three lines to your Apache httpd.conf configuration file to set up the CGI binary:

Example #1 PHP and Apache 2.0 as CGI

ScriptAlias /php/ "c:/php/"
AddType application/x-httpd-php .php

# For PHP 4
Action application/x-httpd-php "/php/php.exe"

# For PHP 5
Action application/x-httpd-php "/php/php-cgi.exe"

Warning

A server deployed in CGI mode is open to several possible vulnerabilities. Please read our CGI security section to learn how to defend yourself from such attacks.

Installing as an Apache module

You need to insert these two lines to your Apache httpd.conf configuration file to set up the PHP module for Apache 2.0:

Example #2 PHP and Apache 2.0 as Module

# For PHP 4 do something like this:
LoadModule php4_module "c:/php/php4apache2.dll"
# Don't forget to copy the php4apache2.dll file from the sapi directory!
AddType application/x-httpd-php .php

# For PHP 5 do something like this:
LoadModule php5_module "c:/php/php5apache2.dll"
AddType application/x-httpd-php .php

# configure the path to php.ini
PHPIniDir "C:/php"

Note: Remember to substitute your actual path to PHP for the c:/php/ in the above examples. Take care to use either php4apache2.dll or php5apache2.dll in your LoadModule directive and not php4apache.dll or php5apache.dll as the latter ones are designed to run with Apache 1.3.x.

Note: If you want to use content negotiation, read related FAQ.

Warning

Don't mix up your installation with DLL files from different PHP versions. You have the only choice to use the DLL's and extensions that ship with your downloaded PHP version.



add a note add a note User Contributed Notes
Apache 2.0.x on Microsoft Windows
webssfz at gmail dot com
30-Jun-2008 06:52
@eric dot zhang at rogers dot com:
The line is not necessary since the installer adds these lines to mime.types:
application/x-httpd-php    php
application/x-httpd-php-source    phps
eric dot zhang at rogers dot com
12-Jun-2008 09:44
for me, I have xp, apache 2.2 and php 5.2.6,
to install, just use the installer and choose your modules during installation, and every thing works fine.
After install, I check the httpd.conf and found nothing about "AddType ..." so I assume you don't need it
cormac at kernan dot eu
20-Apr-2008 09:08
All good advice from henke, except where it says "Do not edit the system path".  You will NOT be able to load extensions that have dependencies e.g. MySQL, without adding PHP to your system path.  This threw me for some time as other extensions without dependencies will work without this requirement.
henke at henke37 dot cjb dot net
22-Feb-2008 08:22
Please completely ignore the page contents, it's stale garbage and will just lead to trouble.

Here is how to do it the right way:
Do not copy any php files anywhere
Do not edit the system path
And absolutely do not use the provided cgi directives.

Here is the proper apache directives to load php, preferbly saved as php.conf and included from your main config.

#load the php main library to avoid dll hell
Loadfile "C:\pathtophp\php5ts.dll"

#load the sapi so that apache can use php
LoadModule php5_module "C:\pathtophp\php5apache2_2.dll"

#set the php.ini location so that you don't have to waste time guessing where it is
PHPIniDir "C:\pathtophp"

#Hook the php file extensions, notice that Addtype is NOT USED, since that's just stupid
AddHandler application/x-httpd-php .php
AddHandler application/x-httpd-php-source .phps
cfoesterle at yahoo dot com
10-Feb-2008 01:41
I do not have IIS installed on my server, only Apache. So I had to edit the PHP.ini file and comment out (add leading ";") to the following line "extension=php_iisfunc.dll" as I was getting "Faulting application httpd.exe, faulting module php_iisfunc.dll" errors when this line was active. I also added an additional  "AddType application/x-httpd-php .html" to my httpd.conf file so that inline php would work with files ending with an extension of ".html" on my server.
mjm at alum dot mit dot edu
27-Jan-2008 01:33
If you use the PHP 5 installer, you'll notice that it uses the wrong type of slash on Windows!

Change C:/Program Files/PHP/" to C:\Program Files\PHP\" and everything works great!
rene at metalbunny dot net
27-Nov-2007 07:40
Installed Apache 2.2.6 on WinXP Pro SP2 with PHP 5.2.5 as server module (php5apache2_2.dll)...

Thanks to melanie_c_graham's post, I solved my trouble by commenting out the
PHPIniDir "C:/Program Files/PHP/"
in httpd.conf

With this line present, Apache will generate two "Apache has experienced a problem and needs to close" when attempting to shut down the httpd service.

Starting it up is just smooth, but on shutdown it fails - and with the line present, PHP isn't processed; just produces a blank page (not even an error message).
mhfaust at gmail dot com
23-Nov-2007 12:40
My context -- configuring:
- Windows XP/SP2
- Apache 2.2.6
- PHP 5.2.4 (as Apache module)

I had a problem with PHPIniDir (not loading), when setting it this way:
   PHPIniDir "C:\PHP\"

....but it worked when I changed it to:
   PHPIniDir "C:\PHP"

(deleted trailing slash)

-----------
....This seems relevant to the comment from:
Isaac dot Brown at ArvinMeritor dot com
17-May-2005 06:59

...and contradicts the line in the instructions at the top of this page "A trailing slash may also be necessary for directories."
packard_bell_nec at hotmail dot com
02-Oct-2007 11:24
If you install PHP as an Apache CGI binary, you can add:
AddHandler cgi-script .php
into Apache httpd.conf, and add shebang line to every PHP scripts like:
#!php
<?php
phpinfo
();
?>
. But adding shebang line has a disadvantage that if you decided to install PHP as an Apache module afterwards, then the shebang line WILL appear in the web page.
In fact, you do NOT need to add shebang line to every PHP script even if you install PHP as an Apache CGI binary, because you can add:
ScriptInterpreterSource Registry-Strict
into Apache httpd.conf, and make the registry file and merge it like:
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.php\Shell\ExecCGI\Command]
@="\"C:\\Program Files\\PHP\\php-cgi.exe\""
. Then you will NOT need to change the PHP scripts which do not contain shebang line.
simon dot schmitt at med dot uni-heidelberg dot de
28-Sep-2007 10:43
Zend and Microsoft today announced FastCGI for IIS6 and higher: I tried it and it works fine.
Heres the link to the documentation: http://www.iis.net/php
newbe
17-Sep-2007 10:24
I very thank Richard about the following because my appache2.2.4 could't load php5apache2.dll all the time. Then, I found the right answer as below! Good luck!

richard dot blockley at googlemail dot com
21-Aug-2007 08:34
At time of writing this, Apache 2.2 is out. For PHP5 with Apache 2.2, I believe one has to use the module file php5apache2_2.dll. As opposed to php5apache2.dll
melanie_c_graham at hotmail dot com
01-Sep-2007 06:40
For some reason, installing Apache and PHP, I could not use this line item:

PHPIniDir "C:/php"

If I used it, my web server would not restart.  I commented the line out, and voila - PHP is installed perfectly (after an hour or two of swearing at it) and Apache is happy again.

I am going to operate under the assumption that since my system is working just fine without this ini redirection that ini redirection is not required for my configuration.

I am running Windows XP Home, Apache 2.2.4, PHP 5.2.4
richard dot blockley at googlemail dot com
21-Aug-2007 06:34
At time of writing this, Apache 2.2 is out. For PHP5 with Apache 2.2, I believe one has to use the module file php5apache2_2.dll. As opposed to php5apache2.dll.
philippeboucher at newlogiccanada dot com dot com
31-Jul-2007 05:05
To do a silent install of PHP wich correctly modify the httpd.conf file, you HAVE (I find no other way) to put the directory of the Apache inside the INSTALLDIR's MSI option.  the APACHEDIR doesn't seem to work.  That's the only way I've make it work.  Maybe it's because my Apache is not in the default directory, I don't know, but there is a solution for people who cannot make work the silent install (for those who are told by the php setup that it cannot find the httpd.conf file).

Hope it helps someone.
anonymousness
15-Jun-2007 10:30
Verrrrrrrry important note:

If you enable multi-byte strings for your installation of PHP, the extension loaded MUST be the first extension in the list.

Apache, NOR PHP will generate any error messages or warning information in the error log or in system logs about this.

This information needs to be included in the Readme or in the distributed INI files.

The recommended PHP ini's should place extension=php_mbstring.dll  at the top of the list of extensions.

I had completely forgotten about this when recently upgrading php on a test server; and almost set out to re-install apache.
charlie at oblivion dot cz
14-Feb-2007 09:19
..try to set the extension_dir in php.ini to the absolute path.. (when you are pretty sure that you have set the PHPIniDir the right way)
Jim Keller
10-Jan-2007 10:35
it's important to note that on Apache 2.2.3 (probably other 2.x versions as well) on Windows, the PHPIniDir directive must use forward slashes to delimit directories, not the backslashes commonly used for Windows path strings. If PHP seems to be ignoring the directive, this may be why.
pcdinh at phpvietnam dot net
07-Oct-2006 06:50
PHP 6 is under active development but for those whose want to try out the new features or just want to keep updated with the development progress of PHP 6.0, you can follow my instructions below to install it on Windows XP and Apache 2.2.3

# For PHP 6 do something like this:
LoadModule php5_module "c:/server/php6/php6apache2_2.dll"
AddType application/x-httpd-php .php
PHPIniDir "c:/server/php6"

You should change the path as in your system. The directive LoadModule php5_module seems a bit strange to you. It should be LoadModule php6_module instead. However, I have just taken a look at php.internals and came across a message that said it should be changed in the near future after the PHP 5.2 is official released. At the time I write this, PHP 5.2 RC6 is planned to be released in the next few days.
k2wardog at yahoo dot com
06-Sep-2006 10:55
I was also having the 403 forbidden error.  Removing the trailing backslash from the script alias as well as adding the following lines solved the issue:

<Directory "C:/php">
   AllowOverride None
   Options None
   Order allow,deny
   Allow from all
</Directory>

Thanks for the help boss.
subajawa at yahoo dot com
04-Aug-2006 04:56
To install PHP as Apache 2 CGI script, add these lines in addition to the 3 lines mentioned in the document.

<Directory "C:/php">
    AllowOverride None
    Options None
    Order allow,deny
    Allow from all
</Directory>
04-Aug-2006 04:31
There is a mistake in documentation regarding installation of PHP as Apache 2 CGI script. The ScriptAlias directive should not have trailing slash on 'php' as it then means that 'php' should be part of the URL, just like 'cgi-bin' usually is, and in case of PHP this leads to 403 Forbidden.

Instead, this is the correct directive (no trailing slash on 'php'):

ScriptAlias /php "C:/path/to/PHP/dir"
12-Dec-2005 08:12
There are often strong suggestions that Apache/MySQL/PHP should be set up in the Windows root folder, and dire warnings against using folders with spaces in the name. But as a relatively non-technical user, I hate cluttering my Windows XP root directory with folders that should be under Program Files, and of keeping any documents other than in "My Documents" (even though I agree that MS's folder tree is ugly).

Frankly I've never had any difficulty with Apache and MySQL under Program Files, PHP5 deep in the Apache tree, and all documents under My Docs.. Here are the related Apache 2 config lines I use in case anyone is interested (sorry if there are broken lines):

ServerRoot "C:/Program Files/Apache Group/Apache2"

DocumentRoot "C:/Documents and settings/UserNm/My Documents/Websites"

# PHP 5 module
LoadModule php5_module "c:/Program Files/Apache Group/Apache2/php5/php5apache2.dll"
AddType application/x-httpd-php .php
PHPIniDir "C:/Program Files/Apache Group/Apache2/php5/"
withheld at withheld dot com
06-Aug-2005 09:40
BTW I use Win9x to develop but it's not a production server. And yes, adding a trailing slash to the PHPIniDir directive helps.
Isaac dot Brown at ArvinMeritor dot com
17-May-2005 08:59
Some XP machines are having troubles with the PHPIniDir derective not finding the php.ini (or so they think). Directories that do contain a php.ini file are returned as empty and it defaults to the next method of finding php.ini (often C:/windows or C:/winnt).

This is likely caused by read permissions not being set correctly on NTFS file systems, however, it has occurred when no cause could be identified. If setting correct file permissions doesn't work, the easiest way around this problem is moving php.ini to the Apache directory or adding the HKEY_LOCAL_MACHINE\SOFTWARE\PHP\IniFilePath string to your registry and setting it to the correct directory.
wrowe at apache dot org
11-Apr-2005 08:26
Although the warning above reads "We do not recommend using a threaded MPM in production with Apache2" - ignore that nonsense for Win32.

All Apache/Win32 builds were *always* threaded.  Always choose Apache 2 over Apache 1.3 on Windows - because major portions of Apache 2 were written from the ground up to accept Windows.

Apache 1.3 was never designed for threads or non-posix systems.  For Windows they were squirled in with some rather ugly hacks, which will never enjoy much improvement.

 
show source | credits | sitemap | contact | advertising | mirror sites