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 HTTP Server on 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.3</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/">Documentation</a> > <a href="../">Version 2.3</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Using Apache HTTP Server on 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>
25 <p>This document explains how to install, configure and run
26 Apache 2.3 under Microsoft Windows. If you have questions after
27 reviewing the documentation (and any event and error logs), you
28 should consult the peer-supported
29 <a href="http://httpd.apache.org/userslist.html">users' mailing
32 <p>This document assumes that you are installing a binary
33 distribution of Apache. If you want to compile Apache yourself
34 (possibly to help with development or tracking down bugs),
35 see <a href="win_compiling.html">Compiling Apache for Microsoft
38 <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Operating System Requirements</a></li>
39 <li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for Windows</a></li>
40 <li><img alt="" src="../images/down.gif" /> <a href="#inst">Installing Apache for Windows</a></li>
41 <li><img alt="" src="../images/down.gif" /> <a href="#cust">Customizing Apache for Windows</a></li>
42 <li><img alt="" src="../images/down.gif" /> <a href="#winsvc">Running Apache as a Service</a></li>
43 <li><img alt="" src="../images/down.gif" /> <a href="#wincons">Running Apache as a Console Application</a></li>
44 <li><img alt="" src="../images/down.gif" /> <a href="#test">Testing the Installation</a></li>
46 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
48 <h2><a name="req" id="req">Operating System Requirements</a></h2>
51 <p>The primary Windows platform for running Apache 2.3 is Windows
52 2000 or later. The binary installer only works with the x86 family
53 of processors, such as Intel and AMD processors. Always obtain and
54 install the current service pack to avoid operating system bugs.</p>
56 <div class="note">Apache HTTP Server versions later than 2.2 will not run on any
57 operating system earlier than Windows 2000.</div>
58 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
60 <h2><a name="down" id="down">Downloading Apache for Windows</a></h2>
63 <p>Information on the latest versions of Apache can be found on the
64 web site of the Apache web server at
65 <a href="http://httpd.apache.org/download.cgi">http://httpd.apache.org/download.cgi</a>.
66 There you will find the current release, as well as more recent alpha
67 or beta test versions, and a list of HTTP and FTP mirrors from which
68 you can download the Apache web server. Please use a mirror near to
69 you for a fast and reliable download.</p>
71 <p>For Windows installations you should download the version of
72 Apache for Windows with the <code>.msi</code> extension. This is a
73 single Microsoft Installer file, which contains a ready-to-run
74 build of Apache. There is a separate <code>.zip</code> file,
75 which contains only the source code, see the summary above.</p>
76 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
78 <h2><a name="inst" id="inst">Installing Apache for Windows</a></h2>
81 <p>You need Microsoft Installer 2.0 or above for the installation
82 to work. For Windows NT 4.0 and 2000 refer to Microsoft's article
83 <a href="http://support.microsoft.com/kb/292539/">KB 292539</a>.
84 Windows XP and later do not require this update.</p>
86 <p>Note that you cannot install two versions of Apache 2.3 on the
87 same computer with the binary installer. You can, however, install
88 a version of the 1.3 series <strong>and</strong> a version of the
89 2.3 series on the same computer without problems. If you need to
90 have two different 2.3 versions on the same computer, you have to
91 <a href="win_compiling.html">compile and install Apache from the
94 <p>Run the Apache <code>.msi</code> file you downloaded above. The
95 installation will ask you for these things:</p>
98 <li><p><strong>Network Domain.</strong> Enter the DNS domain in which
99 your server is or will be registered in. For example, if your
100 server's full DNS name is <code>server.mydomain.net</code>, you would
101 type <code>mydomain.net</code> here.</p></li>
103 <li><p><strong>Server Name.</strong> Your server's full DNS name.
104 From the example above, you would type <code>server.mydomain.net</code>
107 <li><p><strong>Administrator's Email Address.</strong> Enter the
108 server administrator's or webmaster's email address here. This
109 address will be displayed along with error messages to the client
112 <li><p><strong>For whom to install Apache</strong> Select <code>for
113 All Users, on Port 80, as a Service - Recommended</code> if you'd
114 like your new Apache to listen at port 80 for incoming traffic.
115 It will run as a service (that is, Apache will run even if no one
116 is logged in on the server at the moment) Select <code>only for
117 the Current User, on Port 8080, when started Manually</code> if
118 you'd like to install Apache for your personal experimenting or
119 if you already have another WWW server running on port 80.</p></li>
121 <li><p><strong>The installation type.</strong> Select <code>Typical</code>
122 for everything except the source code and libraries for module
123 development. With <code>Custom</code> you can specify what to
124 install. A full install will require about 13 megabytes of free
125 disk space. This does <em>not</em> include the size of your web
128 <li><p><strong>Where to install.</strong> The default path is
129 <code>C:\Program Files\Apache Software Foundation</code>
130 under which a directory called
131 <code>Apache2.3</code> will be created by default.</p></li>
134 <p>During the installation, Apache will configure the files in the
135 <code>conf</code> subdirectory to reflect the chosen installation
136 directory. However, if any of the configuration files in this
137 directory already exist, they will not be overwritten. Instead, the
138 new copy of the corresponding file will be left with the extension
139 <code>.default</code>. So, for example, if <code>conf\httpd.conf</code>
140 already exists, it will be renamed as <code>conf\httpd.conf.default</code>.
141 After the installation you should manually check to see what new
142 settings are in the <code>.default</code> file, and if necessary,
143 update your existing configuration file.</p>
145 <p>Also, if you already have a file called <code>htdocs\index.html</code>,
146 it will not be overwritten (and no <code>index.html.default</code>
147 will be installed either). This means it should be safe to install
148 Apache over an existing installation, although you would have to
149 stop the existing running server before doing the installation, and
150 then start the new one after the installation is finished.</p>
152 <p>After installing Apache, you must edit the configuration files
153 in the <code>conf</code> subdirectory as required. These files
154 will be configured during the installation so that Apache is ready
155 to be run from the directory it was installed into, with the
156 documents server from the subdirectory <code>htdocs</code>. There
157 are lots of other options which you should set before you really
158 start using Apache. However, to get started quickly, the files
159 should work as installed.</p>
160 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
161 <div class="section">
162 <h2><a name="cust" id="cust">Customizing Apache for Windows</a></h2>
165 <p>Apache is configured by the files in the <code>conf</code>
166 subdirectory. These are the same files used to configure the Unix
167 version, but there are a few different directives for Apache on
168 Windows. See the <a href="../mod/directives.html">directive index</a>
169 for all the available directives.</p>
171 <p>The main differences in Apache for Windows are:</p>
173 <li><p>Because Apache for Windows is multithreaded, it does not
174 use a separate process for each request, as Apache can on Unix.
175 Instead there are usually only two Apache processes running: a
176 parent process, and a child which handles the requests. Within
177 the child process each request is handled by a separate thread.
180 <p>The process management directives are also different:</p>
182 <p><code class="directive"><a href="../mod/mpm_common.html#maxrequestsperchild">MaxRequestsPerChild</a></code>:
183 Like the Unix directive, this controls how many requests (actually,
184 connections) which a single child process will serve before exiting.
185 However, unlike on Unix, a replacement process is not instantly
186 available. Use the default <code>MaxRequestsPerChild 0</code>,
187 unless instructed to change the behavior to overcome a memory leak
188 in third party modules or in-process applications.</p>
190 <div class="warning"><strong>Warning: The server configuration
191 file is reread when a new child process is started. If you have
192 modified <code>httpd.conf</code>, the new child may not start or
193 you may receive unexpected results.</strong></div>
195 <p><code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>:
196 This directive is new. It tells the server how many threads it
197 should use. This is the maximum number of connections the server
198 can handle at once, so be sure to set this number high enough for
199 your site if you get a lot of hits. The recommended default is
200 <code>ThreadsPerChild 150</code>, but this mut be adjusted to
201 reflect the greatest anticipated number of simultanious
202 connections to accept.</p></li>
204 <li><p>The directives that accept filenames as arguments must use
205 Windows filenames instead of Unix ones. However, because Apache
206 may interpret backslashes as an "escape character" sequence, you
207 should consistently use forward slashes in path names, not
208 backslashes. Drive letters can be used; if omitted, the drive
209 of the SystemRoot direcive (or -d command line option) becomes
210 the default.</p></li>
212 <li><p>While filenames are generally case-insensitive on
213 Windows, URLs are still treated internally as case-sensitive
214 before they are mapped to the filesystem. For example, the
215 <code class="directive"><a href="../mod/core.html#location"><Location></a></code>,
216 <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>, and <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> directives all use
217 case-sensitive arguments. For this reason, it is particularly
218 important to use the <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> directive when attempting
219 to limit access to content in the filesystem, since this
220 directive applies to any content in a directory, regardless of
221 how it is accessed. If you wish to assure that only lowercase
222 is used in URLs, you can use something like:</p>
224 <div class="example"><p><code>
225 RewriteEngine On<br />
226 RewriteMap lowercase int:tolower<br />
227 RewriteCond %{REQUEST_URI} [A-Z]<br />
228 RewriteRule (.*) ${lowercase:$1} [R,L]
229 </code></p></div></li>
231 <li><p>When running, Apache needs write access only to the logs
232 directory and any configured cache directory tree. Due to the
233 issue of case insensitive and short 8.3 format names, Apache must
234 validate all path names given. This means that each directory
235 which Apache evaluates, from the drive root up to the directory
236 leaf, must have read, list and traverse directory permissions.
237 If Apache2.3 is installed at C:\Program Files, then the root
238 directory, Program Files and Apache2.3 must all be visible
241 <li><p>Apache for Windows contains the ability to load modules at
242 runtime, without recompiling the server. If Apache is compiled
243 normally, it will install a number of optional modules in the
244 <code>\Apache2.3\modules</code> directory. To activate these or
245 other modules, the new <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>
246 directive must be used. For example, to activate the status
247 module, use the following (in addition to the status-activating
248 directives in <code>access.conf</code>):</p>
250 <div class="example"><p><code>
251 LoadModule status_module modules/mod_status.so
254 <p>Information on <a href="../mod/mod_so.html#creating">creating
255 loadable modules</a> is also available.</p></li>
257 <li><p>Apache can also load ISAPI (Internet Server Application
258 Programming Interface) extensions such as those used by Microsoft
259 IIS and other Windows servers. <a href="../mod/mod_isapi.html">More
260 information is available</a>. Note that Apache <strong>cannot</strong>
261 load ISAPI Filters, and ISAPI Handlers with some Microsoft feature
262 extensions will not work.</p></li>
264 <li><p>When running CGI scripts, the method Apache uses to find
265 the interpreter for the script is configurable using the
266 <code class="directive"><a href="../mod/core.html#scriptinterpretersource">ScriptInterpreterSource</a></code>
269 <li><p>Since it is often difficult to manage files with names
270 like <code>.htaccess</code> in Windows, you may find it useful to
271 change the name of this per-directory configuration file using
272 the <code class="directive"><a href="../mod/core.html#accessfilename">AccessFilename</a></code>
275 <li><p>Any errors during Apache startup are logged into the
276 Windows event log when running on Windows NT. This mechanism
277 acts as a backup for those situations where Apache is not yet
278 prepared to use the <code>error.log</code> file. You can
279 review the Windows Applicat Event Log by using the Event Viewer,
280 e.g. Start - Settings - Control Panel - Administrative Tools
281 - Event Viewer.</p></li>
284 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
285 <div class="section">
286 <h2><a name="winsvc" id="winsvc">Running Apache as a Service</a></h2>
289 <p>You can install Apache as a service automatically during the
290 installation. If you chose to install for all users, the
291 installation will create an Apache service for you. If you specify
292 to install for yourself only, you can manually register Apache as a
293 service after the installation. You have to be a member of the
294 Administrators group for the service installation to succeed.</p>
296 <p>Apache comes with a utility called the Apache Service Monitor.
297 With it you can see and manage the state of all installed Apache
298 services on any machine on your network. To be able to manage an
299 Apache service with the monitor, you have to first install the
300 service (either automatically via the installation or manually).
303 <p>You can install Apache as a Windows NT service as follows from
304 the command prompt at the Apache <code>bin</code> subdirectory:</p>
306 <div class="example"><p><code>
310 <p>If you need to specify the name of the service you want to
311 install, use the following command. You have to do this if you
312 have several different service installations of Apache on your
315 <div class="example"><p><code>
316 httpd.exe -k install -n "MyServiceName"
319 <p>If you need to have specifically named configuration files for
320 different services, you must use this:</p>
322 <div class="example"><p><code>
323 httpd.exe -k install -n "MyServiceName" -f "c:\files\my.conf"
326 <p>If you use the first command without any special parameters except
327 <code>-k install</code>, the service will be called <code>Apache2.3</code>
328 and the configuration will be assumed to be <code>conf\httpd.conf</code>.
331 <p>Removing an Apache service is easy. Just use:</p>
333 <div class="example"><p><code>
334 httpd.exe -k uninstall
337 <p>The specific Apache service to be uninstalled can be specified by using:</p>
339 <div class="example"><p><code>
340 httpd.exe -k uninstall -n "MyServiceName"
343 <p>Normal starting, restarting and shutting down of an Apache
344 service is usually done via the Apache Service Monitor, by using
345 commands like <code>NET START Apache2.3</code> and <code>NET STOP
346 Apache2.3</code> or via normal Windows service management. Before
347 starting Apache as a service by any means, you should test the
348 service's configuration file by using:</p>
350 <div class="example"><p><code>
351 httpd.exe -n "MyServiceName" -t
354 <p>You can control an Apache service by its command line switches,
355 too. To start an installed Apache service you'll use this:</p>
357 <div class="example"><p><code>
361 <p>To stop an Apache service via the command line switches, use
364 <div class="example"><p><code>
370 <div class="example"><p><code>
371 httpd.exe -k shutdown
374 <p>You can also restart a running service and force it to reread
375 its configuration file by using:</p>
377 <div class="example"><p><code>
381 <p>By default, all Apache services are registered to run as the
382 system user (the <code>LocalSystem</code> account). The
383 <code>LocalSystem</code> account has no privileges to your network
384 via any Windows-secured mechanism, including the file system, named
385 pipes, DCOM, or secure RPC. It has, however, wide privileges locally.
388 <div class="warning"><strong>Never grant any network privileges to
389 the <code>LocalSystem</code> account! If you need Apache to be able
390 to access network resources, create a separate account for Apache as
391 noted below.</strong></div>
393 <p>It is recommended that users create a separate account for running
394 Apache service(s). If you have to access network resources via Apache,
395 this is required.</p>
398 <li>Create a normal domain user account, and be sure to
399 memorize its password.</li>
401 <li>Grant the newly-created user a privilege of <code>Log on
402 as a service</code> and <code>Act as part of the operating
403 system</code>. On Windows NT 4.0 these privileges are granted via
404 User Manager for Domains, but on Windows 2000 and XP you probably
405 want to use Group Policy for propagating these settings. You can
406 also manually set these via the Local Security Policy MMC snap-in.
409 <li>Confirm that the created account is a member of the Users
412 <li>Grant the account read and execute (RX) rights to all document
413 and script folders (<code>htdocs</code> and <code>cgi-bin</code>
416 <li>Grant the account change (RWXD) rights to the
417 Apache <code>logs</code> directory.</li>
419 <li>Grant the account read and execute (RX) rights to the
420 <code>httpd.exe</code> binary executable.</li>
423 <div class="note">It is usually a good practice to grant the user the Apache
424 service runs as read and execute (RX) access to the whole Apache2.3
425 directory, except the <code>logs</code> subdirectory, where the
426 user has to have at least change (RWXD) rights.</div>
428 <p>If you allow the account to log in as a user and as a service,
429 then you can log on with that account and test that the account has
430 the privileges to execute the scripts, read the web pages, and that
431 you can start Apache in a console window. If this works, and you
432 have followed the steps above, Apache should execute as a service
433 with no problems.</p>
435 <div class="note"><strong>Error code 2186</strong> is a good indication that
436 you need to review the "Log On As" configuration for the service,
437 since Apache cannot access a required network resource. Also, pay
438 close attention to the privileges of the user Apache is
439 configured to run as.</div>
441 <p>When starting Apache as a service you may encounter an error
442 message from the Windows Service Control Manager. For example,
443 if you try to start Apache by using the Services applet in the
444 Windows Control Panel, you may get the following message:</p>
446 <div class="example"><p><code>
447 Could not start the Apache2.3 service on \\COMPUTER <br />
448 Error 1067; The process terminated unexpectedly.
451 <p>You will get this generic error if there is any problem with
452 starting the Apache service. In order to see what is really causing
453 the problem you should follow the instructions for Running Apache
454 for Windows from the Command Prompt.</p>
456 <p>If you are having problems with the service, it is suggested
457 you follow the instructions below to try starting httpd.exe from
458 a console window, and work out the errors before struggling to
459 start it as a service again.</p>
460 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
461 <div class="section">
462 <h2><a name="wincons" id="wincons">Running Apache as a Console Application</a></h2>
465 <p>Running Apache as a service is usually the recommended way to
466 use it, but it is sometimes easier to work from the command line,
467 especially during initial configuration and testing.</p>
469 <p>To run Apache from the command line as a console application,
470 use the following command:</p>
472 <div class="example"><p><code>
476 <p>Apache will execute, and will remain running until it is stopped
477 by pressing Control-C.</p>
479 <p>You can also run Apache via the shortcut Start Apache in Console
480 placed to <code>Start Menu --> Programs --> Apache HTTP Server
481 2.3.xx --> Control Apache Server</code> during the installation.
482 This will open a console window and start Apache inside it. If you
483 don't have Apache installed as a service, the window will remain
484 visible until you stop Apache by pressing Control-C in the console
485 window where Apache is running in. The server will exit in a few
486 seconds. However, if you do have Apache installed as a service, the
487 shortcut starts the service. If the Apache service is running
488 already, the shortcut doesn't do anything.</p>
490 <p>You can tell a running Apache to stop by opening another console
491 window and entering:</p>
493 <div class="example"><p><code>
494 httpd.exe -k shutdown
497 <p>This should be preferred over pressing Control-C because this
498 lets Apache end any current operations and clean up gracefully.</p>
500 <p>You can also tell Apache to restart. This forces it to reread
501 the configuration file. Any operations in progress are allowed to
502 complete without interruption. To restart Apache, either press
503 Control-Break in the console window you used for starting Apache,
506 <div class="example"><p><code>
510 <p>in any other console window.</p>
512 <div class="note">Note for people familiar with the Unix version of Apache:
513 these commands provide a Windows equivalent to <code>kill -TERM
514 <em>pid</em></code> and <code>kill -USR1 <em>pid</em></code>. The
515 command line option used, <code>-k</code>, was chosen as a reminder
516 of the <code>kill</code> command used on Unix.</div>
518 <p>If the Apache console window closes immediately or unexpectedly
519 after startup, open the Command Prompt from the Start Menu -->
520 Programs. Change to the folder to which you installed Apache, type
521 the command <code>httpd.exe</code>, and read the error message. Then
522 change to the logs folder, and review the <code>error.log</code>
523 file for configuration mistakes. If you accepted the defaults when
524 you installed Apache, the commands would be:</p>
526 <div class="example"><p><code>
528 cd "\Program Files\Apache Software Foundation\Apache2.3\bin" <br />
532 <p>Then wait for Apache to stop, or press Control-C. Then enter the
535 <div class="example"><p><code>
540 <p>When working with Apache it is important to know how it will
541 find the configuration file. You can specify a configuration file
542 on the command line in two ways:</p>
545 <li><p><code>-f</code> specifies an absolute or relative path to
546 a particular configuration file:</p>
548 <div class="example"><p><code>
549 httpd.exe -f "c:\my server files\anotherconfig.conf"
554 <div class="example"><p><code>
555 httpd.exe -f files\anotherconfig.conf
556 </code></p></div></li>
558 <li><p><code>-n</code> specifies the installed Apache service
559 whose configuration file is to be used:</p>
561 <div class="example"><p><code>
562 httpd.exe -n "MyServiceName"
567 <p>In both of these cases, the proper
568 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> should be set in
569 the configuration file.</p>
571 <p>If you don't specify a configuration file with <code>-f</code>
572 or <code>-n</code>, Apache will use the file name compiled into the
573 server, such as <code>conf\httpd.conf</code>. This built-in path
574 is relative to the installation directory. You can verify the compiled
575 file name from a value labelled as <code>SERVER_CONFIG_FILE</code> when
576 invoking Apache with the <code>-V</code> switch, like this:</p>
578 <div class="example"><p><code>
582 <p>Apache will then try to determine its <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> by trying the following, in this order:</p>
585 <li>A <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive
586 via the <code>-C</code> command line switch.</li>
588 <li>The <code>-d</code> switch on the command line.</li>
590 <li>Current working directory.</li>
592 <li>A registry entry which was created if you did a binary
595 <li>The server root compiled into the server. This is <code>
596 /apache</code> by default, you can verify it by using <code>
597 httpd.exe -V</code> and looking for a value labelled as
598 <code>HTTPD_ROOT</code>.</li>
601 <p>During the installation, a version-specific registry key is
602 created in the Windows registry. The location of this key depends
603 on the type of the installation. If you chose to install Apache
604 for all users, the key is located under the
605 <code>HKEY_LOCAL_MACHINE</code> hive, like this (the version
606 numbers will of course vary between different versions of Apache:
609 <div class="example"><p><code>
610 HKEY_LOCAL_MACHINE\SOFTWARE\Apache Software Foundation\Apache\2.2.2
613 <p>Correspondingly, if you chose to install Apache for the current
614 user only, the key is located under the <code>HKEY_CURRENT_USER</code>
615 hive, the contents of which are dependent of the user currently
618 <div class="example"><p><code>
619 HKEY_CURRENT_USER\SOFTWARE\Apache Software Foundation\Apache\2.2.2
622 <p>This key is compiled into the server and can enable you to test
623 new versions without affecting the current version. Of course, you
624 must take care not to install the new version in the same
625 directory as another version.</p>
627 <p>If you did not do a binary install, Apache will in some
628 scenarios complain about the missing registry key. This warning can
629 be ignored if the server was otherwise able to find its
630 configuration file.</p>
632 <p>The value of this key is the
633 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directory which
634 contains the <code>conf</code> subdirectory. When Apache starts it
635 reads the <code>httpd.conf</code> file from that directory. If
636 this file contains a <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>
637 directive which contains a different directory from the one
638 obtained from the registry key above, Apache will forget the
639 registry key and use the directory from the configuration file. If
640 you copy the Apache directory or configuration files to a new
641 location it is vital that you update the
642 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive in the
643 <code>httpd.conf</code> file to reflect the new location.</p>
644 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
645 <div class="section">
646 <h2><a name="test" id="test">Testing the Installation</a></h2>
649 <p>After starting Apache (either in a console window or as a
650 service) it will be listening on port 80 (unless you changed the
651 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the
652 configuration files or installed Apache only for the current user).
653 To connect to the server and access the default page, launch a
654 browser and enter this URL:</p>
656 <div class="example"><p><code>
660 <p>Apache should respond with a welcome page and you should see
661 "It Works!". If nothing happens or you get an error, look in the
662 <code>error.log</code> file in the <code>logs</code> subdirectory.
663 If your host is not connected to the net, or if you have serious
664 problems with your DNS (Domain Name Service) configuration, you
665 may have to use this URL:</p>
667 <div class="example"><p><code>
671 <p>If you happen to be running Apache on an alternate port, you
672 need to explicitly put that in the URL:</p>
674 <div class="example"><p><code>
675 http://127.0.0.1:8080/
678 <p>Once your basic installation is working, you should configure it
679 properly by editing the files in the <code>conf</code> subdirectory.
680 Again, if you change the configuration of the Windows NT service
681 for Apache, first attempt to start it from the command line to
682 make sure that the service starts with no errors.</p>
684 <p>Because Apache <strong>cannot</strong> share the same port with
685 another TCP/IP application, you may need to stop, uninstall or reconfigure
686 certain other services before running Apache. These conflicting
687 services include other WWW servers, some firewall implementations,
688 and even some client applications (such as Skype) which will use port
689 80 to attempt to bypass firewall issues.</p>
691 <div class="bottomlang">
692 <p><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> |
693 <a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
694 </div><div id="footer">
695 <p class="apache">Copyright 2009 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>
696 <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>