From 344a41a2ce7d2198e76c1b24cad3e9fd149c1a30 Mon Sep 17 00:00:00 2001 From: Rich Bowen Date: Tue, 14 Apr 2026 20:41:23 +0000 Subject: [PATCH] Replace uses of "Apache" with "Apache HTTP Server", "Apache httpd" or just "httpd", depending on context. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1933076 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/platform/windows.xml | 176 +++++++++++++++---------------- 1 file changed, 88 insertions(+), 88 deletions(-) diff --git a/docs/manual/platform/windows.xml b/docs/manual/platform/windows.xml index f9b70ecedb..19fd89d8ac 100644 --- a/docs/manual/platform/windows.xml +++ b/docs/manual/platform/windows.xml @@ -27,23 +27,23 @@

This document explains how to install, configure and run - Apache 2.&httpd.minor; under Microsoft Windows. If you have questions after + Apache HTTP Server 2.&httpd.minor; under Microsoft Windows. If you have questions after reviewing the documentation (and any event and error logs), you should consult the peer-supported users' mailing list.

This document assumes that you are installing a binary - distribution of Apache. If you want to compile Apache yourself + distribution of httpd. If you want to compile Apache httpd yourself (possibly to help with development or tracking down bugs), - see Compiling Apache for Microsoft + see Compiling httpd for Microsoft Windows.
Operating System Requirements -

The primary Windows platform for running Apache 2.&httpd.minor; is Windows +

The primary Windows platform for running Apache httpd 2.&httpd.minor; is Windows 2000 or later. Always obtain and install the current service pack to avoid operating system bugs.

@@ -52,7 +52,7 @@
- Downloading Apache for Windows + Downloading httpd for Windows

The Apache HTTP Server Project itself does not provide binary releases of software, only source code. Individual committers may provide @@ -71,11 +71,11 @@

- Customizing Apache for Windows + Customizing httpd for Windows -

Apache is configured by the files in the conf +

Apache httpd is configured by the files in the conf subdirectory. These are the same files used to configure the Unix - version, but there are a few different directives for Apache on + version, but there are a few different directives for httpd on Windows. See the directive index for all the available directives.

@@ -86,11 +86,11 @@ customize either the default installation root or the overall layout of the initial configuration.

-

The main differences in Apache for Windows are:

+

The main differences in httpd for Windows are:

    -

  • Because Apache for Windows is multithreaded, it does not - use a separate process for each request, as Apache can on Unix. - Instead there are usually only two Apache processes running: a +

  • Because httpd for Windows is multithreaded, it does not + use a separate process for each request, as httpd can on Unix. + Instead there are usually only two httpd processes running: a parent process, and a child which handles the requests. Within the child process each request is handled by a separate thread.

    @@ -120,7 +120,7 @@ connections to accept.

  • The directives that accept filenames as arguments must use - Windows filenames instead of Unix ones. However, because Apache + Windows filenames instead of Unix ones. However, because httpd may interpret backslashes as an "escape character" sequence, you should consistently use forward slashes in path names, not backslashes.

    • @@ -146,18 +146,18 @@ RewriteCond "%{REQUEST_URI}" "[A-Z]" RewriteRule "(.*)" "${lowercase:$1}" [R,L] -

  • When running, Apache needs write access only to the logs +

  • When running, httpd needs write access only to the logs directory and any configured cache directory tree. Due to the - issue of case insensitive and short 8.3 format names, Apache must + issue of case insensitive and short 8.3 format names, httpd must validate all path names given. This means that each directory - which Apache evaluates, from the drive root up to the directory + which httpd evaluates, from the drive root up to the directory leaf, must have read, list and traverse directory permissions. If Apache2.&httpd.minor; is installed at C:\Program Files, then the root directory, Program Files and Apache2.&httpd.minor; must all be visible - to Apache.

    • + to httpd.

    -

  • Apache for Windows contains the ability to load modules at - runtime, without recompiling the server. If Apache is compiled +

  • httpd for Windows contains the ability to load modules at + runtime, without recompiling the server. If httpd is compiled normally, it will install a number of optional modules in the \Apache2.&httpd.minor;\modules directory. To activate these or other modules, the LoadModule @@ -172,14 +172,14 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

    Information on creating loadable modules is also available.

    • -

  • Apache can also load ISAPI (Internet Server Application +

  • httpd can also load ISAPI (Internet Server Application Programming Interface) extensions such as those used by Microsoft IIS and other Windows servers. More - information is available. Note that Apache cannot + information is available. Note that httpd cannot load ISAPI Filters, and ISAPI Handlers with some Microsoft feature extensions will not work.

    • -

  • When running CGI scripts, the method Apache uses to find +

  • When running CGI scripts, the method httpd uses to find the interpreter for the script is configurable using the ScriptInterpreterSource directive.

    • @@ -190,9 +190,9 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] the AccessFilename directive.

    -

  • Any errors during Apache startup are logged into the +

  • Any errors during httpd startup are logged into the Windows event log when running on Windows NT. This mechanism - acts as a backup for those situations where Apache is not yet + acts as a backup for those situations where httpd is not yet prepared to use the error.log file. You can review the Windows Application Event Log by using the Event Viewer, e.g. Start - Settings - Control Panel - Administrative Tools @@ -202,17 +202,17 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

- Running Apache as a Service + Running httpd as a Service -

Apache comes with a utility called the Apache Service Monitor. - With it you can see and manage the state of all installed Apache +

Apache httpd comes with a utility called the Apache Service Monitor. + With it you can see and manage the state of all installed httpd services on any machine on your network. To be able to manage an - Apache service with the monitor, you have to first install the + httpd service with the monitor, you have to first install the service (either automatically via the installation or manually).

-

You can install Apache as a Windows NT service as follows from - the command prompt at the Apache bin subdirectory:

+

You can install httpd as a Windows NT service as follows from + the command prompt at the httpd bin subdirectory:

httpd.exe -k install @@ -220,7 +220,7 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

If you need to specify the name of the service you want to install, use the following command. You have to do this if you - have several different service installations of Apache on your + have several different service installations of httpd on your computer. If you specify a name during the install, you have to also specify it during any other -k operation.

@@ -240,37 +240,37 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] and the configuration will be assumed to be conf\httpd.conf.

-

Removing an Apache service is easy. Just use:

+

Removing an httpd service is easy. Just use:

httpd.exe -k uninstall -

The specific Apache service to be uninstalled can be specified by using:

+

The specific httpd service to be uninstalled can be specified by using:

httpd.exe -k uninstall -n "MyServiceName" -

Normal starting, restarting and shutting down of an Apache +

Normal starting, restarting and shutting down of an httpd service is usually done via the Apache Service Monitor, by using commands like NET START Apache2.&httpd.minor; and NET STOP Apache2.&httpd.minor; or via normal Windows service management. Before - starting Apache as a service by any means, you should test the + starting httpd as a service by any means, you should test the service's configuration file by using:

httpd.exe -n "MyServiceName" -t -

You can control an Apache service by its command line switches, - too. To start an installed Apache service you'll use this:

+

You can control an httpd service by its command line switches, + too. To start an installed httpd service you'll use this:

httpd.exe -k start -n "MyServiceName" -

To stop an Apache service via the command line switches, use +

To stop an httpd service via the command line switches, use this:

@@ -290,7 +290,7 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] httpd.exe -k restart -n "MyServiceName" -

By default, all Apache services are registered to run as the +

By default, all httpd services are registered to run as the system user (the LocalSystem account). The LocalSystem account has no privileges to your network via any Windows-secured mechanism, including the file system, named @@ -298,12 +298,12 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

Never grant any network privileges to - the LocalSystem account! If you need Apache to be able - to access network resources, create a separate account for Apache as + the LocalSystem account! If you need httpd to be able + to access network resources, create a separate account for httpd as noted below.

It is recommended that users create a separate account for running - Apache service(s). If you have to access network resources via Apache, + httpd service(s). If you have to access network resources via httpd, this is required.

    @@ -326,13 +326,13 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] for example).
  1. Grant the account change (RWXD) rights to the - Apache logs directory.
    2. + httpd logs directory.
  2. Grant the account read and execute (RX) rights to the httpd.exe binary executable.
- It is usually a good practice to grant the user the Apache + It is usually a good practice to grant the user the httpd service runs as read and execute (RX) access to the whole Apache2.&httpd.minor; directory, except the logs subdirectory, where the user has to have at least change (RWXD) rights. @@ -340,19 +340,19 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

If you allow the account to log in as a user and as a service, then you can log on with that account and test that the account has the privileges to execute the scripts, read the web pages, and that - you can start Apache in a console window. If this works, and you - have followed the steps above, Apache should execute as a service + you can start httpd in a console window. If this works, and you + have followed the steps above, httpd should execute as a service with no problems.

Error code 2186 is a good indication that you need to review the "Log On As" configuration for the service, - since Apache cannot access a required network resource. Also, pay - close attention to the privileges of the user Apache is + since httpd cannot access a required network resource. Also, pay + close attention to the privileges of the user httpd is configured to run as. -

When starting Apache as a service you may encounter an error +

When starting httpd as a service you may encounter an error message from the Windows Service Control Manager. For example, - if you try to start Apache by using the Services applet in the + if you try to start httpd by using the Services applet in the Windows Control Panel, you may get the following message:

@@ -361,8 +361,8 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

You will get this generic error if there is any problem with - starting the Apache service. In order to see what is really causing - the problem you should follow the instructions for Running Apache + starting the httpd service. In order to see what is really causing + the problem you should follow the instructions for Running httpd for Windows from the Command Prompt.

If you are having problems with the service, it is suggested @@ -372,34 +372,34 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

- Running Apache as a Console Application + Running httpd as a Console Application -

Running Apache as a service is usually the recommended way to +

Running Apache httpd as a service is usually the recommended way to use it, but it is sometimes easier to work from the command line, especially during initial configuration and testing.

-

To run Apache from the command line as a console application, +

To run httpd from the command line as a console application, use the following command:

httpd.exe -

Apache will execute, and will remain running until it is stopped +

httpd will execute, and will remain running until it is stopped by pressing Control-C.

-

You can also run Apache via the shortcut Start Apache in Console +

You can also run httpd via the shortcut Start Apache in Console placed to Start Menu --> Programs --> Apache HTTP Server 2.&httpd.minor;.xx --> Control Apache Server during the installation. - This will open a console window and start Apache inside it. If you - don't have Apache installed as a service, the window will remain - visible until you stop Apache by pressing Control-C in the console - window where Apache is running in. The server will exit in a few - seconds. However, if you do have Apache installed as a service, the - shortcut starts the service. If the Apache service is running + This will open a console window and start httpd inside it. If you + don't have httpd installed as a service, the window will remain + visible until you stop httpd by pressing Control-C in the console + window where httpd is running in. The server will exit in a few + seconds. However, if you do have httpd installed as a service, the + shortcut starts the service. If the httpd service is running already, the shortcut doesn't do anything.

-

If Apache is running as a service, you can tell it to stop by opening another console +

If httpd is running as a service, you can tell it to stop by opening another console window and entering:

@@ -407,16 +407,16 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

Running as a service should be preferred over running in a - console window because this lets Apache end any current operations + console window because this lets httpd end any current operations and clean up gracefully.

But if the server is running in a console window, you can only stop it by pressing Control-C in the same window.

-

You can also tell Apache to restart. This forces it to reread +

You can also tell httpd to restart. This forces it to reread the configuration file. Any operations in progress are allowed to - complete without interruption. To restart Apache, either press - Control-Break in the console window you used for starting Apache, + complete without interruption. To restart httpd, either press + Control-Break in the console window you used for starting httpd, or enter

@@ -425,15 +425,15 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

if the server is running as a service.

- Note for people familiar with the Unix version of Apache: + Note for people familiar with the Unix version of httpd: these commands provide a Windows equivalent to kill -TERM pid and kill -USR1 pid. The command line option used, -k, was chosen as a reminder of the kill command used on Unix. -

If the Apache console window closes immediately or unexpectedly +

If the httpd console window closes immediately or unexpectedly after startup, open the Command Prompt from the Start Menu --> - Programs. Change to the folder to which you installed Apache, type + Programs. Change to the folder to which you installed httpd, type the command httpd.exe, and read the error message. Then change to the logs folder, and review the error.log file for configuration mistakes. Assuming httpd was installed into @@ -446,7 +446,7 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] httpd.exe -

Then wait for Apache to stop, or press Control-C. Then enter the +

Then wait for httpd to stop, or press Control-C. Then enter the following:

@@ -454,7 +454,7 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] more < error.log -

When working with Apache it is important to know how it will +

When working with httpd it is important to know how it will find the configuration file. You can specify a configuration file on the command line in two ways:

@@ -472,7 +472,7 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] httpd.exe -f files\anotherconfig.conf -

  • -n specifies the installed Apache service +

  • -n specifies the installed httpd service whose configuration file is to be used:

    @@ -486,17 +486,17 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] the configuration file.

    If you don't specify a configuration file with -f - or -n, Apache will use the file name compiled into the + or -n, httpd will use the file name compiled into the server, such as conf\httpd.conf. This built-in path is relative to the installation directory. You can verify the compiled file name from a value labelled as SERVER_CONFIG_FILE when - invoking Apache with the -V switch, like this:

    + invoking httpd with the -V switch, like this:

    httpd.exe -V -

    Apache will then try to determine its httpd will then try to determine its ServerRoot by trying the following, in this order:

      @@ -516,20 +516,20 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] HTTPD_ROOT.
    -

    If you did not do a binary install, Apache will in some +

    If you did not do a binary install, httpd will in some scenarios complain about the missing registry key. This warning can be ignored if the server was otherwise able to find its configuration file.

    The value of this key is the ServerRoot directory which - contains the conf subdirectory. When Apache starts it + contains the conf subdirectory. When httpd starts it reads the httpd.conf file from that directory. If this file contains a ServerRoot directive which contains a different directory from the one - obtained from the registry key above, Apache will forget the + obtained from the registry key above, httpd will forget the registry key and use the directory from the configuration file. If - you copy the Apache directory or configuration files to a new + you copy the httpd directory or configuration files to a new location it is vital that you update the ServerRoot directive in the httpd.conf file to reflect the new location.

    @@ -538,10 +538,10 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]
    Testing the Installation -

    After starting Apache (either in a console window or as a +

    After starting Apache httpd (either in a console window or as a service) it will be listening on port 80 (unless you changed the Listen directive in the - configuration files or installed Apache only for the current user). + configuration files or installed httpd only for the current user). To connect to the server and access the default page, launch a browser and enter this URL:

    @@ -549,7 +549,7 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] http://localhost/ -

    Apache should respond with a welcome page and you should see +

    httpd should respond with a welcome page and you should see "It Works!". If nothing happens or you get an error, look in the error.log file in the logs subdirectory. If your host is not connected to the net, or if you have serious @@ -560,7 +560,7 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L] http://127.0.0.1/ -

    If you happen to be running Apache on an alternate port, you +

    If you happen to be running httpd on an alternate port, you need to explicitly put that in the URL:

    @@ -570,12 +570,12 @@ RewriteRule "(.*)" "${lowercase:$1}" [R,L]

    Once your basic installation is working, you should configure it properly by editing the files in the conf subdirectory. Again, if you change the configuration of the Windows NT service - for Apache, first attempt to start it from the command line to + for httpd, first attempt to start it from the command line to make sure that the service starts with no errors.

    -

    Because Apache cannot share the same port with +

    Because httpd cannot share the same port with another TCP/IP application, you may need to stop, uninstall or reconfigure - certain other services before running Apache. These conflicting + certain other services before running httpd. These conflicting services include other WWW servers, some firewall implementations, and even some client applications (such as Skype) which will use port 80 to attempt to bypass firewall issues.

    -- 2.47.3