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 <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
6 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
7 This file is generated from xml source: DO NOT EDIT
8 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
10 <title>Using Apache HTTP Server on Microsoft Windows - Apache HTTP Server Version 2.5</title>
11 <link href="../style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
12 <link href="../style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
13 <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" />
14 <script src="../style/scripts/prettify.min.js" type="text/javascript">
17 <link href="../images/favicon.ico" rel="shortcut icon" /></head>
18 <body id="manual-page"><div id="page-header">
19 <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>
20 <p class="apache">Apache HTTP Server Version 2.5</p>
21 <img alt="" src="../images/feather.png" /></div>
22 <div class="up"><a href="./"><img title="<-" alt="<-" src="../images/left.gif" /></a></div>
24 <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>
26 <p><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> |
27 <a href="../fr/platform/windows.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
28 <a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
31 <p>This document explains how to install, configure and run
32 Apache 2.5 under Microsoft Windows. If you have questions after
33 reviewing the documentation (and any event and error logs), you
34 should consult the peer-supported
35 <a href="http://httpd.apache.org/userslist.html">users' mailing
38 <p>This document assumes that you are installing a binary
39 distribution of Apache. If you want to compile Apache yourself
40 (possibly to help with development or tracking down bugs),
41 see <a href="win_compiling.html">Compiling Apache for Microsoft
44 <div id="quickview"><ul id="toc"><li><img alt="" src="../images/down.gif" /> <a href="#req">Operating System Requirements</a></li>
45 <li><img alt="" src="../images/down.gif" /> <a href="#down">Downloading Apache for Windows</a></li>
46 <li><img alt="" src="../images/down.gif" /> <a href="#cust">Customizing Apache for Windows</a></li>
47 <li><img alt="" src="../images/down.gif" /> <a href="#winsvc">Running Apache as a Service</a></li>
48 <li><img alt="" src="../images/down.gif" /> <a href="#wincons">Running Apache as a Console Application</a></li>
49 <li><img alt="" src="../images/down.gif" /> <a href="#test">Testing the Installation</a></li>
50 <li><img alt="" src="../images/down.gif" /> <a href="#windrivemap">Configuring Access to Network Resources</a></li>
51 <li><img alt="" src="../images/down.gif" /> <a href="#tuning">Windows Tuning</a></li>
52 </ul><h3>See also</h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
53 <div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
55 <h2><a name="req" id="req">Operating System Requirements</a> <a title="Permanent link" href="#req" class="permalink">¶</a></h2>
58 <p>The primary Windows platform for running Apache 2.5 is Windows
59 2000 or later. Always obtain and
60 install the current service pack to avoid operating system bugs.</p>
62 <div class="note">Apache HTTP Server versions later than 2.2 will not run on any
63 operating system earlier than Windows 2000.</div>
64 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
66 <h2><a name="down" id="down">Downloading Apache for Windows</a> <a title="Permanent link" href="#down" class="permalink">¶</a></h2>
69 <p>The Apache HTTP Server Project itself does not provide binary releases of
70 software, only source code. Individual committers <em>may</em> provide
71 binary packages as a convenience, but it is not a release deliverable.</p>
72 <p>If you cannot compile the Apache HTTP Server
73 yourself, you can obtain a binary package from numerous binary distributions
74 available on the Internet.</p>
76 <p>Popular options for deploying Apache httpd, and, optionally, PHP
77 and MySQL, on Microsoft Windows, include:</p>
79 <li><a href="http://www.apachehaus.com/cgi-bin/download.plx">ApacheHaus</a></li>
80 <li><a href="http://www.apachelounge.com/download/">Apache Lounge</a></li>
81 <li><a href="http://bitnami.com/stack/wamp">Bitnami WAMP Stack</a></li>
82 <li><a href="http://www.wampserver.com/">WampServer</a></li>
83 <li><a href="http://www.apachefriends.org/en/xampp.html">XAMPP</a></li>
85 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
87 <h2><a name="cust" id="cust">Customizing Apache for Windows</a> <a title="Permanent link" href="#cust" class="permalink">¶</a></h2>
90 <p>Apache is configured by the files in the <code>conf</code>
91 subdirectory. These are the same files used to configure the Unix
92 version, but there are a few different directives for Apache on
93 Windows. See the <a href="../mod/directives.html">directive index</a>
94 for all the available directives.</p>
96 <p>The main differences in Apache for Windows are:</p>
98 <li><p>Because Apache for Windows is multithreaded, it does not
99 use a separate process for each request, as Apache can on Unix.
100 Instead there are usually only two Apache processes running: a
101 parent process, and a child which handles the requests. Within
102 the child process each request is handled by a separate thread.
105 <p>The process management directives are also different:</p>
107 <p><code class="directive"><a href="../mod/mpm_common.html#maxconnectionsperchild">MaxConnectionsPerChild</a></code>:
108 Like the Unix directive, this controls how many connections a single
109 child process will serve before exiting.
110 However, unlike on Unix, a replacement process is not instantly
111 available. Use the default <code>MaxConnectionsPerChild 0</code>,
112 unless instructed to change the behavior to overcome a memory leak
113 in third party modules or in-process applications.</p>
115 <div class="warning"><strong>Warning: The server configuration
116 file is reread when a new child process is started. If you have
117 modified <code>httpd.conf</code>, the new child may not start or
118 you may receive unexpected results.</strong></div>
120 <p><code class="directive"><a href="../mod/mpm_common.html#threadsperchild">ThreadsPerChild</a></code>:
121 This directive is new. It tells the server how many threads it
122 should use. This is the maximum number of connections the server
123 can handle at once, so be sure to set this number high enough for
124 your site if you get a lot of hits. The recommended default is
125 <code>ThreadsPerChild 150</code>, but this must be adjusted to
126 reflect the greatest anticipated number of simultaneous
127 connections to accept.</p></li>
129 <li><p>The directives that accept filenames as arguments must use
130 Windows filenames instead of Unix ones. However, because Apache
131 may interpret backslashes as an "escape character" sequence, you
132 should consistently use forward slashes in path names, not
133 backslashes.</p></li>
135 <li><p>While filenames are generally case-insensitive on
136 Windows, URLs are still treated internally as case-sensitive
137 before they are mapped to the filesystem. For example, the
138 <code class="directive"><a href="../mod/core.html#location"><Location></a></code>,
139 <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
140 case-sensitive arguments. For this reason, it is particularly
141 important to use the <code class="directive"><a href="../mod/core.html#directory"><Directory></a></code> directive when attempting
142 to limit access to content in the filesystem, since this
143 directive applies to any content in a directory, regardless of
144 how it is accessed. If you wish to assure that only lowercase
145 is used in URLs, you can use something like:</p>
147 <pre class="prettyprint lang-config">RewriteEngine On
148 RewriteMap lowercase "int:tolower"
149 RewriteCond "%{REQUEST_URI}" "[A-Z]"
150 RewriteRule "(.*)" "${lowercase:$1}" [R,L]</pre>
153 <li><p>When running, Apache needs write access only to the logs
154 directory and any configured cache directory tree. Due to the
155 issue of case insensitive and short 8.3 format names, Apache must
156 validate all path names given. This means that each directory
157 which Apache evaluates, from the drive root up to the directory
158 leaf, must have read, list and traverse directory permissions.
159 If Apache2.5 is installed at C:\Program Files, then the root
160 directory, Program Files and Apache2.5 must all be visible
163 <li><p>Apache for Windows contains the ability to load modules at
164 runtime, without recompiling the server. If Apache is compiled
165 normally, it will install a number of optional modules in the
166 <code>\Apache2.5\modules</code> directory. To activate these or
167 other modules, the <code class="directive"><a href="../mod/mod_so.html#loadmodule">LoadModule</a></code>
168 directive must be used. For example, to activate the status
169 module, use the following (in addition to the status-activating
170 directives in <code>access.conf</code>):</p>
172 <pre class="prettyprint lang-config">LoadModule status_module "modules/mod_status.so"</pre>
175 <p>Information on <a href="../mod/mod_so.html#creating">creating
176 loadable modules</a> is also available.</p></li>
178 <li><p>Apache can also load ISAPI (Internet Server Application
179 Programming Interface) extensions such as those used by Microsoft
180 IIS and other Windows servers. <a href="../mod/mod_isapi.html">More
181 information is available</a>. Note that Apache <strong>cannot</strong>
182 load ISAPI Filters, and ISAPI Handlers with some Microsoft feature
183 extensions will not work.</p></li>
185 <li><p>When running CGI scripts, the method Apache uses to find
186 the interpreter for the script is configurable using the
187 <code class="directive"><a href="../mod/core.html#scriptinterpretersource">ScriptInterpreterSource</a></code>
190 <li><p>Since it is often difficult to manage files with names
191 like <code>.htaccess</code> in Windows, you may find it useful to
192 change the name of this per-directory configuration file using
193 the <code class="directive"><a href="../mod/core.html#accessfilename">AccessFilename</a></code>
196 <li><p>Any errors during Apache startup are logged into the
197 Windows event log when running on Windows NT. This mechanism
198 acts as a backup for those situations where Apache is not yet
199 prepared to use the <code>error.log</code> file. You can
200 review the Windows Application Event Log by using the Event Viewer,
201 e.g. Start - Settings - Control Panel - Administrative Tools
202 - Event Viewer.</p></li>
205 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
206 <div class="section">
207 <h2><a name="winsvc" id="winsvc">Running Apache as a Service</a> <a title="Permanent link" href="#winsvc" class="permalink">¶</a></h2>
210 <p>Apache comes with a utility called the Apache Service Monitor.
211 With it you can see and manage the state of all installed Apache
212 services on any machine on your network. To be able to manage an
213 Apache service with the monitor, you have to first install the
214 service (either automatically via the installation or manually).
217 <p>You can install Apache as a Windows NT service as follows from
218 the command prompt at the Apache <code>bin</code> subdirectory:</p>
220 <div class="example"><p><code>
224 <p>If you need to specify the name of the service you want to
225 install, use the following command. You have to do this if you
226 have several different service installations of Apache on your
227 computer. If you specify a name during the install, you have to
228 also specify it during any other -k operation.</p>
230 <div class="example"><p><code>
231 httpd.exe -k install -n "MyServiceName"
234 <p>If you need to have specifically named configuration files for
235 different services, you must use this:</p>
237 <div class="example"><p><code>
238 httpd.exe -k install -n "MyServiceName" -f "c:\files\my.conf"
241 <p>If you use the first command without any special parameters except
242 <code>-k install</code>, the service will be called <code>Apache2.5</code>
243 and the configuration will be assumed to be <code>conf\httpd.conf</code>.
246 <p>Removing an Apache service is easy. Just use:</p>
248 <div class="example"><p><code>
249 httpd.exe -k uninstall
252 <p>The specific Apache service to be uninstalled can be specified by using:</p>
254 <div class="example"><p><code>
255 httpd.exe -k uninstall -n "MyServiceName"
258 <p>Normal starting, restarting and shutting down of an Apache
259 service is usually done via the Apache Service Monitor, by using
260 commands like <code>NET START Apache2.5</code> and <code>NET STOP
261 Apache2.5</code> or via normal Windows service management. Before
262 starting Apache as a service by any means, you should test the
263 service's configuration file by using:</p>
265 <div class="example"><p><code>
266 httpd.exe -n "MyServiceName" -t
269 <p>You can control an Apache service by its command line switches,
270 too. To start an installed Apache service you'll use this:</p>
272 <div class="example"><p><code>
273 httpd.exe -k start -n "MyServiceName"
276 <p>To stop an Apache service via the command line switches, use
279 <div class="example"><p><code>
280 httpd.exe -k stop -n "MyServiceName"
285 <div class="example"><p><code>
286 httpd.exe -k shutdown -n "MyServiceName"
289 <p>You can also restart a running service and force it to reread
290 its configuration file by using:</p>
292 <div class="example"><p><code>
293 httpd.exe -k restart -n "MyServiceName"
296 <p>By default, all Apache services are registered to run as the
297 system user (the <code>LocalSystem</code> account). The
298 <code>LocalSystem</code> account has no privileges to your network
299 via any Windows-secured mechanism, including the file system, named
300 pipes, DCOM, or secure RPC. It has, however, wide privileges locally.
303 <div class="warning"><strong>Never grant any network privileges to
304 the <code>LocalSystem</code> account! If you need Apache to be able
305 to access network resources, create a separate account for Apache as
306 noted below.</strong></div>
308 <p>It is recommended that users create a separate account for running
309 Apache service(s). If you have to access network resources via Apache,
310 this is required.</p>
313 <li>Create a normal domain user account, and be sure to
314 memorize its password.</li>
316 <li>Grant the newly-created user a privilege of <code>Log on
317 as a service</code> and <code>Act as part of the operating
318 system</code>. On Windows NT 4.0 these privileges are granted via
319 User Manager for Domains, but on Windows 2000 and XP you probably
320 want to use Group Policy for propagating these settings. You can
321 also manually set these via the Local Security Policy MMC snap-in.
324 <li>Confirm that the created account is a member of the Users
327 <li>Grant the account read and execute (RX) rights to all document
328 and script folders (<code>htdocs</code> and <code>cgi-bin</code>
331 <li>Grant the account change (RWXD) rights to the
332 Apache <code>logs</code> directory.</li>
334 <li>Grant the account read and execute (RX) rights to the
335 <code>httpd.exe</code> binary executable.</li>
338 <div class="note">It is usually a good practice to grant the user the Apache
339 service runs as read and execute (RX) access to the whole Apache2.5
340 directory, except the <code>logs</code> subdirectory, where the
341 user has to have at least change (RWXD) rights.</div>
343 <p>If you allow the account to log in as a user and as a service,
344 then you can log on with that account and test that the account has
345 the privileges to execute the scripts, read the web pages, and that
346 you can start Apache in a console window. If this works, and you
347 have followed the steps above, Apache should execute as a service
348 with no problems.</p>
350 <div class="note"><strong>Error code 2186</strong> is a good indication that
351 you need to review the "Log On As" configuration for the service,
352 since Apache cannot access a required network resource. Also, pay
353 close attention to the privileges of the user Apache is
354 configured to run as.</div>
356 <p>When starting Apache as a service you may encounter an error
357 message from the Windows Service Control Manager. For example,
358 if you try to start Apache by using the Services applet in the
359 Windows Control Panel, you may get the following message:</p>
361 <div class="example"><p><code>
362 Could not start the Apache2.5 service on \\COMPUTER <br />
363 Error 1067; The process terminated unexpectedly.
366 <p>You will get this generic error if there is any problem with
367 starting the Apache service. In order to see what is really causing
368 the problem you should follow the instructions for Running Apache
369 for Windows from the Command Prompt.</p>
371 <p>If you are having problems with the service, it is suggested
372 you follow the instructions below to try starting httpd.exe from
373 a console window, and work out the errors before struggling to
374 start it as a service again.</p>
375 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
376 <div class="section">
377 <h2><a name="wincons" id="wincons">Running Apache as a Console Application</a> <a title="Permanent link" href="#wincons" class="permalink">¶</a></h2>
380 <p>Running Apache as a service is usually the recommended way to
381 use it, but it is sometimes easier to work from the command line,
382 especially during initial configuration and testing.</p>
384 <p>To run Apache from the command line as a console application,
385 use the following command:</p>
387 <div class="example"><p><code>
391 <p>Apache will execute, and will remain running until it is stopped
392 by pressing Control-C.</p>
394 <p>You can also run Apache via the shortcut Start Apache in Console
395 placed to <code>Start Menu --> Programs --> Apache HTTP Server
396 2.5.xx --> Control Apache Server</code> during the installation.
397 This will open a console window and start Apache inside it. If you
398 don't have Apache installed as a service, the window will remain
399 visible until you stop Apache by pressing Control-C in the console
400 window where Apache is running in. The server will exit in a few
401 seconds. However, if you do have Apache installed as a service, the
402 shortcut starts the service. If the Apache service is running
403 already, the shortcut doesn't do anything.</p>
405 <p>If Apache is running as a service, you can tell it to stop by opening another console
406 window and entering:</p>
408 <div class="example"><p><code>
409 httpd.exe -k shutdown
412 <p>Running as a service should be preferred over running in a
413 console window because this lets Apache end any current operations
414 and clean up gracefully.</p>
416 <p>But if the server is running in a console window, you can
417 only stop it by pressing Control-C in the same window.</p>
419 <p>You can also tell Apache to restart. This forces it to reread
420 the configuration file. Any operations in progress are allowed to
421 complete without interruption. To restart Apache, either press
422 Control-Break in the console window you used for starting Apache,
425 <div class="example"><p><code>
429 <p>if the server is running as a service.</p>
431 <div class="note">Note for people familiar with the Unix version of Apache:
432 these commands provide a Windows equivalent to <code>kill -TERM
433 <em>pid</em></code> and <code>kill -USR1 <em>pid</em></code>. The
434 command line option used, <code>-k</code>, was chosen as a reminder
435 of the <code>kill</code> command used on Unix.</div>
437 <p>If the Apache console window closes immediately or unexpectedly
438 after startup, open the Command Prompt from the Start Menu -->
439 Programs. Change to the folder to which you installed Apache, type
440 the command <code>httpd.exe</code>, and read the error message. Then
441 change to the logs folder, and review the <code>error.log</code>
442 file for configuration mistakes. Assuming httpd was installed into
443 <code>C:\Program Files\Apache Software Foundation\Apache2.5\</code>,
444 you can do the following:</p>
446 <div class="example"><p><code>
448 cd "\Program Files\Apache Software Foundation\Apache2.5\bin" <br />
452 <p>Then wait for Apache to stop, or press Control-C. Then enter the
455 <div class="example"><p><code>
460 <p>When working with Apache it is important to know how it will
461 find the configuration file. You can specify a configuration file
462 on the command line in two ways:</p>
465 <li><p><code>-f</code> specifies an absolute or relative path to
466 a particular configuration file:</p>
468 <div class="example"><p><code>
469 httpd.exe -f "c:\my server files\anotherconfig.conf"
474 <div class="example"><p><code>
475 httpd.exe -f files\anotherconfig.conf
476 </code></p></div></li>
478 <li><p><code>-n</code> specifies the installed Apache service
479 whose configuration file is to be used:</p>
481 <div class="example"><p><code>
482 httpd.exe -n "MyServiceName"
487 <p>In both of these cases, the proper
488 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> should be set in
489 the configuration file.</p>
491 <p>If you don't specify a configuration file with <code>-f</code>
492 or <code>-n</code>, Apache will use the file name compiled into the
493 server, such as <code>conf\httpd.conf</code>. This built-in path
494 is relative to the installation directory. You can verify the compiled
495 file name from a value labelled as <code>SERVER_CONFIG_FILE</code> when
496 invoking Apache with the <code>-V</code> switch, like this:</p>
498 <div class="example"><p><code>
502 <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>
505 <li>A <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive
506 via the <code>-C</code> command line switch.</li>
508 <li>The <code>-d</code> switch on the command line.</li>
510 <li>Current working directory.</li>
512 <li>A registry entry which was created if you did a binary
515 <li>The server root compiled into the server. This is <code>
516 /apache</code> by default, you can verify it by using <code>
517 httpd.exe -V</code> and looking for a value labelled as
518 <code>HTTPD_ROOT</code>.</li>
521 <p>If you did not do a binary install, Apache will in some
522 scenarios complain about the missing registry key. This warning can
523 be ignored if the server was otherwise able to find its
524 configuration file.</p>
526 <p>The value of this key is the
527 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directory which
528 contains the <code>conf</code> subdirectory. When Apache starts it
529 reads the <code>httpd.conf</code> file from that directory. If
530 this file contains a <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code>
531 directive which contains a different directory from the one
532 obtained from the registry key above, Apache will forget the
533 registry key and use the directory from the configuration file. If
534 you copy the Apache directory or configuration files to a new
535 location it is vital that you update the
536 <code class="directive"><a href="../mod/core.html#serverroot">ServerRoot</a></code> directive in the
537 <code>httpd.conf</code> file to reflect the new location.</p>
538 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
539 <div class="section">
540 <h2><a name="test" id="test">Testing the Installation</a> <a title="Permanent link" href="#test" class="permalink">¶</a></h2>
543 <p>After starting Apache (either in a console window or as a
544 service) it will be listening on port 80 (unless you changed the
545 <code class="directive"><a href="../mod/mpm_common.html#listen">Listen</a></code> directive in the
546 configuration files or installed Apache only for the current user).
547 To connect to the server and access the default page, launch a
548 browser and enter this URL:</p>
550 <div class="example"><p><code>
554 <p>Apache should respond with a welcome page and you should see
555 "It Works!". If nothing happens or you get an error, look in the
556 <code>error.log</code> file in the <code>logs</code> subdirectory.
557 If your host is not connected to the net, or if you have serious
558 problems with your DNS (Domain Name Service) configuration, you
559 may have to use this URL:</p>
561 <div class="example"><p><code>
565 <p>If you happen to be running Apache on an alternate port, you
566 need to explicitly put that in the URL:</p>
568 <div class="example"><p><code>
569 http://127.0.0.1:8080/
572 <p>Once your basic installation is working, you should configure it
573 properly by editing the files in the <code>conf</code> subdirectory.
574 Again, if you change the configuration of the Windows NT service
575 for Apache, first attempt to start it from the command line to
576 make sure that the service starts with no errors.</p>
578 <p>Because Apache <strong>cannot</strong> share the same port with
579 another TCP/IP application, you may need to stop, uninstall or reconfigure
580 certain other services before running Apache. These conflicting
581 services include other WWW servers, some firewall implementations,
582 and even some client applications (such as Skype) which will use port
583 80 to attempt to bypass firewall issues.</p>
584 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
585 <div class="section">
586 <h2><a name="windrivemap" id="windrivemap">Configuring Access to Network Resources</a> <a title="Permanent link" href="#windrivemap" class="permalink">¶</a></h2>
589 <p>Access to files over the network can be specified using two
590 mechanisms provided by Windows:</p>
593 <dt>Mapped drive letters</dt>
594 <dd>e.g., <code>Alias /images/ Z:/</code></dd>
597 <dd>e.g., <code>Alias /images/ //imagehost/www/images/</code></dd>
600 <p>Mapped drive letters allow the administrator to maintain the
601 mapping to a specific machine and path outside of the Apache httpd
602 configuration. However, these mappings are associated only with
603 interactive sessions and are not directly available to Apache httpd
604 when it is started as a service. <strong>Use only UNC paths for
605 network resources in httpd.conf</strong> so that the resources can
606 be accessed consistently regardless of how Apache httpd is started.
607 (Arcane and error prone procedures may work around the restriction
608 on mapped drive letters, but this is not recommended.)</p>
610 <div class="example"><h3>Example DocumentRoot with UNC path</h3><pre class="prettyprint lang-config">DocumentRoot "//dochost/www/html/"</pre>
613 <div class="example"><h3>Example DocumentRoot with IP address in UNC path</h3><pre class="prettyprint lang-config">DocumentRoot "//192.168.1.50/docs/"</pre>
616 <div class="example"><h3>Example Alias and corresponding Directory with UNC path</h3><pre class="prettyprint lang-config">Alias "/images/" "//imagehost/www/images/"
618 <Directory "//imagehost/www/images/">
620 <Directory></pre>
623 <p>When running Apache httpd as a service, you must create a
624 separate account in order to access network resources, as described
626 </div><div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
627 <div class="section">
628 <h2><a name="tuning" id="tuning">Windows Tuning</a> <a title="Permanent link" href="#tuning" class="permalink">¶</a></h2>
631 <li><p>If more than a few dozen piped loggers are used on an operating system
632 instance, scaling up the "desktop heap" is often necessary. For
633 more detailed information, refer to the <a href="../logs.html#piped">piped logging</a> documentation.</p></li>
636 <div class="bottomlang">
637 <p><span>Available Languages: </span><a href="../en/platform/windows.html" title="English"> en </a> |
638 <a href="../fr/platform/windows.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
639 <a href="../ko/platform/windows.html" hreflang="ko" rel="alternate" title="Korean"> ko </a></p>
640 </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>
641 <script type="text/javascript"><!--//--><![CDATA[//><!--
642 var comments_shortname = 'httpd';
643 var comments_identifier = 'http://httpd.apache.org/docs/trunk/platform/windows.html';
645 if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
646 d.write('<div id="comments_thread"><\/div>');
647 var s = d.createElement('script');
648 s.type = 'text/javascript';
650 s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
651 (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
654 d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
656 })(window, document);
657 //--><!]]></script></div><div id="footer">
658 <p class="apache">Copyright 2019 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>
659 <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[//><!--
660 if (typeof(prettyPrint) !== 'undefined') {