From: Joshua Slive Date: Sun, 19 Nov 2000 05:04:08 +0000 (+0000) Subject: Remove more of the directives that moved to mpm_common.html X-Git-Tag: APACHE_2_0_ALPHA_8~16 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b93c6a2d01e98732c26cfb1c8bf3011fdc4825b3;p=apache Remove more of the directives that moved to mpm_common.html git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@87022 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/core.html b/docs/manual/mod/core.html index e222e38d9f..194dc4a364 100644 --- a/docs/manual/mod/core.html +++ b/docs/manual/mod/core.html @@ -41,7 +41,6 @@ always available.
  • ErrorLog
  • <Files>
  • <FilesMatch> -
  • Group
  • HostNameLookups
  • IdentityCheck
  • <IfDefine> @@ -55,8 +54,6 @@ always available.
  • LimitRequestFields
  • LimitRequestFieldsize
  • LimitRequestLine -
  • Listen -
  • ListenBacklog
  • <Location>
  • <LocationMatch>
  • LogLevel @@ -71,7 +68,6 @@ always available.
  • RLimitNPROC
  • Satisfy
  • ScriptInterpreterSource -
  • SendBufferSize
  • ServerAdmin
  • ServerAlias
  • ServerName @@ -83,7 +79,6 @@ always available.
  • ThreadStackSize
  • TimeOut
  • UseCanonicalName -
  • User
  • <VirtualHost>
    @@ -966,56 +961,6 @@ different sections are combined when a request is received
    -

    Group directive

    - -Syntax: Group unix-group
    -Default: Group #-1
    -Context: server config, virtual host
    -Status: core
    -Compatibility: Removed in version 2.0

    - -The Group directive sets the group under which the server will answer requests. -In order to use this directive, the stand-alone server must be run initially -as root. Unix-group is one of: -

    -
    A group name -
    Refers to the given group by name. -
    # followed by a group number. -
    Refers to a group by its number. -
    - -It is recommended that you set up a new group specifically for running the -server. Some admins use user nobody, but this is not always -possible or desirable.

    - -Note: if you start the server as a non-root user, it will fail to change -to the specified group, and will instead continue to run as the group of the -original user.

    - -Special note: Use of this directive in <VirtualHost> requires a -properly configured suEXEC wrapper. -When used inside a <VirtualHost> in this manner, only the group -that CGIs are run as is affected. Non-CGI requests are still processed -as the group specified in the main Group directive.

    - -SECURITY: See User for a discussion of the security -considerations.

    -

    HostNameLookups directive

    -

    Listen directive

    -Syntax: -Listen [IP address:]port number
    -Context: server config
    -Status: core
    -Compatibility: Listen is only available in Apache -1.1 and later. Moved in version 2.0 to the MPMs. - -

    The Listen directive instructs Apache to listen to more than one IP -address or port; by default it responds to requests on all IP -interfaces, but only on the port given by the Port directive.

    - -Listen can be used instead of BindAddress and Port. It tells -the server to accept incoming requests on the specified port or -address-and-port combination. If the first format is used, with a port -number only, the server listens to the given port on all interfaces, -instead of the port given by the Port directive. If an IP -address is given as well as a port, the server will listen on the -given port and interface.

    - -Note that you may still require a Port directive so -that URLs that Apache generates that point to your server still -work.

    - -Multiple Listen directives may be used -to specify a number of addresses and ports to listen to. The server -will respond to requests from any of the listed addresses and -ports. -

    - -For example, to make the server accept connections on both port -80 and port 8000, use: -

    -   Listen 80
-   Listen 8000
-
    - -To make the server accept connections on two specified -interfaces and port numbers, use -
    -   Listen 192.170.2.1:80
-   Listen 192.170.2.5:8000
-
    - -

    See Also: -DNS Issues
    -See Also: -Setting which addresses and ports Apache uses
    -See Also: -Known Bugs -

    -
    - -

    ListenBacklog directive

    -Syntax: ListenBacklog backlog
    -Default: ListenBacklog 511
    -Context: server config
    -Status: Core
    -Compatibility: ListenBacklog is only available in Apache -versions after 1.2.0. Moved in version 2.0 to the MPMs. - -

    The maximum length of the queue of pending connections. Generally no -tuning is needed or desired, however on some systems it is desirable -to increase this when under a TCP SYN flood attack. See -the backlog parameter to the listen(2) system call. - -

    This will often be limited to a smaller number by the operating -system. This varies from OS to OS. Also note that many OSes do not -use exactly what is specified as the backlog, but use a number based on -(but normally larger than) what is set. -

    -

    <Location> directive

    -

    SendBufferSize directive

    - -Syntax: SendBufferSize bytes
    -Context: server config
    -Status: core
    -Compatibility: Removed in version 2.0.

    - -The server will set the TCP buffer size to the number of bytes -specified. Very useful to increase past standard OS defaults on high -speed high latency (i.e., 100ms or so, such as transcontinental -fast pipes) -

    -

    ServerAdmin directive

    -

    User directive

    - -Syntax: User unix-userid
    -Default: User #-1
    -Context: server config, virtual host
    -Status: core
    -Compatibility: Removed in version 2.0.

    - -The User directive sets the userid as which the server will answer requests. -In order to use this directive, the standalone server must be run initially -as root. Unix-userid is one of: -

    -
    A username -
    Refers to the given user by name. -
    # followed by a user number. -
    Refers to a user by their number. -
    - -The user should have no privileges which result in it being able to access -files which are not intended to be visible to the outside world, and -similarly, the user should not be able to execute code which is not -meant for httpd requests. It is recommended that you set up a new user and -group specifically for running the server. Some admins use user -nobody, but this is not always possible or desirable. -For example mod_proxy's cache, when enabled, must be accessible to this user -(see the CacheRoot -directive).

    - -Notes: If you start the server as a non-root user, it will fail to change -to the lesser privileged user, and will instead continue to run as -that original user. If you do start the server as root, then it is normal -for the parent process to remain running as root.

    - -Special note: Use of this directive in <VirtualHost> requires a -properly configured suEXEC wrapper. -When used inside a <VirtualHost> in this manner, only the user -that CGIs are run as is affected. Non-CGI requests are still processed -with the user specified in the main User directive.

    - -SECURITY: Don't set User (or Group) to -root unless you know exactly what you are doing, and what the -dangers are.

    -

    <VirtualHost> directive