-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
-<HTML>
-<HEAD>
-<TITLE>Server-Wide Configuration</TITLE>
-</HEAD>
-
-<!-- Background white, links blue (unvisited), navy (visited), red (active) -->
-<BODY
- BGCOLOR="#FFFFFF"
- TEXT="#000000"
- LINK="#0000FF"
- VLINK="#000080"
- ALINK="#FF0000"
->
-<!--#include virtual="header.html" -->
-<h1 align="center">Server-Wide Configuration</h1>
-
-<p>This document explains some of the directives provided by the
-<a href="mod/core.html">core</A> server which are used to configure
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en"><head>
+<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type" />
+<!--
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ This file is generated from xml source: DO NOT EDIT
+ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
+ -->
+<title>Server-Wide Configuration - Apache HTTP Server Version 2.5</title>
+<link href="./style/css/manual.css" rel="stylesheet" media="all" type="text/css" title="Main stylesheet" />
+<link href="./style/css/manual-loose-100pc.css" rel="alternate stylesheet" media="all" type="text/css" title="No Sidebar - Default font size" />
+<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" />
+<script src="./style/scripts/prettify.min.js" type="text/javascript">
+</script>
+
+<link href="./images/favicon.ico" rel="shortcut icon" /></head>
+<body id="manual-page"><div id="page-header">
+<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>
+<p class="apache">Apache HTTP Server Version 2.5</p>
+<img alt="" src="./images/feather.png" /></div>
+<div class="up"><a href="./"><img title="<-" alt="<-" src="./images/left.gif" /></a></div>
+<div id="path">
+<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></div><div id="page-content"><div id="preamble"><h1>Server-Wide Configuration</h1>
+<div class="toplang">
+<p><span>Available Languages: </span><a href="./en/server-wide.html" title="English"> en </a> |
+<a href="./fr/server-wide.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
+<a href="./ja/server-wide.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
+<a href="./ko/server-wide.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
+<a href="./tr/server-wide.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
+</div>
+
+<p>This document explains some of the directives provided by
+the <code class="module"><a href="./mod/core.html">core</a></code> server which are used to configure
the basic operations of the server.</p>
-
-<ul>
-<li><a href="#identification">Server Identification</a></li>
-<li><a href="#locations">File Locations</a></li>
-<li><a href="#process">Process Creation</a></li>
-<li><a href="#network">Network Configuration</a></li>
-<li><a href="#resource">Limiting Resource Usage</a></li>
-</ul>
-
-<hr>
-
-<h2><a name="identification">Server Identification</a></h2>
-
-<table border="1">
-<tr><td valign="top">
-<strong>Related Directives</strong><br><br>
-
-<A HREF="mod/core.html#servername">ServerName</A><br>
-<A HREF="mod/core.html#serveradmin">ServerAdmin</A><br>
-<A HREF="mod/core.html#serversignature">ServerSignature</A><br>
-<A HREF="mod/core.html#servertokens">ServerTokens</A><br>
-<A HREF="mod/core.html#usecanonicalname">UseCanonicalName</A><br>
-</td></tr></table>
-
-<p>The <code>ServerAdmin</code> and <code>ServerTokens</code>
-directives control what information about the server will be presented
-in server-generated documents such as error messages.
-The <code>ServerTokens</code> directive sets the value of the
-Server HTTP response header field.</p>
-
-<p>The <code>ServerName</code> and <code>UseCanonicalName</code>
-directives are used by the server to determine how to construct
-self-referential URLs. For example, when a client requests a
-directory, but does not include the trailing slash in the directory
-name, Apache must redirect the client to the full name including the
-trailing slash so that the client will correctly resolve relative
-references in the document.</p>
-
-<hr>
-
-<h2><a name="locations">File Locations</a></h2>
-
-<table border="1">
-<tr><td valign="top">
-<strong>Related Directives</strong><br><br>
-
-<a href="mod/core.html#coredumpdirectory">CoreDumpDirectory</a><br>
-<a href="mod/core.html#documentroot">DocumentRoot</a><br>
-<a href="mod/core.html#errorlog">ErrorLog</a><br>
-<a href="mod/core.html#lockfile">Lockfile</a><br>
-<a href="mod/core.html#pidfile">PidFile</a><br>
-<a href="mod/core.html#scoreboardfile">ScoreBoardFile</a><br>
-<a href="mod/core.html#serverroot">ServerRoot</a><br>
-</td></tr></table>
-
-<p>These directives control the locations of the various files that
-Apache needs for proper operation. When the pathname used does not
-begin with a slash "/", the files are located relative to the
-<code>ServerRoot</code>. Be careful about locating files in paths
-which are writable by non-root users. See the <a
-href="misc/security_tips.html">security tips</a> documentation for
-more details.</p>
-
-<hr>
-
-<h2><a name="process">Process Creation</a></h2>
-
-<table border="1">
-<tr><td valign="top">
-<strong>Related Directives</strong><br><br>
-
-<a href="mod/core.html#bs2000account">BS2000Account</a><br>
-<a href="mod/core.html#group">Group</a><br>
-<a href="mod/core.html#maxclients">MaxClients</a><br>
-<a href="mod/core.html#maxrequestsperchild">MaxRequestsPerChild</a><br>
-<a href="mod/core.html#maxspareservers">MaxSpareServers</a><br>
-<a href="mod/core.html#minspareservers">MinSpareServers</a><br>
-<a href="mod/core.html#servertype">ServerType</a><br>
-<a href="mod/core.html#startservers">StartServers</a><br>
-<a href="mod/core.html#threadsperchild">ThreadsPerChild</a><br>
-<a href="mod/core.html#user">User</a><br>
-</td></tr></table>
-
-<p>When <code>ServerType</code> is set to its recommended value of
-<code>Standalone</code>, Apache 1.3 for Unix is a pre-forking web
-server. A single control process is responsible for launching child
-processes which listen for connections and serve them when they
-arrive. Apache always tries to maintain several <em>spare</em> or
-idle server processes, which stand ready to serve incoming requests.
-In this way, clients do not need to wait for a new child processes to
-be forked before their requests can be served.</p>
-
-<p>The <code>StartServers</code>, <code>MinSpareServers</code>,
-<code>MaxSpareServers</code>, and <code>MaxServers</code> regulate how
-the parent process creates children to serve requests. In general,
-Apache is very self-regulating, so most sites do not need to adjust
-these directives from their default values. Sites which need to serve
-more than 256 simultaneous requests may need to increase
-<code>MaxClients</code>, while sites with limited memory may need to
-decrease <code>MaxClients</code> to keep the server from thrashing
-(swapping memory to disk and back). More information about tuning
-process creation is provided in the <a
-href="misc/perf-tuning.html">performance hints</a> documentation.</p>
-
-<p>While the parent process is usually started as root under Unix
-in order to bind to port 80, the child processes are launched
-by Apache as a less-privileged user. The <code>User</code> and
-<code>Group</code> directives are used to set the privileges
-of the Apache child processes. The child processes must
-be able to read all the content that will be served, but
-should have as few privileges beyond that as possible.
-In addition, unless <a href="suexec.html">suexec</a> is used,
-these directives also set the privileges which will be inherited
-by CGI scripts.</p>
-
-<p><code>MaxRequestsPerChild</code> controls how frequently the server
-recycles processes by killing old ones and launching new ones.</p>
-
-<p>Under Windows, Apache launches one control process and one
-child process. The child process creates multiple threads to
-serve requests. The number of threads is controlled by the
-<code>ThreadsPerChild</code> directive.</p>
-
-<hr>
-
-<h2><a name="network">Network Configuration</a></h2>
-
-<table border="1">
-<tr><td valign="top">
-<strong>Related Directives</strong><br><br>
-
-<a href="mod/core.html#bindaddress">BindAddress</a><br>
-<a href="mod/core.html#keepalive">KeepAlive</a><br>
-<a href="mod/core.html#keepalivetimeout">KeepAliveTimeout</a><br>
-<a href="mod/core.html#listen">Listen</a><br>
-<a href="mod/core.html#listenbacklog">ListenBackLog</a><br>
-<a href="mod/core.html#maxkeepaliverequests">MaxKeepAliveRequests</a><br>
-<a href="mod/core.html#port">Port</a><br>
-<a href="mod/core.html#sendbuffersize">SendBufferSize</a><br>
-<a href="mod/core.html#timeOut">TimeOut</a><br>
-</td></tr></table>
-
-<p>When Apache starts, it connects to some port and address on the
-local machine and waits for incoming requests. By default, it listens
-to all addresses on the machine, and to the port as specified by the
-<code>Port</code> directive in the server configuration. However, it
-can be told to listen to more than one port, to listen to only
-selected addresses, or a combination. This is often combined with the
-<a href="vhosts/">Virtual Host</a> feature which determines how Apache
-responds to different IP addresses, hostnames and ports.</p>
-
-<p>There are two directives used to restrict or specify which addresses
-and ports Apache listens to. The <code>BindAddress</code> directive
-is used to restrict the server to listening to a single IP address.
-The <code>Listen</code> directive can be used to specify multiple
-IP addresses and/or Ports to which Apache will listen.</p>
-
-<p>The <code>ListenBackLog</code>, <code>SendBufferSize</code>, and
-<code>TimeOut</code> directives are used to adjust how Apache
-interacts with the network.</p>
-
-<p>The <code>KeepAlive</code>, <code>KeepAliveTimeout</code>,
-and <code>MaxKeepAliveRequests</code> directives are used to
-configure how Apache handles persistent connections.</p>
-
-<hr>
-<h2><a name="resource">Limiting Resource Usage</a></h2>
-<table border="1">
-<tr><td valign="top">
-<strong>Related Directives</strong><br><br>
-
-<a href="mod/core.html#limitrequestbody">LimitRequestBody</a><br>
-<a href="mod/core.html#limitrequestfields">LimitRequestFields</a><br>
-<a href="mod/core.html#limitrequestfieldsize">LimitRequestFieldsize</a><br>
-<a href="mod/core.html#limitrequestline">LimitRequestLine</a><br>
-<a href="mod/core.html#rlimitcpu">RLimitCPU</a><br>
-<a href="mod/core.html#rlimitmem">RLimitMEM</a><br>
-<a href="mod/core.html#rlimitnproc">RLimitNPROC</a><br>
-<a href="mod/core.html#threadstacksize">ThreadStackSize</a><br>
-</td></tr></table>
-
-<p>The <code>LimitRequest</code>* directives are used to place limits
-on the amount of resources Apache will use in reading requests
-from clients. By limiting these values, some kinds of denial
-of service attacks can be mitigated.</p>
-
-<p>The <code>RLimit</code>* directives are used to limit the amount
-of resources which can be used by processes forked off from
-the Apache children. In particular, this will control
-resources used by CGI scripts and SSI exec commands.</p>
-
-<p>The <code>ThreadStackSize</code> directive is used only
-on Netware to control the stack size.</p>
-
-<!--#include virtual="footer.html" -->
-</BODY>
-</HTML>
+</div>
+<div id="quickview"><ul id="toc"><li><img alt="" src="./images/down.gif" /> <a href="#identification">Server Identification</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#locations">File Locations</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#resource">Limiting Resource Usage</a></li>
+<li><img alt="" src="./images/down.gif" /> <a href="#implementation">Implementation Choices</a></li>
+</ul><h3>See also</h3><ul class="seealso"><li><a href="#comments_section">Comments</a></li></ul></div>
+<div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="identification" id="identification">Server Identification</a><a title="Permanent link" href="#identification" class="permalink">¶</a></h2>
+
+
+ <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="./mod/core.html#servername">ServerName</a></code></li><li><code class="directive"><a href="./mod/core.html#serveradmin">ServerAdmin</a></code></li><li><code class="directive"><a href="./mod/core.html#serversignature">ServerSignature</a></code></li><li><code class="directive"><a href="./mod/core.html#servertokens">ServerTokens</a></code></li><li><code class="directive"><a href="./mod/core.html#usecanonicalname">UseCanonicalName</a></code></li><li><code class="directive"><a href="./mod/core.html#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code></li></ul></td></tr></table>
+
+ <p>The <code class="directive"><a href="./mod/core.html#serveradmin">ServerAdmin</a></code> and
+ <code class="directive"><a href="./mod/core.html#servertokens">ServerTokens</a></code> directives
+ control what information about the server will be presented
+ in server-generated documents such as error messages. The
+ <code class="directive"><a href="./mod/core.html#servertokens">ServerTokens</a></code> directive
+ sets the value of the Server HTTP response header field.</p>
+
+ <p>The <code class="directive"><a href="./mod/core.html#servername">ServerName</a></code>,
+ <code class="directive"><a href="./mod/core.html#usecanonicalname">UseCanonicalName</a></code> and
+ <code class="directive"><a href="./mod/core.html#usecanonicalphysicalport">UseCanonicalPhysicalPort</a></code>
+ directives are used by the server to determine how to construct
+ self-referential URLs. For example, when a client requests a
+ directory, but does not include the trailing slash in the
+ directory name, httpd must redirect the client to the full
+ name including the trailing slash so that the client will
+ correctly resolve relative references in the document.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="locations" id="locations">File Locations</a><a title="Permanent link" href="#locations" class="permalink">¶</a></h2>
+
+
+ <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="./mod/mpm_common.html#coredumpdirectory">CoreDumpDirectory</a></code></li><li><code class="directive"><a href="./mod/core.html#documentroot">DocumentRoot</a></code></li><li><code class="directive"><a href="./mod/core.html#errorlog">ErrorLog</a></code></li><li><code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code></li><li><code class="directive"><a href="./mod/mpm_common.html#pidfile">PidFile</a></code></li><li><code class="directive"><a href="./mod/mpm_common.html#scoreboardfile">ScoreBoardFile</a></code></li><li><code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code></li></ul></td></tr></table>
+
+ <p>These directives control the locations of the various files
+ that httpd needs for proper operation. When the pathname used
+ does not begin with a slash (/), the files are located relative
+ to the <code class="directive"><a href="./mod/core.html#serverroot">ServerRoot</a></code>. Be careful
+ about locating files in paths which are writable by non-root users.
+ See the <a href="misc/security_tips.html#serverroot">security tips</a>
+ documentation for more details.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="resource" id="resource">Limiting Resource Usage</a><a title="Permanent link" href="#resource" class="permalink">¶</a></h2>
+
+
+ <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="./mod/core.html#limitrequestbody">LimitRequestBody</a></code></li><li><code class="directive"><a href="./mod/core.html#limitrequestfields">LimitRequestFields</a></code></li><li><code class="directive"><a href="./mod/core.html#limitrequestfieldsize">LimitRequestFieldsize</a></code></li><li><code class="directive"><a href="./mod/core.html#limitrequestline">LimitRequestLine</a></code></li><li><code class="directive"><a href="./mod/core.html#rlimitcpu">RLimitCPU</a></code></li><li><code class="directive"><a href="./mod/core.html#rlimitmem">RLimitMEM</a></code></li><li><code class="directive"><a href="./mod/core.html#rlimitnproc">RLimitNPROC</a></code></li><li><code class="directive"><a href="./mod/mpm_common.html#threadstacksize">ThreadStackSize</a></code></li></ul></td></tr></table>
+
+ <p>The <code class="directive">LimitRequest</code>*
+ directives are used to place limits on the amount of resources
+ httpd will use in reading requests from clients. By limiting
+ these values, some kinds of denial of service attacks can be
+ mitigated.</p>
+
+ <p>The <code class="directive">RLimit</code>* directives
+ are used to limit the amount of resources which can be used by
+ processes forked off from the httpd children. In particular,
+ this will control resources used by CGI scripts and SSI exec
+ commands.</p>
+
+ <p>The <code class="directive"><a href="./mod/mpm_common.html#threadstacksize">ThreadStackSize</a></code>
+ directive is used with some platforms to control the stack size.</p>
+ </div><div class="top"><a href="#page-header"><img alt="top" src="./images/up.gif" /></a></div>
+<div class="section">
+<h2><a name="implementation" id="implementation">Implementation Choices</a><a title="Permanent link" href="#implementation" class="permalink">¶</a></h2>
+
+
+ <table class="related"><tr><th>Related Modules</th><th>Related Directives</th></tr><tr><td /><td><ul><li><code class="directive"><a href="./mod/core.html#mutex">Mutex</a></code></li></ul></td></tr></table>
+
+ <p>The <code class="directive">Mutex</code> directive can be used to change
+ the underlying implementation used for mutexes, in order to relieve
+ functional or performance problems with <a class="glossarylink" href="./glossary.html#apr" title="see glossary">APR</a>'s
+ default choice.</p>
+ </div></div>
+<div class="bottomlang">
+<p><span>Available Languages: </span><a href="./en/server-wide.html" title="English"> en </a> |
+<a href="./fr/server-wide.html" hreflang="fr" rel="alternate" title="Français"> fr </a> |
+<a href="./ja/server-wide.html" hreflang="ja" rel="alternate" title="Japanese"> ja </a> |
+<a href="./ko/server-wide.html" hreflang="ko" rel="alternate" title="Korean"> ko </a> |
+<a href="./tr/server-wide.html" hreflang="tr" rel="alternate" title="Türkçe"> tr </a></p>
+</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>
+<script type="text/javascript"><!--//--><![CDATA[//><!--
+var comments_shortname = 'httpd';
+var comments_identifier = 'http://httpd.apache.org/docs/trunk/server-wide.html';
+(function(w, d) {
+ if (w.location.hostname.toLowerCase() == "httpd.apache.org") {
+ d.write('<div id="comments_thread"><\/div>');
+ var s = d.createElement('script');
+ s.type = 'text/javascript';
+ s.async = true;
+ s.src = 'https://comments.apache.org/show_comments.lua?site=' + comments_shortname + '&page=' + comments_identifier;
+ (d.getElementsByTagName('head')[0] || d.getElementsByTagName('body')[0]).appendChild(s);
+ }
+ else {
+ d.write('<div id="comments_thread">Comments are disabled for this page at the moment.<\/div>');
+ }
+})(window, document);
+//--><!]]></script></div><div id="footer">
+<p class="apache">Copyright 2018 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>
+<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[//><!--
+if (typeof(prettyPrint) !== 'undefined') {
+ prettyPrint();
+}
+//--><!]]></script>
+</body></html>
\ No newline at end of file
projects / apache / blobdiff