X-Git-Url: https://granicus.if.org/sourcecode?a=blobdiff_plain;f=docs%2Fmanual%2Fserver-wide.html.en;h=2ebee8a1bdbb9e1e6e7c975c6f868ddb0fdd1e4d;hb=5464a1ae693bf0fa7a850df511ffcfc99903e71e;hp=e74c989792c2fc0266d3baa975da1152b0bca9f1;hpb=5347b4715f26723df0db4777315860c934fda4a8;p=apache diff --git a/docs/manual/server-wide.html.en b/docs/manual/server-wide.html.en index e74c989792..2ebee8a1bd 100644 --- a/docs/manual/server-wide.html.en +++ b/docs/manual/server-wide.html.en @@ -1,26 +1,33 @@ - -Server-Wide Configuration - Apache HTTP Server +Server-Wide Configuration - Apache HTTP Server Version 2.5 - + + + + +

Apache HTTP Server Version 2.5

+
<-
-Apache > HTTP Server > Documentation > Version 2.3

Server-Wide Configuration

+Apache > HTTP Server > Documentation > Version 2.5

Server-Wide Configuration

Available Languages:  en  | + fr  |  ja  | - ko 

+ ko  | + tr 

This document explains some of the directives provided by @@ -30,10 +37,11 @@ the basic operations of the server.

+
  • Implementation Choices
  • +

    See also

    top
    -

    Server Identification

    +

    Server Identification

    @@ -51,18 +59,18 @@ the basic operations of the server.

    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 + 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.

    top
    -

    File Locations

    +

    File Locations

    - +

    These directives control the locations of the various files - that Apache needs for proper operation. When the pathname used + that httpd needs for proper operation. When the pathname used does not begin with a slash (/), the files are located relative to the ServerRoot. Be careful about locating files in paths which are writable by non-root users. @@ -70,31 +78,65 @@ the basic operations of the server.

    documentation for more details.

    top
    -

    Limiting Resource Usage

    +

    Limiting Resource Usage

    The LimitRequest* directives are used to place limits on the amount of resources - Apache will use in reading requests from clients. By limiting + httpd will use in reading requests from clients. By limiting these values, some kinds of denial of service attacks can be mitigated.

    The RLimit* directives are used to limit the amount of resources which can be used by - processes forked off from the Apache children. In particular, + processes forked off from the httpd children. In particular, this will control resources used by CGI scripts and SSI exec commands.

    The ThreadStackSize directive is used with some platforms to control the stack size.

    +
    top
    +
    +

    Implementation Choices

    + + + + +

    The Mutex directive can be used to change + the underlying implementation used for mutexes, in order to relieve + functional or performance problems with APR's + default choice.

    Available Languages:  en  | + fr  |  ja  | - ko 

    -
    + ko  | + tr 

    +
    top

    Comments

    Notice:
    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 mailing lists.
    +
    \ No newline at end of file