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" /><link rel="stylesheet" type="text/css" href="../style/css/prettify.css" />
12 <script src="../style/scripts/prettify.js" type="text/javascript">
15 <link href="../images/favicon.ico" rel="shortcut icon" /></head>
16 <body id="manual-page"><div id="page-header">
17 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p>
18 <p class="apache">Apache HTTP Server Version 2.5</p>
19 <img alt="" src="../images/feather.gif" /></div>
20 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
22 <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.5</a> > <a href="./">Platform Specific Notes</a></div><div id="page-content"><div id="preamble"><h1>Using Apache HTTP Server on Microsoft Windows</h1>
24 <p><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> |
25 <a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
28 <p>This document explains how to install, configure and run
29 Apache 2.5 under Microsoft Windows. If you have questions after
30 reviewing the documentation (and any event and error logs), you
31 should consult the peer-supported
32 <a href="http://httpd.apache.org/userslist.html">users' mailing
35 <p>This document assumes that you are installing a binary
36 distribution of Apache. If you want to compile Apache yourself
37 (possibly to help with development or tracking down bugs),
38 see <a href="win_compiling.html">Compiling Apache for Microsoft
41 <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Operating System Requirements</a></li>
42 <li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for Windows</a></li>
43 <li><img alt="" src="../images/down.gif" /> <a href="#cust">Customizing Apache for Windows</a></li>
44 <li><img alt="" src="../images/down.gif" /> <a href="#winsvc">Running Apache as a Service</a></li>
45 <li><img alt="" src="../images/down.gif" /> <a href="#wincons">Running Apache as a Console Application</a></li>
46 <li><img alt="" src="../images/down.gif" /> <a href="#test">Testing the Installation</a></li>
47 <li><img alt="" src="../images/down.gif" /> <a href="#windrivemap">Configuring Access to Network Resources</a></li>
48 </ul><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
49 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
51 <h2><a name="req" id="req">Operating System Requirements</a></h2>
54 <p>The primary Windows platform for running Apache 2.5 is Windows
55 2000 or later. Always obtain and
56 install the current service pack to avoid operating system bugs.</p>
58 <div class="note">Apache HTTP Server versions later than 2.2 will not run on any
59 operating system earlier than Windows 2000.</div>
60 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
62 <h2><a name="down" id="down">Downloading Apache for Windows</a></h2>
65 <p>The Apache HTTP Server Project itself does not provide binary releases of
66 software, only source code. If you cannot compile the Apache HTTP Server
67 yourself, you can obtain a binary package from numerous binary distributions
68 available on the Internet.</p>
70 <p>Popular options for deploying Apache httpd, and, optionally, PHP
71 and MySQL, on Microsoft Windows, include:</p>
73 <li><a href="http://www.apachefriends.org/en/xampp.html">XAMPP, from
74 ApacheFriends</a></li>
75 <li><a href="http://www.wampserver.com/">WampServer</a></li>
77 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
79 <h2><a name="cust" id="cust">Customizing Apache for Windows</a></h2>
82 <p>Apache is configured by the files in the <code>conf</code>
83 subdirectory. These are the same files used to configure the Unix
84 version, but there are a few different directives for Apache on
85 Windows. See the <a href="../mod/directives.html">directive index</a>
86 for all the available directives.</p>
88 <p>The main differences in Apache for Windows are:</p>
90 <li><p>Because Apache for Windows is multithreaded, it does not
91 use a separate process for each request, as Apache can on Unix.
92 Instead there are usually only two Apache processes running: a
93 parent process, and a child which handles the requests. Within
94 the child process each request is handled by a separate thread.
97 <p>The process management directives are also different:</p>
99 <p><code class="directive"><a href="../mod/mpm_common.html#maxconnectionsperchild">MaxConnectionsPerChild</a></code>:
100 Like the Unix directive, this controls how many connections a single
101 child process will serve before exiting.
102 However, unlike on Unix, a replacement process is not instantly
103 available. Use the default <code>MaxConnectionsPerChild 0</code>,
104 unless instructed to change the behavior to overcome a memory leak
105 in third party modules or in-process applications.</p>
107 <div class="warning"><strong>Warning: The server configuration
108 file is reread when a new child process is started. If you have
109 modified <code>httpd.conf</code>, the new child may not start or
110 you may receive unexpected results.</strong></div>
112 <p><code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>:
113 This directive is new. It tells the server how many threads it
114 should use. This is the maximum number of connections the server
115 can handle at once, so be sure to set this number high enough for
116 your site if you get a lot of hits. The recommended default is
117 <code>ThreadsPerChild 150</code>, but this must be adjusted to
118 reflect the greatest anticipated number of simultaneous
119 connections to accept.</p></li>
121 <li><p>The directives that accept filenames as arguments must use
122 Windows filenames instead of Unix ones. However, because Apache
123 may interpret backslashes as an "escape character" sequence, you
124 should consistently use forward slashes in path names, not
125 backslashes.</p></li>
127 <li><p>While filenames are generally case-insensitive on
128 Windows, URLs are still treated internally as case-sensitive
129 before they are mapped to the filesystem. For example, the
130 <code class="directive"><a href="../mod/core.html#location"><Location></a></code>,
131 <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
132 case-sensitive arguments. For this reason, it is particularly
133 important to use the <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> directive when attempting
134 to limit access to content in the filesystem, since this
135 directive applies to any content in a directory, regardless of
136 how it is accessed. If you wish to assure that only lowercase
137 is used in URLs, you can use something like:</p>
139 <pre class="prettyprint lang-config">
141 RewriteMap lowercase int:tolower
142 RewriteCond %{REQUEST_URI} [A-Z]
143 RewriteRule (.*) ${lowercase:$1} [R,L]
147 <li><p>When running, Apache needs write access only to the logs
148 directory and any configured cache directory tree. Due to the
149 issue of case insensitive and short 8.3 format names, Apache must
150 validate all path names given. This means that each directory
151 which Apache evaluates, from the drive root up to the directory
152 leaf, must have read, list and traverse directory permissions.
153 If Apache2.5 is installed at C:\Program Files, then the root
154 directory, Program Files and Apache2.5 must all be visible
157 <li><p>Apache for Windows contains the ability to load modules at
158 runtime, without recompiling the server. If Apache is compiled
159 normally, it will install a number of optional modules in the
160 <code>\Apache2.5\modules</code> directory. To activate these or
161 other modules, the new <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>
162 directive must be used. For example, to activate the status
163 module, use the following (in addition to the status-activating
164 directives in <code>access.conf</code>):</p>
166 <pre class="prettyprint lang-config">
167 LoadModule status_module modules/mod_status.so
171 <p>Information on <a href="../mod/mod_so.html#creating">creating
172 loadable modules</a> is also available.</p></li>
174 <li><p>Apache can also load ISAPI (Internet Server Application
175 Programming Interface) extensions such as those used by Microsoft
176 IIS and other Windows servers. <a href="../mod/mod_isapi.html">More
177 information is available</a>. Note that Apache <strong>cannot</strong>
178 load ISAPI Filters, and ISAPI Handlers with some Microsoft feature
179 extensions will not work.</p></li>
181 <li><p>When running CGI scripts, the method Apache uses to find
182 the interpreter for the script is configurable using the
183 <code class="directive"><a href="../mod/core.html#scriptinterpretersource">ScriptInterpreterSource</a></code>
186 <li><p>Since it is often difficult to manage files with names
187 like <code>.htaccess</code> in Windows, you may find it useful to
188 change the name of this per-directory configuration file using
189 the <code class="directive"><a href="../mod/core.html#accessfilename">AccessFilename</a></code>
192 <li><p>Any errors during Apache startup are logged into the
193 Windows event log when running on Windows NT. This mechanism
194 acts as a backup for those situations where Apache is not yet
195 prepared to use the <code>error.log</code> file. You can
196 review the Windows Application Event Log by using the Event Viewer,
197 e.g. Start - Settings - Control Panel - Administrative Tools
198 - Event Viewer.</p></li>
201 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
202 <div class="section">
203 <h2><a name="winsvc" id="winsvc">Running Apache as a Service</a></h2>
206 <p>Apache comes with a utility called the Apache Service Monitor.
207 With it you can see and manage the state of all installed Apache
208 services on any machine on your network. To be able to manage an
209 Apache service with the monitor, you have to first install the
210 service (either automatically via the installation or manually).
213 <p>You can install Apache as a Windows NT service as follows from
214 the command prompt at the Apache <code>bin</code> subdirectory:</p>
216 <div class="example"><p><code>
220 <p>If you need to specify the name of the service you want to
221 install, use the following command. You have to do this if you
222 have several different service installations of Apache on your
223 computer. If you specify a name during the install, you have to
224 also specify it during any other -k operation.</p>
226 <div class="example"><p><code>
227 httpd.exe -k install -n "MyServiceName"
230 <p>If you need to have specifically named configuration files for
231 different services, you must use this:</p>
233 <div class="example"><p><code>
234 httpd.exe -k install -n "MyServiceName" -f "c:\files\my.conf"
237 <p>If you use the first command without any special parameters except
238 <code>-k install</code>, the service will be called <code>Apache2.5</code>
239 and the configuration will be assumed to be <code>conf\httpd.conf</code>.
242 <p>Removing an Apache service is easy. Just use:</p>
244 <div class="example"><p><code>
245 httpd.exe -k uninstall
248 <p>The specific Apache service to be uninstalled can be specified by using:</p>
250 <div class="example"><p><code>
251 httpd.exe -k uninstall -n "MyServiceName"
254 <p>Normal starting, restarting and shutting down of an Apache
255 service is usually done via the Apache Service Monitor, by using
256 commands like <code>NET START Apache2.5</code> and <code>NET STOP
257 Apache2.5</code> or via normal Windows service management. Before
258 starting Apache as a service by any means, you should test the
259 service's configuration file by using:</p>
261 <div class="example"><p><code>
262 httpd.exe -n "MyServiceName" -t
265 <p>You can control an Apache service by its command line switches,
266 too. To start an installed Apache service you'll use this:</p>
268 <div class="example"><p><code>
269 httpd.exe -k start -n "MyServiceName"
272 <p>To stop an Apache service via the command line switches, use
275 <div class="example"><p><code>
276 httpd.exe -k stop -n "MyServiceName"
281 <div class="example"><p><code>
282 httpd.exe -k shutdown -n "MyServiceName"
285 <p>You can also restart a running service and force it to reread
286 its configuration file by using:</p>
288 <div class="example"><p><code>
289 httpd.exe -k restart -n "MyServiceName"
292 <p>By default, all Apache services are registered to run as the
293 system user (the <code>LocalSystem</code> account). The
294 <code>LocalSystem</code> account has no privileges to your network
295 via any Windows-secured mechanism, including the file system, named
296 pipes, DCOM, or secure RPC. It has, however, wide privileges locally.
299 <div class="warning"><strong>Never grant any network privileges to
300 the <code>LocalSystem</code> account! If you need Apache to be able
301 to access network resources, create a separate account for Apache as
302 noted below.</strong></div>
304 <p>It is recommended that users create a separate account for running
305 Apache service(s). If you have to access network resources via Apache,
306 this is required.</p>
309 <li>Create a normal domain user account, and be sure to
310 memorize its password.</li>
312 <li>Grant the newly-created user a privilege of <code>Log on
313 as a service</code> and <code>Act as part of the operating
314 system</code>. On Windows NT 4.0 these privileges are granted via
315 User Manager for Domains, but on Windows 2000 and XP you probably
316 want to use Group Policy for propagating these settings. You can
317 also manually set these via the Local Security Policy MMC snap-in.
320 <li>Confirm that the created account is a member of the Users
323 <li>Grant the account read and execute (RX) rights to all document
324 and script folders (<code>htdocs</code> and <code>cgi-bin</code>
327 <li>Grant the account change (RWXD) rights to the
328 Apache <code>logs</code> directory.</li>
330 <li>Grant the account read and execute (RX) rights to the
331 <code>httpd.exe</code> binary executable.</li>
334 <div class="note">It is usually a good practice to grant the user the Apache
335 service runs as read and execute (RX) access to the whole Apache2.5
336 directory, except the <code>logs</code> subdirectory, where the
337 user has to have at least change (RWXD) rights.</div>
339 <p>If you allow the account to log in as a user and as a service,
340 then you can log on with that account and test that the account has
341 the privileges to execute the scripts, read the web pages, and that
342 you can start Apache in a console window. If this works, and you
343 have followed the steps above, Apache should execute as a service
344 with no problems.</p>
346 <div class="note"><strong>Error code 2186</strong> is a good indication that
347 you need to review the "Log On As" configuration for the service,
348 since Apache cannot access a required network resource. Also, pay
349 close attention to the privileges of the user Apache is
350 configured to run as.</div>
352 <p>When starting Apache as a service you may encounter an error
353 message from the Windows Service Control Manager. For example,
354 if you try to start Apache by using the Services applet in the
355 Windows Control Panel, you may get the following message:</p>
357 <div class="example"><p><code>
358 Could not start the Apache2.5 service on \\COMPUTER <br />
359 Error 1067; The process terminated unexpectedly.
362 <p>You will get this generic error if there is any problem with
363 starting the Apache service. In order to see what is really causing
364 the problem you should follow the instructions for Running Apache
365 for Windows from the Command Prompt.</p>
367 <p>If you are having problems with the service, it is suggested
368 you follow the instructions below to try starting httpd.exe from
369 a console window, and work out the errors before struggling to
370 start it as a service again.</p>
371 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
372 <div class="section">
373 <h2><a name="wincons" id="wincons">Running Apache as a Console Application</a></h2>
376 <p>Running Apache as a service is usually the recommended way to
377 use it, but it is sometimes easier to work from the command line,
378 especially during initial configuration and testing.</p>
380 <p>To run Apache from the command line as a console application,
381 use the following command:</p>
383 <div class="example"><p><code>
387 <p>Apache will execute, and will remain running until it is stopped
388 by pressing Control-C.</p>
390 <p>You can also run Apache via the shortcut Start Apache in Console
391 placed to <code>Start Menu --> Programs --> Apache HTTP Server
392 2.5.xx --> Control Apache Server</code> during the installation.
393 This will open a console window and start Apache inside it. If you
394 don't have Apache installed as a service, the window will remain
395 visible until you stop Apache by pressing Control-C in the console
396 window where Apache is running in. The server will exit in a few
397 seconds. However, if you do have Apache installed as a service, the
398 shortcut starts the service. If the Apache service is running
399 already, the shortcut doesn't do anything.</p>
401 <p>If Apache is running as a service, you can tell it to stop by opening another console
402 window and entering:</p>
404 <div class="example"><p><code>
405 httpd.exe -k shutdown
408 <p>Running as a service should be preferred over running in a
409 console window because this lets Apache end any current operations
410 and clean up gracefully.</p>
412 <p>But if the server is running in a console window, you can
413 only stop it by pressing Control-C in the same window.</p>
415 <p>You can also tell Apache to restart. This forces it to reread
416 the configuration file. Any operations in progress are allowed to
417 complete without interruption. To restart Apache, either press
418 Control-Break in the console window you used for starting Apache,
421 <div class="example"><p><code>
425 <p>if the server is running as a service.</p>
427 <div class="note">Note for people familiar with the Unix version of Apache:
428 these commands provide a Windows equivalent to <code>kill -TERM
429 <em>pid</em></code> and <code>kill -USR1 <em>pid</em></code>. The
430 command line option used, <code>-k</code>, was chosen as a reminder
431 of the <code>kill</code> command used on Unix.</div>
433 <p>If the Apache console window closes immediately or unexpectedly
434 after startup, open the Command Prompt from the Start Menu -->
435 Programs. Change to the folder to which you installed Apache, type
436 the command <code>httpd.exe</code>, and read the error message. Then
437 change to the logs folder, and review the <code>error.log</code>
438 file for configuration mistakes. Assuming httpd was installed into
439 <code>C:\Program Files\Apache Software Foundation\Apache2.5\</code>,
440 you can do the following:</p>
442 <div class="example"><p><code>
444 cd "\Program Files\Apache Software Foundation\Apache2.5\bin" <br />
448 <p>Then wait for Apache to stop, or press Control-C. Then enter the
451 <div class="example"><p><code>
456 <p>When working with Apache it is important to know how it will
457 find the configuration file. You can specify a configuration file
458 on the command line in two ways:</p>
461 <li><p><code>-f</code> specifies an absolute or relative path to
462 a particular configuration file:</p>
464 <div class="example"><p><code>
465 httpd.exe -f "c:\my server files\anotherconfig.conf"
470 <div class="example"><p><code>
471 httpd.exe -f files\anotherconfig.conf
472 </code></p></div></li>
474 <li><p><code>-n</code> specifies the installed Apache service
475 whose configuration file is to be used:</p>
477 <div class="example"><p><code>
478 httpd.exe -n "MyServiceName"
483 <p>In both of these cases, the proper
484 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> should be set in
485 the configuration file.</p>
487 <p>If you don't specify a configuration file with <code>-f</code>
488 or <code>-n</code>, Apache will use the file name compiled into the
489 server, such as <code>conf\httpd.conf</code>. This built-in path
490 is relative to the installation directory. You can verify the compiled
491 file name from a value labelled as <code>SERVER_CONFIG_FILE</code> when
492 invoking Apache with the <code>-V</code> switch, like this:</p>
494 <div class="example"><p><code>
498 <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>
501 <li>A <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive
502 via the <code>-C</code> command line switch.</li>
504 <li>The <code>-d</code> switch on the command line.</li>
506 <li>Current working directory.</li>
508 <li>A registry entry which was created if you did a binary
511 <li>The server root compiled into the server. This is <code>
512 /apache</code> by default, you can verify it by using <code>
513 httpd.exe -V</code> and looking for a value labelled as
514 <code>HTTPD_ROOT</code>.</li>
517 <p>If you did not do a binary install, Apache will in some
518 scenarios complain about the missing registry key. This warning can
519 be ignored if the server was otherwise able to find its
520 configuration file.</p>
522 <p>The value of this key is the
523 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directory which
524 contains the <code>conf</code> subdirectory. When Apache starts it
525 reads the <code>httpd.conf</code> file from that directory. If
526 this file contains a <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>
527 directive which contains a different directory from the one
528 obtained from the registry key above, Apache will forget the
529 registry key and use the directory from the configuration file. If
530 you copy the Apache directory or configuration files to a new
531 location it is vital that you update the
532 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive in the
533 <code>httpd.conf</code> file to reflect the new location.</p>
534 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
535 <div class="section">
536 <h2><a name="test" id="test">Testing the Installation</a></h2>
539 <p>After starting Apache (either in a console window or as a
540 service) it will be listening on port 80 (unless you changed the
541 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the
542 configuration files or installed Apache only for the current user).
543 To connect to the server and access the default page, launch a
544 browser and enter this URL:</p>
546 <div class="example"><p><code>
550 <p>Apache should respond with a welcome page and you should see
551 "It Works!". If nothing happens or you get an error, look in the
552 <code>error.log</code> file in the <code>logs</code> subdirectory.
553 If your host is not connected to the net, or if you have serious
554 problems with your DNS (Domain Name Service) configuration, you
555 may have to use this URL:</p>
557 <div class="example"><p><code>
561 <p>If you happen to be running Apache on an alternate port, you
562 need to explicitly put that in the URL:</p>
564 <div class="example"><p><code>
565 http://127.0.0.1:8080/
568 <p>Once your basic installation is working, you should configure it
569 properly by editing the files in the <code>conf</code> subdirectory.
570 Again, if you change the configuration of the Windows NT service
571 for Apache, first attempt to start it from the command line to
572 make sure that the service starts with no errors.</p>
574 <p>Because Apache <strong>cannot</strong> share the same port with
575 another TCP/IP application, you may need to stop, uninstall or reconfigure
576 certain other services before running Apache. These conflicting
577 services include other WWW servers, some firewall implementations,
578 and even some client applications (such as Skype) which will use port
579 80 to attempt to bypass firewall issues.</p>
580 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
581 <div class="section">
582 <h2><a name="windrivemap" id="windrivemap">Configuring Access to Network Resources</a></h2>
585 <p>Access to files over the network can be specified using two
586 mechanisms provided by Windows:</p>
589 <dt>Mapped drive letters</dt>
590 <dd>e.g., <code>Alias /images/ Z:/</code></dd>
593 <dd>e.g., <code>Alias /images/ //imagehost/www/images/</code></dd>
596 <p>Mapped drive letters allow the administrator to maintain the
597 mapping to a specific machine and path outside of the Apache httpd
598 configuration. However, these mappings are associated only with
599 interactive sessions and are not directly available to Apache httpd
600 when it is started as a service. <strong>Use only UNC paths for
601 network resources in httpd.conf</strong> so that the resources can
602 be accessed consistently regardless of how Apache httpd is started.
603 (Arcane and error prone procedures may work around the restriction
604 on mapped drive letters, but this is not recommended.)</p>
606 <div class="example"><h3>Example DocumentRoot with UNC path</h3><pre class="prettyprint lang-config">
607 DocumentRoot //dochost/www/html/
611 <div class="example"><h3>Example DocumentRoot with IP address in UNC path</h3><pre class="prettyprint lang-config">
612 DocumentRoot //192.168.1.50/docs/
616 <div class="example"><h3>Example Alias and corresponding Directory with UNC path</h3><pre class="prettyprint lang-config">
617 Alias /images/ //imagehost/www/images/
619 <Directory //imagehost/www/images/>
625 <p>When running Apache httpd as a service, you must create a
626 separate account in order to access network resources, as described
629 <div class="bottomlang">
630 <p><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> |
631 <a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
632 </div><div class="top"><a href="#page-header"><img src="../images/up.gif" alt="top" /></a></div><div class="section"><h2><a id="comments_section" name="comments_section">Comments</a></h2><div class="warning"><strong>Notice:</strong><br />This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed again by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Freenode, or sent to our <a href="http://httpd.apache.org/lists.html">mailing lists</a>.</div>
633 <script type="text/javascript"><!--//--><![CDATA[//><!--
634 var comments_shortname = 'httpd';
635 var comments_identifier = 'http://httpd.apache.org/docs/trunk/platform/windows.html';
637 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
638 d.write('<div id="comments_thread"><\/div>');
639 var s = d.createElement('script');
640 s.type = 'text/javascript';
642 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
643 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
646 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
648 })(window, document);
649 //--><!]]></script></div><div id="footer">
650 <p class="apache">Copyright 2013 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>
651 <p class="menu"><a href="../mod/">Modules</a> | <a href="../mod/quickreference.html">Directives</a> | <a href="http://wiki.apache.org/httpd/FAQ">FAQ</a> | <a href="../glossary.html">Glossary</a> | <a href="../sitemap.html">Sitemap</a></p></div><script type="text/javascript"><!--//--><![CDATA[//><!--
652 if (typeof(prettyPrint) !== 'undefined') {