Apache HTTP Server Version 2.4
Apache HTTP Server Version 2.4
This document explains how to install, configure and run Apache 2.4 under Microsoft Windows. If you have questions after reviewing the documentation (and any event and error logs), you should consult the peer-supported users' mailing list.
This document assumes that you are installing a binary distribution of Apache. If you want to compile Apache yourself (possibly to help with development or tracking down bugs), see Compiling Apache for Microsoft Windows.
Operating System Requirements Downloading Apache for Windows Customizing Apache for Windows Running Apache as a Service Running Apache as a Console Application Testing the Installation Configuring Access to Network Resources Windows Tuning
The primary Windows platform for running Apache 2.4 is Windows 2000 or later. Always obtain and install the current service pack to avoid operating system bugs.
The Apache HTTP Server Project itself does not provide binary releases of software, only source code. Individual committers may provide binary packages as a convenience, but it is not a release deliverable.
If you cannot compile the Apache HTTP Server yourself, you can obtain a binary package from numerous binary distributions available on the Internet.
Popular options for deploying Apache httpd, and, optionally, PHP and MySQL, on Microsoft Windows, include:
Apache is configured by the files in the conf
subdirectory. These are the same files used to configure the Unix
version, but there are a few different directives for Apache on
Windows. See the directive index
for all the available directives.
The main differences in Apache for Windows are:
Because Apache for Windows is multithreaded, it does not use a separate process for each request, as Apache can on Unix. Instead there are usually only two Apache processes running: a parent process, and a child which handles the requests. Within the child process each request is handled by a separate thread.
The process management directives are also different:
MaxConnectionsPerChild:
Like the Unix directive, this controls how many connections a single
child process will serve before