just "httpd", depending on context.
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@
1933076 13f79535-47bb-0310-9956-
ffa450edef68
<summary>
<p>This document explains how to install, configure and run
<summary>
<p>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
<a href="http://httpd.apache.org/userslist.html">users' mailing
list</a>.</p>
<p>This document assumes that you are installing a binary
reviewing the documentation (and any event and error logs), you
should consult the peer-supported
<a href="http://httpd.apache.org/userslist.html">users' mailing
list</a>.</p>
<p>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),
(possibly to help with development or tracking down bugs),
- see <a href="win_compiling.html">Compiling Apache for Microsoft
+ see <a href="win_compiling.html">Compiling httpd for Microsoft
Windows</a>.</p>
</summary>
<section id="req">
<title>Operating System Requirements</title>
Windows</a>.</p>
</summary>
<section id="req">
<title>Operating System Requirements</title>
- <p>The primary Windows platform for running Apache 2.&httpd.minor; is Windows
+ <p>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.</p>
2000 or later. Always obtain and
install the current service pack to avoid operating system bugs.</p>
</section>
<section id="down">
</section>
<section id="down">
- <title>Downloading Apache for Windows</title>
+ <title>Downloading httpd for Windows</title>
<p>The Apache HTTP Server Project itself does not provide binary releases of
software, only source code. Individual committers <em>may</em> provide
<p>The Apache HTTP Server Project itself does not provide binary releases of
software, only source code. Individual committers <em>may</em> provide
- <title>Customizing Apache for Windows</title>
+ <title>Customizing httpd for Windows</title>
- <p>Apache is configured by the files in the <code>conf</code>
+ <p>Apache httpd is configured by the files in the <code>conf</code>
subdirectory. These are the same files used to configure the Unix
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 <a href="../mod/directives.html">directive index</a>
for all the available directives.</p>
Windows. See the <a href="../mod/directives.html">directive index</a>
for all the available directives.</p>
customize either the default installation root or the overall layout of
the initial configuration.</p>
customize either the default installation root or the overall layout of
the initial configuration.</p>
- <p>The main differences in Apache for Windows are:</p>
+ <p>The main differences in httpd for Windows are:</p>
- <li><p>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
+ <li><p>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.
</p>
parent process, and a child which handles the requests. Within
the child process each request is handled by a separate thread.
</p>
connections to accept.</p></li>
<li><p>The directives that accept filenames as arguments must use
connections to accept.</p></li>
<li><p>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.</p></li>
may interpret backslashes as an "escape character" sequence, you
should consistently use forward slashes in path names, not
backslashes.</p></li>
RewriteRule "(.*)" "${lowercase:$1}" [R,L]
</highlight></li>
RewriteRule "(.*)" "${lowercase:$1}" [R,L]
</highlight></li>
- <li><p>When running, Apache needs write access only to the logs
+ <li><p>When running, httpd needs write access only to the logs
directory and any configured cache directory tree. Due to the
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
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
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
- <li><p>Apache for Windows contains the ability to load modules at
- runtime, without recompiling the server. If Apache is compiled
+ <li><p>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
<code>\Apache2.&httpd.minor;\modules</code> directory. To activate these or
other modules, the <directive module="mod_so">LoadModule</directive>
normally, it will install a number of optional modules in the
<code>\Apache2.&httpd.minor;\modules</code> directory. To activate these or
other modules, the <directive module="mod_so">LoadModule</directive>
<p>Information on <a href="../mod/mod_so.html#creating">creating
loadable modules</a> is also available.</p></li>
<p>Information on <a href="../mod/mod_so.html#creating">creating
loadable modules</a> is also available.</p></li>
- <li><p>Apache can also load ISAPI (Internet Server Application
+ <li><p>httpd can also load ISAPI (Internet Server Application
Programming Interface) extensions such as those used by Microsoft
IIS and other Windows servers. <a href="../mod/mod_isapi.html">More
Programming Interface) extensions such as those used by Microsoft
IIS and other Windows servers. <a href="../mod/mod_isapi.html">More
- information is available</a>. Note that Apache <strong>cannot</strong>
+ information is available</a>. Note that httpd <strong>cannot</strong>
load ISAPI Filters, and ISAPI Handlers with some Microsoft feature
extensions will not work.</p></li>
load ISAPI Filters, and ISAPI Handlers with some Microsoft feature
extensions will not work.</p></li>
- <li><p>When running CGI scripts, the method Apache uses to find
+ <li><p>When running CGI scripts, the method httpd uses to find
the interpreter for the script is configurable using the
<directive module="core">ScriptInterpreterSource</directive>
directive.</p></li>
the interpreter for the script is configurable using the
<directive module="core">ScriptInterpreterSource</directive>
directive.</p></li>
the <directive module="core">AccessFilename</directive>
directive.</p></li>
the <directive module="core">AccessFilename</directive>
directive.</p></li>
- <li><p>Any errors during Apache startup are logged into the
+ <li><p>Any errors during httpd startup are logged into the
Windows event log when running on Windows NT. This mechanism
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 <code>error.log</code> file. You can
review the Windows Application Event Log by using the Event Viewer,
e.g. Start - Settings - Control Panel - Administrative Tools
prepared to use the <code>error.log</code> file. You can
review the Windows Application Event Log by using the Event Viewer,
e.g. Start - Settings - Control Panel - Administrative Tools
</section>
<section id="winsvc">
</section>
<section id="winsvc">
- <title>Running Apache as a Service</title>
+ <title>Running httpd as a Service</title>
- <p>Apache comes with a utility called the Apache Service Monitor.
- With it you can see and manage the state of all installed Apache
+ <p>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
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).
</p>
service (either automatically via the installation or manually).
</p>
- <p>You can install Apache as a Windows NT service as follows from
- the command prompt at the Apache <code>bin</code> subdirectory:</p>
+ <p>You can install httpd as a Windows NT service as follows from
+ the command prompt at the httpd <code>bin</code> subdirectory:</p>
<example>
httpd.exe -k install
<example>
httpd.exe -k install
<p>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
<p>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.</p>
computer. If you specify a name during the install, you have to
also specify it during any other -k operation.</p>
and the configuration will be assumed to be <code>conf\httpd.conf</code>.
</p>
and the configuration will be assumed to be <code>conf\httpd.conf</code>.
</p>
- <p>Removing an Apache service is easy. Just use:</p>
+ <p>Removing an httpd service is easy. Just use:</p>
<example>
httpd.exe -k uninstall
</example>
<example>
httpd.exe -k uninstall
</example>
- <p>The specific Apache service to be uninstalled can be specified by using:</p>
+ <p>The specific httpd service to be uninstalled can be specified by using:</p>
<example>
httpd.exe -k uninstall -n "MyServiceName"
</example>
<example>
httpd.exe -k uninstall -n "MyServiceName"
</example>
- <p>Normal starting, restarting and shutting down of an Apache
+ <p>Normal starting, restarting and shutting down of an httpd
service is usually done via the Apache Service Monitor, by using
commands like <code>NET START Apache2.&httpd.minor;</code> and <code>NET STOP
Apache2.&httpd.minor;</code> or via normal Windows service management. Before
service is usually done via the Apache Service Monitor, by using
commands like <code>NET START Apache2.&httpd.minor;</code> and <code>NET STOP
Apache2.&httpd.minor;</code> 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:</p>
<example>
httpd.exe -n "MyServiceName" -t
</example>
service's configuration file by using:</p>
<example>
httpd.exe -n "MyServiceName" -t
</example>
- <p>You can control an Apache service by its command line switches,
- too. To start an installed Apache service you'll use this:</p>
+ <p>You can control an httpd service by its command line switches,
+ too. To start an installed httpd service you'll use this:</p>
<example>
httpd.exe -k start -n "MyServiceName"
</example>
<example>
httpd.exe -k start -n "MyServiceName"
</example>
- <p>To stop an Apache service via the command line switches, use
+ <p>To stop an httpd service via the command line switches, use
httpd.exe -k restart -n "MyServiceName"
</example>
httpd.exe -k restart -n "MyServiceName"
</example>
- <p>By default, all Apache services are registered to run as the
+ <p>By default, all httpd services are registered to run as the
system user (the <code>LocalSystem</code> account). The
<code>LocalSystem</code> account has no privileges to your network
via any Windows-secured mechanism, including the file system, named
system user (the <code>LocalSystem</code> account). The
<code>LocalSystem</code> account has no privileges to your network
via any Windows-secured mechanism, including the file system, named
</p>
<note type="warning"><strong>Never grant any network privileges to
</p>
<note type="warning"><strong>Never grant any network privileges to
- the <code>LocalSystem</code> account! If you need Apache to be able
- to access network resources, create a separate account for Apache as
+ the <code>LocalSystem</code> account! If you need httpd to be able
+ to access network resources, create a separate account for httpd as
noted below.</strong></note>
<p>It is recommended that users create a separate account for running
noted below.</strong></note>
<p>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.</p>
<ol>
this is required.</p>
<ol>
for example).</li>
<li>Grant the account change (RWXD) rights to the
for example).</li>
<li>Grant the account change (RWXD) rights to the
- Apache <code>logs</code> directory.</li>
+ httpd <code>logs</code> directory.</li>
<li>Grant the account read and execute (RX) rights to the
<code>httpd.exe</code> binary executable.</li>
</ol>
<li>Grant the account read and execute (RX) rights to the
<code>httpd.exe</code> binary executable.</li>
</ol>
- <note>It is usually a good practice to grant the user the Apache
+ <note>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 <code>logs</code> subdirectory, where the
user has to have at least change (RWXD) rights.</note>
service runs as read and execute (RX) access to the whole Apache2.&httpd.minor;
directory, except the <code>logs</code> subdirectory, where the
user has to have at least change (RWXD) rights.</note>
<p>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
<p>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.</p>
<note><strong>Error code 2186</strong> is a good indication that
you need to review the "Log On As" configuration for the service,
with no problems.</p>
<note><strong>Error code 2186</strong> 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.</note>
configured to run as.</note>
- <p>When starting Apache as a service you may encounter an error
+ <p>When starting httpd as a service you may encounter an error
message from the Windows Service Control Manager. For example,
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:</p>
<example>
Windows Control Panel, you may get the following message:</p>
<example>
</example>
<p>You will get this generic error if there is any problem with
</example>
<p>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.</p>
<p>If you are having problems with the service, it is suggested
for Windows from the Command Prompt.</p>
<p>If you are having problems with the service, it is suggested
</section>
<section id="wincons">
</section>
<section id="wincons">
- <title>Running Apache as a Console Application</title>
+ <title>Running httpd as a Console Application</title>
- <p>Running Apache as a service is usually the recommended way to
+ <p>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.</p>
use it, but it is sometimes easier to work from the command line,
especially during initial configuration and testing.</p>
- <p>To run Apache from the command line as a console application,
+ <p>To run httpd from the command line as a console application,
use the following command:</p>
<example>
httpd.exe
</example>
use the following command:</p>
<example>
httpd.exe
</example>
- <p>Apache will execute, and will remain running until it is stopped
+ <p>httpd will execute, and will remain running until it is stopped
by pressing Control-C.</p>
by pressing Control-C.</p>
- <p>You can also run Apache via the shortcut Start Apache in Console
+ <p>You can also run httpd via the shortcut Start Apache in Console
placed to <code>Start Menu --> Programs --> Apache HTTP Server
2.&httpd.minor;.xx --> Control Apache Server</code> during the installation.
placed to <code>Start Menu --> Programs --> Apache HTTP Server
2.&httpd.minor;.xx --> Control Apache Server</code> 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.</p>
already, the shortcut doesn't do anything.</p>
- <p>If Apache is running as a service, you can tell it to stop by opening another console
+ <p>If httpd is running as a service, you can tell it to stop by opening another console
window and entering:</p>
<example>
window and entering:</p>
<example>
</example>
<p>Running as a service should be preferred over running in a
</example>
<p>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.</p>
<p>But if the server is running in a console window, you can
only stop it by pressing Control-C in the same window.</p>
and clean up gracefully.</p>
<p>But if the server is running in a console window, you can
only stop it by pressing Control-C in the same window.</p>
- <p>You can also tell Apache to restart. This forces it to reread
+ <p>You can also tell httpd to restart. This forces it to reread
the configuration file. Any operations in progress are allowed to
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,
<p>if the server is running as a service.</p>
<p>if the server is running as a service.</p>
- <note>Note for people familiar with the Unix version of Apache:
+ <note>Note for people familiar with the Unix version of httpd:
these commands provide a Windows equivalent to <code>kill -TERM
<em>pid</em></code> and <code>kill -USR1 <em>pid</em></code>. The
command line option used, <code>-k</code>, was chosen as a reminder
of the <code>kill</code> command used on Unix.</note>
these commands provide a Windows equivalent to <code>kill -TERM
<em>pid</em></code> and <code>kill -USR1 <em>pid</em></code>. The
command line option used, <code>-k</code>, was chosen as a reminder
of the <code>kill</code> command used on Unix.</note>
- <p>If the Apache console window closes immediately or unexpectedly
+ <p>If the httpd console window closes immediately or unexpectedly
after startup, open the Command Prompt from the Start Menu -->
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 <code>httpd.exe</code>, and read the error message. Then
change to the logs folder, and review the <code>error.log</code>
file for configuration mistakes. Assuming httpd was installed into
the command <code>httpd.exe</code>, and read the error message. Then
change to the logs folder, and review the <code>error.log</code>
file for configuration mistakes. Assuming httpd was installed into
- <p>Then wait for Apache to stop, or press Control-C. Then enter the
+ <p>Then wait for httpd to stop, or press Control-C. Then enter the
more < error.log
</example>
more < error.log
</example>
- <p>When working with Apache it is important to know how it will
+ <p>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:</p>
find the configuration file. You can specify a configuration file
on the command line in two ways:</p>
httpd.exe -f files\anotherconfig.conf
</example></li>
httpd.exe -f files\anotherconfig.conf
</example></li>
- <li><p><code>-n</code> specifies the installed Apache service
+ <li><p><code>-n</code> specifies the installed httpd service
whose configuration file is to be used:</p>
<example>
whose configuration file is to be used:</p>
<example>
the configuration file.</p>
<p>If you don't specify a configuration file with <code>-f</code>
the configuration file.</p>
<p>If you don't specify a configuration file with <code>-f</code>
- or <code>-n</code>, Apache will use the file name compiled into the
+ or <code>-n</code>, httpd will use the file name compiled into the
server, such as <code>conf\httpd.conf</code>. This built-in path
is relative to the installation directory. You can verify the compiled
file name from a value labelled as <code>SERVER_CONFIG_FILE</code> when
server, such as <code>conf\httpd.conf</code>. This built-in path
is relative to the installation directory. You can verify the compiled
file name from a value labelled as <code>SERVER_CONFIG_FILE</code> when
- invoking Apache with the <code>-V</code> switch, like this:</p>
+ invoking httpd with the <code>-V</code> switch, like this:</p>
<example>
httpd.exe -V
</example>
<example>
httpd.exe -V
</example>
- <p>Apache will then try to determine its <directive module="core"
+ <p>httpd will then try to determine its <directive module="core"
>ServerRoot</directive> by trying the following, in this order:</p>
<ol>
>ServerRoot</directive> by trying the following, in this order:</p>
<ol>
<code>HTTPD_ROOT</code>.</li>
</ol>
<code>HTTPD_ROOT</code>.</li>
</ol>
- <p>If you did not do a binary install, Apache will in some
+ <p>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.</p>
<p>The value of this key is the
<directive module="core">ServerRoot</directive> directory which
scenarios complain about the missing registry key. This warning can
be ignored if the server was otherwise able to find its
configuration file.</p>
<p>The value of this key is the
<directive module="core">ServerRoot</directive> directory which
- contains the <code>conf</code> subdirectory. When Apache starts it
+ contains the <code>conf</code> subdirectory. When httpd starts it
reads the <code>httpd.conf</code> file from that directory. If
this file contains a <directive module="core">ServerRoot</directive>
directive which contains a different directory from the one
reads the <code>httpd.conf</code> file from that directory. If
this file contains a <directive module="core">ServerRoot</directive>
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
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
<directive module="core">ServerRoot</directive> directive in the
<code>httpd.conf</code> file to reflect the new location.</p>
location it is vital that you update the
<directive module="core">ServerRoot</directive> directive in the
<code>httpd.conf</code> file to reflect the new location.</p>
<section id="test">
<title>Testing the Installation</title>
<section id="test">
<title>Testing the Installation</title>
- <p>After starting Apache (either in a console window or as a
+ <p>After starting Apache httpd (either in a console window or as a
service) it will be listening on port 80 (unless you changed the
<directive module="mpm_common">Listen</directive> directive in the
service) it will be listening on port 80 (unless you changed the
<directive module="mpm_common">Listen</directive> 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:</p>
To connect to the server and access the default page, launch a
browser and enter this URL:</p>
http://localhost/
</example>
http://localhost/
</example>
- <p>Apache should respond with a welcome page and you should see
+ <p>httpd should respond with a welcome page and you should see
"It Works!". If nothing happens or you get an error, look in the
<code>error.log</code> file in the <code>logs</code> subdirectory.
If your host is not connected to the net, or if you have serious
"It Works!". If nothing happens or you get an error, look in the
<code>error.log</code> file in the <code>logs</code> subdirectory.
If your host is not connected to the net, or if you have serious
http://127.0.0.1/
</example>
http://127.0.0.1/
</example>
- <p>If you happen to be running Apache on an alternate port, you
+ <p>If you happen to be running httpd on an alternate port, you
need to explicitly put that in the URL:</p>
<example>
need to explicitly put that in the URL:</p>
<example>
<p>Once your basic installation is working, you should configure it
properly by editing the files in the <code>conf</code> subdirectory.
Again, if you change the configuration of the Windows NT service
<p>Once your basic installation is working, you should configure it
properly by editing the files in the <code>conf</code> 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.</p>
make sure that the service starts with no errors.</p>
- <p>Because Apache <strong>cannot</strong> share the same port with
+ <p>Because httpd <strong>cannot</strong> share the same port with
another TCP/IP application, you may need to stop, uninstall or reconfigure
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.</p>
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.</p>
projects / thirdparty / apache / httpd.git / commitdiff
