1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
3 <html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head><!--
4 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
5 This file is generated from xml source: DO NOT EDIT
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
8 <title>Using Apache with Microsoft Windows - Apache HTTP Server</title>
9 <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
10 <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
11 <link href="../style/css/manual-print.css" rel="stylesheet" media="print" type="text/css" />
12 <link href="../images/favicon.ico" rel="shortcut icon" /></head>
13 <body id="manual-page"><div id="page-header">
14 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
15 <p class="apache">Apache HTTP Server Version 2.1</p>
16 <img alt="" src="../images/feather.gif" /></div>
17 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
19 <a href="http://www.apache.org/">Apache</a> > <a href="http://httpd.apache.org/">HTTP Server</a> > <a href="http://httpd.apache.org/docs-project/">Documentation</a> > <a href="../">Version 2.1</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Using Apache with Microsoft Windows</h1>
21 <p>This document explains how to install, configure and run
22 Apache 2.0 under Microsoft Windows. If you find any bugs, or
23 wish to contribute in other ways, please use our <a href="http://httpd.apache.org/bug_report.html">bug reporting
26 <p>This document assumes that you are installing a binary
27 distribution of Apache. If you want to compile Apache yourself
28 (possibly to help with development or tracking down bugs),
29 see <a href="win_compiling.html">Compiling Apache for Microsoft
32 <p><strong>Because of the current versioning policies on Microsoft
33 Windows operating system families, this document assumes the
34 following:</strong></p>
36 <li><strong>Windows NT:</strong> This means all versions of
37 Windows that are based on the Windows NT kernel. Includes Windows
38 NT, Windows 2000, Windows XP and Windows .Net Server 2003.</li>
39 <li><strong>Windows 9x:</strong> This means older,
40 consumer-oriented versions of Windows. Includes Windows 95 (also
41 OSR2), Windows 98 and Windows ME.</li>
45 <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Operating System Requirements</a></li>
46 <li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for Windows</a></li>
47 <li><img alt="" src="../images/down.gif" /> <a href="#inst">Installing Apache for Windows</a></li>
48 <li><img alt="" src="../images/down.gif" /> <a href="#cust">Customizing Apache for Windows</a></li>
49 <li><img alt="" src="../images/down.gif" /> <a href="#winsvc">Running Apache as a Service</a></li>
50 <li><img alt="" src="../images/down.gif" /> <a href="#wincons">Running Apache as a Console Application</a></li>
51 <li><img alt="" src="../images/down.gif" /> <a href="#test">Testing the Installation</a></li>
53 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
55 <h2><a name="req" id="req">Operating System Requirements</a></h2>
58 <p>The primary Windows platform for running Apache 2.0 is Windows
59 NT. The binary installer only works with the x86 family of
60 processors, such as Intel and AMD processors. Running Apache on
61 Windows 9x is not thoroughly tested, and it is never recommended on
65 <p>On all operating systems, TCP/IP networking must be installed
66 and working. If running on Windows 95, the Winsock 2 upgrade must
67 be installed. Winsock 2 for Windows 95 can be downloaded from <a href="http://www.microsoft.com/windows95/downloads/contents/WUAdminTools/S_WUNetworkingTools/W95Sockets2/Default.asp">here</a>.
70 <p>On Windows NT 4.0, installing Service Pack 6 is strongly
71 recommended, as Service Pack 4 created known issues with TCP/IP
72 and Winsock integrity that were resolved in later Service Packs.</p>
73 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
75 <h2><a name="down" id="down">Downloading Apache for Windows</a></h2>
78 <p>Information on the latest versions of Apache can be found on the
79 web site of the Apache web server at
80 <a href="http://httpd.apache.org/download.cgi">http://httpd.apache.org/download.cgi</a>.
81 There you will find the current release, as well as more recent alpha
82 or beta test versions, and a list of HTTP and FTP mirrors from which
83 you can download the Apache web server. Please use a mirror near to
84 you for a fast and reliable download.</p>
86 <p>For Windows installations you should download the version of
87 Apache for Windows with the <code>.msi</code> extension. This is a
88 single Microsoft Installer file, which contains a ready-to-run
89 version of Apache. There is a separate <code>.zip</code> file,
90 which contains only the source code. You can compile Apache
91 yourself with the Microsoft Visual C++ (Visual Studio) tools.</p>
92 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
94 <h2><a name="inst" id="inst">Installing Apache for Windows</a></h2>
97 <p>You need Microsoft Installer 1.2 or above for the installation
98 to work. On Windows 9x you can update your Microsoft Installer to
99 version 2.0 <a href="http://www.microsoft.com/downloads/release.asp?ReleaseID=32831">here</a>
100 and on Windows NT 4.0 and 2000 the version 2.0 update can be found
101 <a href="http://www.microsoft.com/downloads/release.asp?ReleaseID=32832">here</a>.
102 Windows XP does not need this update.</p>
104 <p>Note that you cannot install two versions of Apache 2.0 on the
105 same computer with the binary installer. You can, however, install
106 a version of the 1.3 series <strong>and</strong> a version of the
107 2.0 series on the same computer without problems. If you need to
108 have two different 2.0 versions on the same computer, you have to
109 <a href="win_compiling.html">compile and install Apache from the
112 <p>Run the Apache <code>.msi</code> file you downloaded above. The
113 installation will ask you for these things:</p>
116 <li><p><strong>Network Domain.</strong> Enter the DNS domain in which
117 your server is or will be registered in. For example, if your
118 server's full DNS name is <code>server.mydomain.net</code>, you would
119 type <code>mydomain.net</code> here.</p></li>
121 <li><p><strong>Server Name.</strong> Your server's full DNS name.
122 From the example above, you would type <code>server.mydomain.net</code>
125 <li><p><strong>Administrator's Email Address.</strong> Enter the
126 server administrator's or webmaster's email address here. This
127 address will be displayed along with error messages to the client
130 <li><p><strong>For whom to install Apache</strong> Select <code>for
131 All Users, on Port 80, as a Service - Recommended</code> if you'd
132 like your new Apache to listen at port 80 for incoming traffic.
133 It will run as a service (that is, Apache will run even if no one
134 is logged in on the server at the moment) Select <code>only for
135 the Current User, on Port 8080, when started Manually</code> if
136 you'd like to install Apache for your personal experimenting or
137 if you already have another WWW server running on port 80.</p></li>
139 <li><p><strong>The installation type.</strong> Select <code>Typical</code>
140 for everything except the source code and libraries for module
141 development. With <code>Custom</code> you can specify what to
142 install. A full install will require about 13 megabytes of free
143 disk space. This does <em>not</em> include the size of your web
146 <li><p><strong>Where to install.</strong> The default path is
147 <code>C:\Program Files\Apache Group</code> under which a directory
148 called <code>Apache2</code> will be created by default.</p></li>
151 <p>During the installation, Apache will configure the files in the
152 <code>conf</code> subdirectory to reflect the chosen installation
153 directory. However, if any of the configuration files in this
154 directory already exist, they will not be overwritten. Instead, the
155 new copy of the corresponding file will be left with the extension
156 <code>.default</code>. So, for example, if <code>conf\httpd.conf</code>
157 already exists, it will be renamed as <code>conf\httpd.conf.default</code>.
158 After the installation you should manually check to see what new
159 settings are in the <code>.default</code> file, and if necessary,
160 update your existing configuration file.</p>
162 <p>Also, if you already have a file called <code>htdocs\index.html</code>,
163 it will not be overwritten (and no <code>index.html.default</code>
164 will be installed either). This means it should be safe to install
165 Apache over an existing installation, although you would have to
166 stop the existing running server before doing the installation, and
167 then start the new one after the installation is finished.</p>
169 <p>After installing Apache, you must edit the configuration files
170 in the <code>conf</code> subdirectory as required. These files
171 will be configured during the installation so that Apache is ready
172 to be run from the directory it was installed into, with the
173 documents server from the subdirectory <code>htdocs</code>. There
174 are lots of other options which you should set before you really
175 start using Apache. However, to get started quickly, the files
176 should work as installed.</p>
177 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
178 <div class="section">
179 <h2><a name="cust" id="cust">Customizing Apache for Windows</a></h2>
182 <p>Apache is configured by the files in the <code>conf</code>
183 subdirectory. These are the same files used to configure the Unix
184 version, but there are a few different directives for Apache on
185 Windows. See the <a href="../mod/directives.html">directive index</a>
186 for all the available directives.</p>
188 <p>The main differences in Apache for Windows are:</p>
190 <li><p>Because Apache for Windows is multithreaded, it does not
191 use a separate process for each request, as Apache does on Unix.
192 Instead there are usually only two Apache processes running: a
193 parent process, and a child which handles the requests. Within
194 the child process each request is handled by a separate thread.
197 <p>The process management directives are also different:</p>
199 <p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code>:
200 Like the Unix directive, this controls how many requests a single
201 child process will serve before exiting. However, unlike on Unix,
202 a single process serves all the requests at once, not just one.
203 If this is set, it is recommended that a very high number is
204 used. The recommended default, <code>MaxRequestsPerChild 0</code>,
205 causes the child process to never exit.</p>
207 <div class="warning"><strong>Warning: The server configuration
208 file is reread when a new child process is started. If you have
209 modified <code>httpd.conf</code>, the new child may not start or
210 you may receive unexpected results.</strong></div>
212 <p><code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>:
213 This directive is new. It tells the server how many threads it
214 should use. This is the maximum number of connections the server
215 can handle at once, so be sure to set this number high enough for
216 your site if you get a lot of hits. The recommended default is
217 <code>ThreadsPerChild 50</code>.</p></li>
219 <li><p>The directives that accept filenames as arguments must use
220 Windows filenames instead of Unix ones. However, because Apache
221 uses Unix-style names internally, you must use forward slashes,
222 not backslashes. Drive letters can be used; if omitted, the drive
223 with the Apache executable will be assumed.</p></li>
225 <li><p>Apache for Windows contains the ability to load modules at
226 runtime, without recompiling the server. If Apache is compiled
227 normally, it will install a number of optional modules in the
228 <code>\Apache2\modules</code> directory. To activate these or
229 other modules, the new <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>
230 directive must be used. For example, to activate the status
231 module, use the following (in addition to the status-activating
232 directives in <code>access.conf</code>):</p>
234 <div class="example"><p><code>
235 LoadModule status_module modules/mod_status.so
238 <p>Information on <a href="../mod/mod_so.html#creating">creating
239 loadable modules</a> is also available.</p></li>
241 <li><p>Apache can also load ISAPI (Internet Server Application
242 Programming Interface) extensions (i.e. internet server
243 applications), such as those used by Microsoft IIS and other
244 Windows servers. <a href="../mod/mod_isapi.html">More information
245 is available</a>. Note that Apache <strong>cannot</strong> load
246 ISAPI Filters.</p></li>
248 <li><p>When running CGI scripts, the method Apache uses to find
249 the interpreter for the script is configurable using the
250 <code class="directive"><a href="../mod/core.html#scriptinterpretersource">ScriptInterpreterSource</a></code>
253 <li><p>Since it is often difficult to manage files with names
254 like <code>.htaccess</code> in Windows, you may find it useful to
255 change the name of this per-directory configuration file using
256 the <code class="directive"><a href="../mod/core.html#accessfilename">AccessFilename</a></code>
259 <li><p>Any errors during Apache startup are logged into the
260 Windows event log when running on Windows NT. This mechanism
261 acts as a backup for those situations where Apache cannot even
262 access the normally used <code>error.log</code> file. You can
263 view the Windows event log by using the Event Viewer application
264 on Windows NT 4.0, and the Event Viewer MMC snap-in on newer
265 versions of Windows.</p>
267 <div class="note"><strong>Note that there is no startup error logging on
268 Windows 9x because no Windows event log exists on those operating
269 systems.</strong></div></li>
272 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
273 <div class="section">
274 <h2><a name="winsvc" id="winsvc">Running Apache as a Service</a></h2>
277 <p>Apache can be run as a service on Windows NT. There is some
278 highly experimental support for similar behavior on Windows 9x.</p>
280 <p>You can install Apache as a service automatically during the
281 installation. If you chose to install for all users, the
282 installation will create an Apache service for you. If you specify
283 to install for yourself only, you can manually register Apache as a
284 service after the installation. You have to be a member of the
285 Administrators group for the service installation to succeed.</p>
287 <p>Apache comes with a utility called the Apache Service Monitor.
288 With it you can see and manage the state of all installed Apache
289 services on any machine on your network. To be able to manage an
290 Apache service with the monitor, you have to first install the
291 service (either automatically via the installation or manually).
294 <p>You can install Apache as a Windows NT service as follows from
295 the command prompt at the Apache <code>bin</code> subdirectory:</p>
297 <div class="example"><p><code>
301 <p>If you need to specify the name of the service you want to
302 install, use the following command. You have to do this if you
303 have several different service installations of Apache on your
306 <div class="example"><p><code>
307 apache -k install -n "MyServiceName"
310 <p>If you need to have specifically named configuration files for
311 different services, you must use this:</p>
313 <div class="example"><p><code>
314 apache -k install -n "MyServiceName" -f "c:\files\my.conf"
317 <p>If you use the first command without any special parameters except
318 <code>-k install</code>, the service will be called <code>Apache2</code>
319 and the configuration will be assumed to be <code>conf\httpd.conf</code>.
322 <p>Removing an Apache service is easy. Just use:</p>
324 <div class="example"><p><code>
328 <p>The specific Apache service to be uninstalled can be specified by using:</p>
330 <div class="example"><p><code>
331 apache -k uninstall -n "MyServiceName"
334 <p>Normal starting, restarting and shutting down of an Apache
335 service is usually done via the Apache Service Monitor, by using
336 commands like <code>NET START Apache2</code> and <code>NET STOP
337 Apache2</code> or via normal Windows service management. Before
338 starting Apache as a service by any means, you should test the
339 service's configuration file by using:</p>
341 <div class="example"><p><code>
342 apache -n "MyServiceName" -t
345 <p>You can control an Apache service by its command line switches,
346 too. To start an installed Apache service you'll use this:</p>
348 <div class="example"><p><code>
352 <p>To stop an Apache service via the command line switches, use
355 <div class="example"><p><code>
361 <div class="example"><p><code>
365 <p>You can also restart a running service and force it to reread
366 its configuration file by using:</p>
368 <div class="example"><p><code>
372 <p>By default, all Apache services are registered to run as the
373 system user (the <code>LocalSystem</code> account). The
374 <code>LocalSystem</code> account has no privileges to your network
375 via any Windows-secured mechanism, including the file system, named
376 pipes, DCOM, or secure RPC. It has, however, wide privileges locally.
379 <div class="warning"><strong>Never grant any network privileges to
380 the <code>LocalSystem</code> account! If you need Apache to be able
381 to access network resources, create a separate account for Apache as
382 noted below.</strong></div>
384 <p>You may want to create a separate account for running Apache
385 service(s). Especially, if you have to access network resources
386 via Apache, this is strongly recommended.</p>
389 <li>Create a normal domain user account, and be sure to
390 memorize its password.</li>
392 <li>Grant the newly-created user a privilege of <code>Log on
393 as a service</code> and <code>Act as part of the operating
394 system</code>. On Windows NT 4.0 these privileges are granted via
395 User Manager for Domains, but on Windows 2000 and XP you probably
396 want to use Group Policy for propagating these settings. You can
397 also manually set these via the Local Security Policy MMC snap-in.
400 <li>Confirm that the created account is a member of the Users
403 <li>Grant the account read and execute (RX) rights to all document
404 and script folders (<code>htdocs</code> and <code>cgi-bin</code>
407 <li>Grant the account change (RWXD) rights to the
408 Apache <code>logs</code> directory.</li>
410 <li>Grant the account read and execute (RX) rights to the
411 <code>Apache.exe</code> binary executable.</li>
414 <div class="note">It is usually a good practice to grant the user the Apache
415 service runs as read and execute (RX) access to the whole Apache2
416 directory, except the <code>logs</code> subdirectory, where the
417 user has to have at least change (RWXD) rights.</div>
419 <p>If you allow the account to log in as a user and as a service,
420 then you can log on with that account and test that the account has the
421 privileges to execute the scripts, read the web pages, and that
422 you can start Apache in a console window. If this works, and you
423 have followed the steps above, Apache should execute as a service
424 with no problems.</p>
426 <div class="note"><strong>Error code 2186</strong> is a good indication that
427 you need to review the "Log On As" configuration for the service,
428 since Apache cannot access a required network resource. Also, pay
429 close attention to the privileges of the user Apache is
430 configured to run as.</div>
432 <p>When starting Apache as a service you may encounter an error
433 message from the Windows Service Control Manager. For example,
434 if you try to start Apache by using the Services applet in the
435 Windows Control Panel, you may get the following message:</p>
437 <div class="example"><p><code>
438 Could not start the Apache2 service on \\COMPUTER <br />
439 Error 1067; The process terminated unexpectedly.
442 <p>You will get this generic error if there is any problem with
443 starting the Apache service. In order to see what is really causing
444 the problem you should follow the instructions for Running Apache
445 for Windows from the Command Prompt.</p>
447 <p>There is some support for Apache on Windows 9x to behave in a
448 similar manner as a service on Windows NT. It is <strong>highly
449 experimental</strong>. It is not of production-class reliability,
450 and its future is not guaranteed. It can be mostly regarded as
451 a risky thing to play with - proceed with caution!</p>
453 <p>There are some differences between the two kinds of services
454 you should be aware of:</p>
457 <li><p>Apache will attempt to start and if successful it will run
458 in the background. If you run the command</p>
460 <div class="example"><p><code>
461 apache -n "MyServiceName" -k start
464 <p>via a shortcut on your desktop, for example, then if the
465 service starts successfully, a console window will flash up but
466 it immediately disappears. If Apache detects any errors on startup
467 such as incorrect entries in the httpd.conf configuration file,
468 the console window will remain visible. This will display an error
469 message which will be useful in tracking down the cause of the
472 <li><p>Windows 9x does not support <code>NET START</code> or
473 <code>NET STOP</code> commands. You must control the Apache
474 service on the command prompt via the <code>-k</code> switches.
477 <li><p>Apache and Windows 9x offer no support for running Apache
478 as a specific user with network privileges. In fact, Windows 9x
479 offers no security on the local machine, either. This is the
480 simple reason because of which the Apache Software Foundation
481 never endorses use of a Windows 9x -based system as a public
482 Apache server. The primitive support for Windows 9x exists only
483 to assist the user in developing web content and learning the
484 Apache server, and perhaps as an intranet server on a secured,
485 private network.</p></li>
489 <p>Once you have confirmed that Apache runs correctly as a
490 console application you can install, control and uninstall the
491 pseudo-service with the same commands as on Windows NT. You can
492 also use the Apache Service Monitor to manage Windows 9x
495 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
496 <div class="section">
497 <h2><a name="wincons" id="wincons">Running Apache as a Console Application</a></h2>
500 <p>Running Apache as a service is usually the recommended way to
501 use it, but it is sometimes easier to work from the command line
502 (on Windows 9x running Apache from the command line is the
503 recommended way due to the lack of reliable service support.)</p>
505 <p>To run Apache from the command line as a console application,
506 use the following command:</p>
508 <div class="example"><p><code>
512 <p>Apache will execute, and will remain running until it is stopped
513 by pressing Control-C.</p>
515 <p>You can also run Apache via the shortcut Start Apache in Console
516 placed to <code>Start Menu --> Programs --> Apache HTTP Server
517 2.0.xx --> Control Apache Server</code> during the installation.
518 This will open a console window and start Apache inside it. If you
519 don't have Apache installed as a service, the window will remain
520 visible until you stop Apache by pressing Control-C in the console
521 window where Apache is running in. The server will exit in a few
522 seconds. However, if you do have Apache installed as a service, the
523 shortcut starts the service. If the Apache service is running
524 already, the shortcut doesn't do anything.</p>
526 <p>You can tell a running Apache to stop by opening another console
527 window and entering:</p>
529 <div class="example"><p><code>
533 <p>This should be preferred over pressing Control-C because this
534 lets Apache end any current operations and clean up gracefully.</p>
536 <p>You can also tell Apache to restart. This forces it to reread
537 the configuration file. Any operations in progress are allowed to
538 complete without interruption. To restart Apache, use:</p>
540 <div class="example"><p><code>
544 <div class="note">Note for people familiar with the Unix version of Apache:
545 these commands provide a Windows equivalent to <code>kill -TERM
546 <em>pid</em></code> and <code>kill -USR1 <em>pid</em></code>. The
547 command line option used, <code>-k</code>, was chosen as a reminder
548 of the <code>kill</code> command used on Unix.</div>
550 <p>If the Apache console window closes immediately or unexpectedly
551 after startup, open the Command Prompt from the Start Menu -->
552 Programs. Change to the folder to which you installed Apache, type
553 the command <code>apache</code>, and read the error message. Then
554 change to the logs folder, and review the <code>error.log</code>
555 file for configuration mistakes. If you accepted the defaults when
556 you installed Apache, the commands would be:</p>
558 <div class="example"><p><code>
560 cd "\Program Files\Apache Group\Apache2\bin" <br />
564 <p>Then wait for Apache to stop, or press Control-C. Then enter the
567 <div class="example"><p><code>
572 <p>When working with Apache it is important to know how it will
573 find the configuration file. You can specify a configuration file
574 on the command line in two ways:</p>
577 <li><p><code>-f</code> specifies an absolute or relative path to
578 a particular configuration file:</p>
580 <div class="example"><p><code>
581 apache -f "c:\my server files\anotherconfig.conf"
586 <div class="example"><p><code>
587 apache -f files\anotherconfig.conf
588 </code></p></div></li>
590 <li><p><code>-n</code> specifies the installed Apache service
591 whose configuration file is to be used:</p>
593 <div class="example"><p><code>
594 apache -n "MyServiceName"
599 <p>In both of these cases, the proper
600 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> should be set in
601 the configuration file.</p>
603 <p>If you don't specify a configuration file with <code>-f</code>
604 or <code>-n</code>, Apache will use the file name compiled into the
605 server, such as <code>conf\httpd.conf</code>. This built-in path
606 is relative to the installation directory. You can verify the compiled
607 file name from a value labelled as <code>SERVER_CONFIG_FILE</code> when
608 invoking Apache with the <code>-V</code> switch, like this:</p>
610 <div class="example"><p><code>
614 <p>Apache will then try to determine its <code class="directive"><a href="../mod/core.html# serverroot">
615 ServerRoot</a></code> by trying the following, in this order:</p>
618 <li>A <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive
619 via the <code>-C</code> command line switch.</li>
621 <li>The <code>-d</code> switch on the command line.</li>
623 <li>Current working directory.</li>
625 <li>A registry entry which was created if you did a binary
628 <li>The server root compiled into the server. This is <code>
629 /apache</code> by default, you can verify it by using <code>
630 apache -V</code> and looking for a value labelled as
631 <code>HTTPD_ROOT</code>.</li>
634 <p>During the installation, a version-specific registry key is
635 created in the Windows registry. The location of this key depends
636 on the type of the installation. If you chose to install Apache
637 for all users, the key is located under the
638 <code>HKEY_LOCAL_MACHINE</code> hive, like this (the version
639 numbers will of course vary between different versions of Apache:
642 <div class="example"><p><code>
643 HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache\2.0.43
646 <p>Correspondingly, if you chose to install Apache for the current
647 user only, the key is located under the <code>HKEY_CURRENT_USER</code>
648 hive, the contents of which are dependent of the user currently
651 <div class="example"><p><code>
652 HKEY_CURRENT_USER\SOFTWARE\Apache Group\Apache\2.0.43
655 <p>This key is compiled into the server and can enable you to test
656 new versions without affecting the current version. Of course, you
657 must take care not to install the new version in the same
658 directory as another version.</p>
660 <p>If you did not do a binary install, Apache will in some
661 scenarios complain about the missing registry key. This warning can
662 be ignored if the server was otherwise able to find its
663 configuration file.</p>
665 <p>The value of this key is the
666 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directory which
667 contains the <code>conf</code> subdirectory. When Apache starts it
668 reads the <code>httpd.conf</code> file from that directory. If
669 this file contains a <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>
670 directive which contains a different directory from the one
671 obtained from the registry key above, Apache will forget the
672 registry key and use the directory from the configuration file. If
673 you copy the Apache directory or configuration files to a new
674 location it is vital that you update the
675 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive in the
676 <code>httpd.conf</code> file to reflect the new location.</p>
678 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
679 <div class="section">
680 <h2><a name="test" id="test">Testing the Installation</a></h2>
683 <p>After starting Apache (either in a console window or as a
684 service) it will be listening on port 80 (unless you changed the
685 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the
686 configuration files or installed Apache only for the current user).
687 To connect to the server and access the default page, launch a
688 browser and enter this URL:</p>
690 <div class="example"><p><code>
694 <p>Apache should respond with a welcome page and a link to the
695 Apache manual. If nothing happens or you get an error, look in the
696 <code>error.log</code> file in the <code>logs</code> subdirectory.
697 If your host is not connected to the net, or if you have serious
698 problems with your DNS (Domain Name Service) configuration, you
699 may have to use this URL:</p>
701 <div class="example"><p><code>
705 <p>Once your basic installation is working, you should configure it
706 properly by editing the files in the <code>conf</code> subdirectory.
707 Again, if you change the configuration of the Windows NT service
708 for Apache, first attempt to start it from the command line to
709 make sure that the service starts with no errors.</p>
711 <p>Because Apache <strong>cannot</strong> share the same port with
712 another TCP/IP application, you may need to stop, uninstall or reconfigure
713 certain other services before running Apache. These conflicting
714 services include other WWW servers and some firewall implementations.
719 <p class="apache">Maintained by the <a href="http://httpd.apache.org/docs-project/">Apache HTTP Server Documentation Project</a></p>
720 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/directives.html">Directives</a> | <a href="../faq/">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div>