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><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> |
22 <a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
26 <p>This document explains how to install, configure and run
27 Apache 2.0 under Microsoft Windows. If you find any bugs, or
28 wish to contribute in other ways, please use our <a href="http://httpd.apache.org/bug_report.html">bug reporting
31 <p>This document assumes that you are installing a binary
32 distribution of Apache. If you want to compile Apache yourself
33 (possibly to help with development or tracking down bugs),
34 see <a href="win_compiling.html">Compiling Apache for Microsoft
37 <p><strong>Because of the current versioning policies on Microsoft
38 Windows operating system families, this document assumes the
39 following:</strong></p>
41 <li><strong>Windows NT:</strong> This means all versions of
42 Windows that are based on the Windows NT kernel. Includes Windows
43 NT, Windows 2000, Windows XP and Windows .Net Server 2003.</li>
44 <li><strong>Windows 9x:</strong> This means older,
45 consumer-oriented versions of Windows. Includes Windows 95 (also
46 OSR2), Windows 98 and Windows ME.</li>
50 <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Operating System Requirements</a></li>
51 <li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for Windows</a></li>
52 <li><img alt="" src="../images/down.gif" /> <a href="#inst">Installing Apache for Windows</a></li>
53 <li><img alt="" src="../images/down.gif" /> <a href="#cust">Customizing Apache for Windows</a></li>
54 <li><img alt="" src="../images/down.gif" /> <a href="#winsvc">Running Apache as a Service</a></li>
55 <li><img alt="" src="../images/down.gif" /> <a href="#wincons">Running Apache as a Console Application</a></li>
56 <li><img alt="" src="../images/down.gif" /> <a href="#test">Testing the Installation</a></li>
58 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
60 <h2><a name="req" id="req">Operating System Requirements</a></h2>
63 <p>The primary Windows platform for running Apache 2.0 is Windows
64 NT. The binary installer only works with the x86 family of
65 processors, such as Intel and AMD processors. Running Apache on
66 Windows 9x is not thoroughly tested, and it is never recommended on
70 <p>On all operating systems, TCP/IP networking must be installed
71 and working. If running on Windows 95, the Winsock 2 upgrade must
72 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>.
75 <p>On Windows NT 4.0, installing Service Pack 6 is strongly
76 recommended, as Service Pack 4 created known issues with TCP/IP
77 and Winsock integrity that were resolved in later Service Packs.</p>
78 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
80 <h2><a name="down" id="down">Downloading Apache for Windows</a></h2>
83 <p>Information on the latest versions of Apache can be found on the
84 web site of the Apache web server at
85 <a href="http://httpd.apache.org/download.cgi">http://httpd.apache.org/download.cgi</a>.
86 There you will find the current release, as well as more recent alpha
87 or beta test versions, and a list of HTTP and FTP mirrors from which
88 you can download the Apache web server. Please use a mirror near to
89 you for a fast and reliable download.</p>
91 <p>For Windows installations you should download the version of
92 Apache for Windows with the <code>.msi</code> extension. This is a
93 single Microsoft Installer file, which contains a ready-to-run
94 version of Apache. There is a separate <code>.zip</code> file,
95 which contains only the source code. You can compile Apache
96 yourself with the Microsoft Visual C++ (Visual Studio) tools.</p>
97 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
99 <h2><a name="inst" id="inst">Installing Apache for Windows</a></h2>
102 <p>You need Microsoft Installer 1.2 or above for the installation
103 to work. On Windows 9x you can update your Microsoft Installer to
104 version 2.0 <a href="http://www.microsoft.com/downloads/release.asp?ReleaseID=32831">here</a>
105 and on Windows NT 4.0 and 2000 the version 2.0 update can be found
106 <a href="http://www.microsoft.com/downloads/release.asp?ReleaseID=32832">here</a>.
107 Windows XP does not need this update.</p>
109 <p>Note that you cannot install two versions of Apache 2.0 on the
110 same computer with the binary installer. You can, however, install
111 a version of the 1.3 series <strong>and</strong> a version of the
112 2.0 series on the same computer without problems. If you need to
113 have two different 2.0 versions on the same computer, you have to
114 <a href="win_compiling.html">compile and install Apache from the
117 <p>Run the Apache <code>.msi</code> file you downloaded above. The
118 installation will ask you for these things:</p>
121 <li><p><strong>Network Domain.</strong> Enter the DNS domain in which
122 your server is or will be registered in. For example, if your
123 server's full DNS name is <code>server.mydomain.net</code>, you would
124 type <code>mydomain.net</code> here.</p></li>
126 <li><p><strong>Server Name.</strong> Your server's full DNS name.
127 From the example above, you would type <code>server.mydomain.net</code>
130 <li><p><strong>Administrator's Email Address.</strong> Enter the
131 server administrator's or webmaster's email address here. This
132 address will be displayed along with error messages to the client
135 <li><p><strong>For whom to install Apache</strong> Select <code>for
136 All Users, on Port 80, as a Service - Recommended</code> if you'd
137 like your new Apache to listen at port 80 for incoming traffic.
138 It will run as a service (that is, Apache will run even if no one
139 is logged in on the server at the moment) Select <code>only for
140 the Current User, on Port 8080, when started Manually</code> if
141 you'd like to install Apache for your personal experimenting or
142 if you already have another WWW server running on port 80.</p></li>
144 <li><p><strong>The installation type.</strong> Select <code>Typical</code>
145 for everything except the source code and libraries for module
146 development. With <code>Custom</code> you can specify what to
147 install. A full install will require about 13 megabytes of free
148 disk space. This does <em>not</em> include the size of your web
151 <li><p><strong>Where to install.</strong> The default path is
152 <code>C:\Program Files\Apache Group</code> under which a directory
153 called <code>Apache2</code> will be created by default.</p></li>
156 <p>During the installation, Apache will configure the files in the
157 <code>conf</code> subdirectory to reflect the chosen installation
158 directory. However, if any of the configuration files in this
159 directory already exist, they will not be overwritten. Instead, the
160 new copy of the corresponding file will be left with the extension
161 <code>.default</code>. So, for example, if <code>conf\httpd.conf</code>
162 already exists, it will be renamed as <code>conf\httpd.conf.default</code>.
163 After the installation you should manually check to see what new
164 settings are in the <code>.default</code> file, and if necessary,
165 update your existing configuration file.</p>
167 <p>Also, if you already have a file called <code>htdocs\index.html</code>,
168 it will not be overwritten (and no <code>index.html.default</code>
169 will be installed either). This means it should be safe to install
170 Apache over an existing installation, although you would have to
171 stop the existing running server before doing the installation, and
172 then start the new one after the installation is finished.</p>
174 <p>After installing Apache, you must edit the configuration files
175 in the <code>conf</code> subdirectory as required. These files
176 will be configured during the installation so that Apache is ready
177 to be run from the directory it was installed into, with the
178 documents server from the subdirectory <code>htdocs</code>. There
179 are lots of other options which you should set before you really
180 start using Apache. However, to get started quickly, the files
181 should work as installed.</p>
182 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
183 <div class="section">
184 <h2><a name="cust" id="cust">Customizing Apache for Windows</a></h2>
187 <p>Apache is configured by the files in the <code>conf</code>
188 subdirectory. These are the same files used to configure the Unix
189 version, but there are a few different directives for Apache on
190 Windows. See the <a href="../mod/directives.html">directive index</a>
191 for all the available directives.</p>
193 <p>The main differences in Apache for Windows are:</p>
195 <li><p>Because Apache for Windows is multithreaded, it does not
196 use a separate process for each request, as Apache does on Unix.
197 Instead there are usually only two Apache processes running: a
198 parent process, and a child which handles the requests. Within
199 the child process each request is handled by a separate thread.
202 <p>The process management directives are also different:</p>
204 <p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code>:
205 Like the Unix directive, this controls how many requests a single
206 child process will serve before exiting. However, unlike on Unix,
207 a single process serves all the requests at once, not just one.
208 If this is set, it is recommended that a very high number is
209 used. The recommended default, <code>MaxRequestsPerChild 0</code>,
210 causes the child process to never exit.</p>
212 <div class="warning"><strong>Warning: The server configuration
213 file is reread when a new child process is started. If you have
214 modified <code>httpd.conf</code>, the new child may not start or
215 you may receive unexpected results.</strong></div>
217 <p><code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>:
218 This directive is new. It tells the server how many threads it
219 should use. This is the maximum number of connections the server
220 can handle at once, so be sure to set this number high enough for
221 your site if you get a lot of hits. The recommended default is
222 <code>ThreadsPerChild 50</code>.</p></li>
224 <li><p>The directives that accept filenames as arguments must use
225 Windows filenames instead of Unix ones. However, because Apache
226 uses Unix-style names internally, you must use forward slashes,
227 not backslashes. Drive letters can be used; if omitted, the drive
228 with the Apache executable will be assumed.</p></li>
230 <li><p>Apache for Windows contains the ability to load modules at
231 runtime, without recompiling the server. If Apache is compiled
232 normally, it will install a number of optional modules in the
233 <code>\Apache2\modules</code> directory. To activate these or
234 other modules, the new <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>
235 directive must be used. For example, to activate the status
236 module, use the following (in addition to the status-activating
237 directives in <code>access.conf</code>):</p>
239 <div class="example"><p><code>
240 LoadModule status_module modules/mod_status.so
243 <p>Information on <a href="../mod/mod_so.html#creating">creating
244 loadable modules</a> is also available.</p></li>
246 <li><p>Apache can also load ISAPI (Internet Server Application
247 Programming Interface) extensions (i.e. internet server
248 applications), such as those used by Microsoft IIS and other
249 Windows servers. <a href="../mod/mod_isapi.html">More information
250 is available</a>. Note that Apache <strong>cannot</strong> load
251 ISAPI Filters.</p></li>
253 <li><p>When running CGI scripts, the method Apache uses to find
254 the interpreter for the script is configurable using the
255 <code class="directive"><a href="../mod/core.html#scriptinterpretersource">ScriptInterpreterSource</a></code>
258 <li><p>Since it is often difficult to manage files with names
259 like <code>.htaccess</code> in Windows, you may find it useful to
260 change the name of this per-directory configuration file using
261 the <code class="directive"><a href="../mod/core.html#accessfilename">AccessFilename</a></code>
264 <li><p>Any errors during Apache startup are logged into the
265 Windows event log when running on Windows NT. This mechanism
266 acts as a backup for those situations where Apache cannot even
267 access the normally used <code>error.log</code> file. You can
268 view the Windows event log by using the Event Viewer application
269 on Windows NT 4.0, and the Event Viewer MMC snap-in on newer
270 versions of Windows.</p>
272 <div class="note"><strong>Note that there is no startup error logging on
273 Windows 9x because no Windows event log exists on those operating
274 systems.</strong></div></li>
277 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
278 <div class="section">
279 <h2><a name="winsvc" id="winsvc">Running Apache as a Service</a></h2>
282 <p>Apache can be run as a service on Windows NT. There is some
283 highly experimental support for similar behavior on Windows 9x.</p>
285 <p>You can install Apache as a service automatically during the
286 installation. If you chose to install for all users, the
287 installation will create an Apache service for you. If you specify
288 to install for yourself only, you can manually register Apache as a
289 service after the installation. You have to be a member of the
290 Administrators group for the service installation to succeed.</p>
292 <p>Apache comes with a utility called the Apache Service Monitor.
293 With it you can see and manage the state of all installed Apache
294 services on any machine on your network. To be able to manage an
295 Apache service with the monitor, you have to first install the
296 service (either automatically via the installation or manually).
299 <p>You can install Apache as a Windows NT service as follows from
300 the command prompt at the Apache <code>bin</code> subdirectory:</p>
302 <div class="example"><p><code>
306 <p>If you need to specify the name of the service you want to
307 install, use the following command. You have to do this if you
308 have several different service installations of Apache on your
311 <div class="example"><p><code>
312 apache -k install -n "MyServiceName"
315 <p>If you need to have specifically named configuration files for
316 different services, you must use this:</p>
318 <div class="example"><p><code>
319 apache -k install -n "MyServiceName" -f "c:\files\my.conf"
322 <p>If you use the first command without any special parameters except
323 <code>-k install</code>, the service will be called <code>Apache2</code>
324 and the configuration will be assumed to be <code>conf\httpd.conf</code>.
327 <p>Removing an Apache service is easy. Just use:</p>
329 <div class="example"><p><code>
333 <p>The specific Apache service to be uninstalled can be specified by using:</p>
335 <div class="example"><p><code>
336 apache -k uninstall -n "MyServiceName"
339 <p>Normal starting, restarting and shutting down of an Apache
340 service is usually done via the Apache Service Monitor, by using
341 commands like <code>NET START Apache2</code> and <code>NET STOP
342 Apache2</code> or via normal Windows service management. Before
343 starting Apache as a service by any means, you should test the
344 service's configuration file by using:</p>
346 <div class="example"><p><code>
347 apache -n "MyServiceName" -t
350 <p>You can control an Apache service by its command line switches,
351 too. To start an installed Apache service you'll use this:</p>
353 <div class="example"><p><code>
357 <p>To stop an Apache service via the command line switches, use
360 <div class="example"><p><code>
366 <div class="example"><p><code>
370 <p>You can also restart a running service and force it to reread
371 its configuration file by using:</p>
373 <div class="example"><p><code>
377 <p>By default, all Apache services are registered to run as the
378 system user (the <code>LocalSystem</code> account). The
379 <code>LocalSystem</code> account has no privileges to your network
380 via any Windows-secured mechanism, including the file system, named
381 pipes, DCOM, or secure RPC. It has, however, wide privileges locally.
384 <div class="warning"><strong>Never grant any network privileges to
385 the <code>LocalSystem</code> account! If you need Apache to be able
386 to access network resources, create a separate account for Apache as
387 noted below.</strong></div>
389 <p>You may want to create a separate account for running Apache
390 service(s). Especially, if you have to access network resources
391 via Apache, this is strongly recommended.</p>
394 <li>Create a normal domain user account, and be sure to
395 memorize its password.</li>
397 <li>Grant the newly-created user a privilege of <code>Log on
398 as a service</code> and <code>Act as part of the operating
399 system</code>. On Windows NT 4.0 these privileges are granted via
400 User Manager for Domains, but on Windows 2000 and XP you probably
401 want to use Group Policy for propagating these settings. You can
402 also manually set these via the Local Security Policy MMC snap-in.
405 <li>Confirm that the created account is a member of the Users
408 <li>Grant the account read and execute (RX) rights to all document
409 and script folders (<code>htdocs</code> and <code>cgi-bin</code>
412 <li>Grant the account change (RWXD) rights to the
413 Apache <code>logs</code> directory.</li>
415 <li>Grant the account read and execute (RX) rights to the
416 <code>Apache.exe</code> binary executable.</li>
419 <div class="note">It is usually a good practice to grant the user the Apache
420 service runs as read and execute (RX) access to the whole Apache2
421 directory, except the <code>logs</code> subdirectory, where the
422 user has to have at least change (RWXD) rights.</div>
424 <p>If you allow the account to log in as a user and as a service,
425 then you can log on with that account and test that the account has the
426 privileges to execute the scripts, read the web pages, and that
427 you can start Apache in a console window. If this works, and you
428 have followed the steps above, Apache should execute as a service
429 with no problems.</p>
431 <div class="note"><strong>Error code 2186</strong> is a good indication that
432 you need to review the "Log On As" configuration for the service,
433 since Apache cannot access a required network resource. Also, pay
434 close attention to the privileges of the user Apache is
435 configured to run as.</div>
437 <p>When starting Apache as a service you may encounter an error
438 message from the Windows Service Control Manager. For example,
439 if you try to start Apache by using the Services applet in the
440 Windows Control Panel, you may get the following message:</p>
442 <div class="example"><p><code>
443 Could not start the Apache2 service on \\COMPUTER <br />
444 Error 1067; The process terminated unexpectedly.
447 <p>You will get this generic error if there is any problem with
448 starting the Apache service. In order to see what is really causing
449 the problem you should follow the instructions for Running Apache
450 for Windows from the Command Prompt.</p>
452 <p>There is some support for Apache on Windows 9x to behave in a
453 similar manner as a service on Windows NT. It is <strong>highly
454 experimental</strong>. It is not of production-class reliability,
455 and its future is not guaranteed. It can be mostly regarded as
456 a risky thing to play with - proceed with caution!</p>
458 <p>There are some differences between the two kinds of services
459 you should be aware of:</p>
462 <li><p>Apache will attempt to start and if successful it will run
463 in the background. If you run the command</p>
465 <div class="example"><p><code>
466 apache -n "MyServiceName" -k start
469 <p>via a shortcut on your desktop, for example, then if the
470 service starts successfully, a console window will flash up but
471 it immediately disappears. If Apache detects any errors on startup
472 such as incorrect entries in the httpd.conf configuration file,
473 the console window will remain visible. This will display an error
474 message which will be useful in tracking down the cause of the
477 <li><p>Windows 9x does not support <code>NET START</code> or
478 <code>NET STOP</code> commands. You must control the Apache
479 service on the command prompt via the <code>-k</code> switches.
482 <li><p>Apache and Windows 9x offer no support for running Apache
483 as a specific user with network privileges. In fact, Windows 9x
484 offers no security on the local machine, either. This is the
485 simple reason because of which the Apache Software Foundation
486 never endorses use of a Windows 9x -based system as a public
487 Apache server. The primitive support for Windows 9x exists only
488 to assist the user in developing web content and learning the
489 Apache server, and perhaps as an intranet server on a secured,
490 private network.</p></li>
494 <p>Once you have confirmed that Apache runs correctly as a
495 console application you can install, control and uninstall the
496 pseudo-service with the same commands as on Windows NT. You can
497 also use the Apache Service Monitor to manage Windows 9x
500 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
501 <div class="section">
502 <h2><a name="wincons" id="wincons">Running Apache as a Console Application</a></h2>
505 <p>Running Apache as a service is usually the recommended way to
506 use it, but it is sometimes easier to work from the command line
507 (on Windows 9x running Apache from the command line is the
508 recommended way due to the lack of reliable service support.)</p>
510 <p>To run Apache from the command line as a console application,
511 use the following command:</p>
513 <div class="example"><p><code>
517 <p>Apache will execute, and will remain running until it is stopped
518 by pressing Control-C.</p>
520 <p>You can also run Apache via the shortcut Start Apache in Console
521 placed to <code>Start Menu --> Programs --> Apache HTTP Server
522 2.0.xx --> Control Apache Server</code> during the installation.
523 This will open a console window and start Apache inside it. If you
524 don't have Apache installed as a service, the window will remain
525 visible until you stop Apache by pressing Control-C in the console
526 window where Apache is running in. The server will exit in a few
527 seconds. However, if you do have Apache installed as a service, the
528 shortcut starts the service. If the Apache service is running
529 already, the shortcut doesn't do anything.</p>
531 <p>You can tell a running Apache to stop by opening another console
532 window and entering:</p>
534 <div class="example"><p><code>
538 <p>This should be preferred over pressing Control-C because this
539 lets Apache end any current operations and clean up gracefully.</p>
541 <p>You can also tell Apache to restart. This forces it to reread
542 the configuration file. Any operations in progress are allowed to
543 complete without interruption. To restart Apache, use:</p>
545 <div class="example"><p><code>
549 <div class="note">Note for people familiar with the Unix version of Apache:
550 these commands provide a Windows equivalent to <code>kill -TERM
551 <em>pid</em></code> and <code>kill -USR1 <em>pid</em></code>. The
552 command line option used, <code>-k</code>, was chosen as a reminder
553 of the <code>kill</code> command used on Unix.</div>
555 <p>If the Apache console window closes immediately or unexpectedly
556 after startup, open the Command Prompt from the Start Menu -->
557 Programs. Change to the folder to which you installed Apache, type
558 the command <code>apache</code>, and read the error message. Then
559 change to the logs folder, and review the <code>error.log</code>
560 file for configuration mistakes. If you accepted the defaults when
561 you installed Apache, the commands would be:</p>
563 <div class="example"><p><code>
565 cd "\Program Files\Apache Group\Apache2\bin" <br />
569 <p>Then wait for Apache to stop, or press Control-C. Then enter the
572 <div class="example"><p><code>
577 <p>When working with Apache it is important to know how it will
578 find the configuration file. You can specify a configuration file
579 on the command line in two ways:</p>
582 <li><p><code>-f</code> specifies an absolute or relative path to
583 a particular configuration file:</p>
585 <div class="example"><p><code>
586 apache -f "c:\my server files\anotherconfig.conf"
591 <div class="example"><p><code>
592 apache -f files\anotherconfig.conf
593 </code></p></div></li>
595 <li><p><code>-n</code> specifies the installed Apache service
596 whose configuration file is to be used:</p>
598 <div class="example"><p><code>
599 apache -n "MyServiceName"
604 <p>In both of these cases, the proper
605 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> should be set in
606 the configuration file.</p>
608 <p>If you don't specify a configuration file with <code>-f</code>
609 or <code>-n</code>, Apache will use the file name compiled into the
610 server, such as <code>conf\httpd.conf</code>. This built-in path
611 is relative to the installation directory. You can verify the compiled
612 file name from a value labelled as <code>SERVER_CONFIG_FILE</code> when
613 invoking Apache with the <code>-V</code> switch, like this:</p>
615 <div class="example"><p><code>
619 <p>Apache will then try to determine its <code class="directive"><a href="../mod/core.html# serverroot">
620 ServerRoot</a></code> by trying the following, in this order:</p>
623 <li>A <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive
624 via the <code>-C</code> command line switch.</li>
626 <li>The <code>-d</code> switch on the command line.</li>
628 <li>Current working directory.</li>
630 <li>A registry entry which was created if you did a binary
633 <li>The server root compiled into the server. This is <code>
634 /apache</code> by default, you can verify it by using <code>
635 apache -V</code> and looking for a value labelled as
636 <code>HTTPD_ROOT</code>.</li>
639 <p>During the installation, a version-specific registry key is
640 created in the Windows registry. The location of this key depends
641 on the type of the installation. If you chose to install Apache
642 for all users, the key is located under the
643 <code>HKEY_LOCAL_MACHINE</code> hive, like this (the version
644 numbers will of course vary between different versions of Apache:
647 <div class="example"><p><code>
648 HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache\2.0.43
651 <p>Correspondingly, if you chose to install Apache for the current
652 user only, the key is located under the <code>HKEY_CURRENT_USER</code>
653 hive, the contents of which are dependent of the user currently
656 <div class="example"><p><code>
657 HKEY_CURRENT_USER\SOFTWARE\Apache Group\Apache\2.0.43
660 <p>This key is compiled into the server and can enable you to test
661 new versions without affecting the current version. Of course, you
662 must take care not to install the new version in the same
663 directory as another version.</p>
665 <p>If you did not do a binary install, Apache will in some
666 scenarios complain about the missing registry key. This warning can
667 be ignored if the server was otherwise able to find its
668 configuration file.</p>
670 <p>The value of this key is the
671 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directory which
672 contains the <code>conf</code> subdirectory. When Apache starts it
673 reads the <code>httpd.conf</code> file from that directory. If
674 this file contains a <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>
675 directive which contains a different directory from the one
676 obtained from the registry key above, Apache will forget the
677 registry key and use the directory from the configuration file. If
678 you copy the Apache directory or configuration files to a new
679 location it is vital that you update the
680 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive in the
681 <code>httpd.conf</code> file to reflect the new location.</p>
683 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
684 <div class="section">
685 <h2><a name="test" id="test">Testing the Installation</a></h2>
688 <p>After starting Apache (either in a console window or as a
689 service) it will be listening on port 80 (unless you changed the
690 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the
691 configuration files or installed Apache only for the current user).
692 To connect to the server and access the default page, launch a
693 browser and enter this URL:</p>
695 <div class="example"><p><code>
699 <p>Apache should respond with a welcome page and a link to the
700 Apache manual. If nothing happens or you get an error, look in the
701 <code>error.log</code> file in the <code>logs</code> subdirectory.
702 If your host is not connected to the net, or if you have serious
703 problems with your DNS (Domain Name Service) configuration, you
704 may have to use this URL:</p>
706 <div class="example"><p><code>
710 <p>Once your basic installation is working, you should configure it
711 properly by editing the files in the <code>conf</code> subdirectory.
712 Again, if you change the configuration of the Windows NT service
713 for Apache, first attempt to start it from the command line to
714 make sure that the service starts with no errors.</p>
716 <p>Because Apache <strong>cannot</strong> share the same port with
717 another TCP/IP application, you may need to stop, uninstall or reconfigure
718 certain other services before running Apache. These conflicting
719 services include other WWW servers and some firewall implementations.
723 <div class="bottomlang">
724 <p><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> |
725 <a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
726 </div><div id="footer">
727 <p class="apache">Copyright 1999-2004 The Apache Software Foundation.<br />Licensed under the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache License, Version 2.0</a>.</p>
728 <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>