📄 httpd.conf-dist-nw
字号:
## Based upon the NCSA server configuration files originally by Rob McCool.## This is the main Apache server configuration file. It contains the# configuration directives that give the server its instructions.# See <URL:http://httpd.apache.org/docs/> for detailed information about# the directives.## Do NOT simply read the instructions in here without understanding# what they do. They're here only as hints or reminders. If you are unsure# consult the online docs. You have been warned. ## After this file is processed, the server will look for and process# sys:/apache/conf/srm.conf and then sys:/apache/conf/access.conf# unless you have overridden these with ResourceConfig and/or# AccessConfig directives here.## The configuration directives are grouped into three basic sections:# 1. Directives that control the operation of the Apache server process as a# whole (the 'global environment').# 2. Directives that define the parameters of the 'main' or 'default' server,# which responds to requests that aren't handled by a virtual host.# These directives also provide default values for the settings# of all virtual hosts.# 3. Settings for virtual hosts, which allow Web requests to be sent to# different IP addresses or hostnames and have them handled by the# same Apache server process.## Configuration and logfile names: If the filenames you specify for many# of the server's control files begin with "/" (or "drive:/" for Win32 and# sys:/ for NetWare), the server will use that explicit path. If the# filenames do *not* begin with "/", the value of ServerRoot is prepended# -- so "logs/foo.log" with ServerRoot set to "/usr/local/apache" will be# interpreted by the server as "/usr/local/apache/logs/foo.log".#### Section 1: Global Environment## The directives in this section affect the overall operation of Apache,# such as the number of concurrent requests it can handle or where it# can find its configuration files.### ServerType is either inetd, or standalone. Inetd mode is only supported on# Unix platforms.#ServerType standalone## ServerRoot: The top of the directory tree under which the server's# configuration, error, and log files are kept.## NOTE! If you intend to place this on an NFS (or otherwise network)# mounted filesystem then please read the LockFile documentation# (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);# you will save yourself a lot of trouble.#ServerRoot "sys:/apache"## PidFile: The file in which the server should record its process# identification number when it starts.#PidFile logs/httpd.pid## ScoreBoardFile: File used to store internal server process information.# Not all architectures require this. But if yours does (you'll know because# this file will be created when you run Apache) then you *must* ensure that# no two invocations of Apache share the same scoreboard file.#ScoreBoardFile logs/apache_status## In the standard configuration, the server will process this file,# srm.conf, and access.conf in that order. The latter two files are# now distributed empty, as it is recommended that all directives# be kept in a single file for simplicity. The commented-out values# below are the built-in defaults. You can have the server ignore# these files altogether by using "/dev/null" (for Unix) or# "nul" (for Win32) for the arguments to the directives.##ResourceConfig conf/srm.conf#AccessConfig conf/access.conf## Timeout: The number of seconds before receives and sends time out.#Timeout 300## KeepAlive: Whether or not to allow persistent connections (more than# one request per connection). Set to "Off" to deactivate.#KeepAlive On## MaxKeepAliveRequests: The maximum number of requests to allow# during a persistent connection. Set to 0 to allow an unlimited amount.# We recommend you leave this number high, for maximum performance.#MaxKeepAliveRequests 100## KeepAliveTimeout: Number of seconds to wait for the next request from the# same client on the same connection.#KeepAliveTimeout 15## Number of concurrent threads (i.e., requests) the server will allow.# Set this value according to the responsiveness of the server (more# requests active at once means they're all handled more slowly) and# the amount of system resources you'll allow the server to consume.#ThreadsPerChild 50## When NetWare creates a thread you need to specify the stack size.# You may need to increase this if you get stack overflows.# ThreadStackSize 65536ThreadStackSize 65536## MaxRequestsPerChild: the number of requests each child process is# allowed to process before the child dies. The child will exit so# as to avoid problems after prolonged use when Apache (and maybe the# libraries it uses) leak memory or other resources. On most systems, this# isn't really needed, but a few (such as Solaris) do have notable leaks# in the libraries. For these platforms, set to something like 10000# or so; a setting of 0 means unlimited.## NOTE: This value does not include keepalive requests after the initial# request per connection. For example, if a child process handles# an initial request and 10 subsequent "keptalive" requests, it# would only count as 1 request towards this limit.#MaxRequestsPerChild 0## Listen: Allows you to bind Apache to specific IP addresses and/or# ports, instead of the default. See also the <VirtualHost># directive.##Listen 3000#Listen 12.34.56.78:80## BindAddress: You can support virtual hosts with this option. This directive# is used to tell the server which IP address to listen to. It can either# contain "*", an IP address, or a fully qualified Internet domain name.# See also the <VirtualHost> and Listen directives.##BindAddress *## Dynamic Shared Object (DSO) Support## To be able to use the functionality of a module which was built as a DSO you# have to place corresponding `LoadModule' lines at this location so the# directives contained in it are actually available _before_ they are used.# Please read the file http://httpd.apache.org/docs/dso.html for more# details about the DSO mechanism and run `httpd -l' for the list of already# built-in (statically linked and thus always available) modules in your httpd# binary.## Note: The order is which modules are loaded is important. Don't change# the order below without expert advice.# LoadModule anon_auth_module modules/authanon.nlm# LoadModule cern_meta_module modules/cernmeta.nlm# LoadModule digest_module modules/digest.nlm# LoadModule expires_module modules/expires.nlm# LoadModule log_forensic_module modules/forensic.nlm# LoadModule headers_module modules/headers.nlm# LoadModule proxy_module modules/proxy.nlm# LoadModule rewrite_module modules/rewrite.nlm# LoadModule speling_module modules/speling.nlm# LoadModule status_module modules/status.nlm# LoadModule info_module modules/info.nlm# LoadModule unique_id_module modules/uniqueid.nlm# LoadModule usertrack_module modules/usrtrack.nlm# LoadModule tls_module modules/mod_tls.nlm# LoadModule vhost_alias_module modules/vhost.nlm## ExtendedStatus controls whether Apache will generate "full" status# information (ExtendedStatus On) or just basic information (ExtendedStatus# Off) when the "server-status" handler is called. The default is Off.##ExtendedStatus On### Section 2: 'Main' server configuration## The directives in this section set up the values used by the 'main'# server, which responds to any requests that aren't handled by a# <VirtualHost> definition. These values also provide defaults for# any <VirtualHost> containers you may define later in the file.## All of these directives may appear inside <VirtualHost> containers,# in which case these default settings will be overridden for the# virtual host being defined.### Port: The port to which the standalone server listens. For# ports < 1023, you will need httpd to be run as root initially.#Port 80## ServerAdmin: Your address, where problems with the server should be# e-mailed. This address appears on some server-generated pages, such# as error documents.#ServerAdmin you@example.com## ServerName allows you to set a host name which is sent back to clients for# your server if it's different than the one the program would get (i.e., use# "www" instead of the host's real name).## Note: You cannot just invent host names and hope they work. The name you # define here must be a valid DNS name for your host. If you don't understand# this, ask your network administrator.# If your host doesn't have a registered DNS name, enter its IP address here.# You will have to access it by its address (e.g., http://123.45.67.89/)# anyway, and this will make redirections work in a sensible way.#ServerName 123.45.67.89## DocumentRoot: The directory out of which you will serve your# documents. By default, all requests are taken from this directory, but# symbolic links and aliases may be used to point to other locations.#DocumentRoot "sys:/apache/htdocs"## Each directory to which Apache has access, can be configured with respect# to which services and features are allowed and/or disabled in that# directory (and its subdirectories). ## First, we configure the "default" to be a very restrictive set of # permissions. #<Directory /> Options FollowSymLinks AllowOverride None</Directory>## Note that from this point forward you must specifically allow# particular features to be enabled - so if something's not working as# you might expect, make sure that you have specifically enabled it# below.### This should be changed to whatever you set DocumentRoot to.#<Directory "sys:/apache/htdocs">## This may also be "None", "All", or any combination of "Indexes",# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".## Note that "MultiViews" must be named *explicitly* --- "Options All"# doesn't give it to you.# Options Indexes FollowSymLinks MultiViews## This controls which options the .htaccess files in directories can# override. Can also be "All", or any combination of "Options", "FileInfo", # "AuthConfig", and "Limit"# AllowOverride None## Controls who can get stuff from this server.# Order allow,deny Allow from all</Directory>## UserDir: The name of the directory which is appended onto a user's home# directory if a ~user request is received.#<IfModule mod_userdir.c> UserDir /home/*/public_html</IfModule>## Control access to UserDir directories. The following is an example# for a site where these directories are restricted to read-only.##<Directory /home/*/public_html># AllowOverride FileInfo AuthConfig Limit# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec# <Limit GET POST OPTIONS PROPFIND># Order allow,deny# Allow from all# </Limit># <LimitExcept GET POST OPTIONS PROPFIND># Order deny,allow# Deny from all# </LimitExcept>#</Directory>## DirectoryIndex: Name of the file or files to use as a pre-written HTML# directory index. Separate multiple entries with spaces.#<IfModule mod_dir.c> DirectoryIndex index.html</IfModule>## AccessFileName: The name of the file to look for in each directory# for access control information.#AccessFileName .htaccess## The following lines prevent .htaccess files from being viewed by# Web clients. Since .htaccess files often contain authorization# information, access is disallowed for security reasons. Comment# these lines out if you want Web visitors to see the contents of# .htaccess files. If you change the AccessFileName directive above,# be sure to make the corresponding changes here.## Also, folks tend to use names such as .htpasswd for password# files, so this will protect those as well.#<Files ~ "^\.ht"> Order allow,deny Deny from all Satisfy All</Files>## CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each# document that was negotiated on the basis of content. This asks proxy# servers not to cache the document. Uncommenting the following line disables# this behavior, and proxies will be allowed to cache the documents.##CacheNegotiatedDocs## UseCanonicalName: (new for 1.3) With this setting turned on, whenever# Apache needs to construct a self-referencing URL (a URL that refers back# to the server the response is coming from) it will use ServerName and# Port to form a "canonical" name. With this setting off, Apache will# use the hostname:port that the client supplied, when possible. This# also affects SERVER_NAME and SERVER_PORT in CGI scripts.#UseCanonicalName On## TypesConfig describes where the mime.types file (or equivalent) is# to be found.#<IfModule mod_mime.c> TypesConfig conf/mime.types</IfModule>## DefaultType is the default MIME type the server will use for a document# if it cannot otherwise determine one, such as from filename extensions.# If your server contains mostly text or HTML documents, "text/plain" is# a good value. If most of your content is binary, such as applications# or images, you may want to use "application/octet-stream" instead to# keep browsers from trying to display binary files as though they are# text.#DefaultType text/plain## The mod_mime_magic module allows the server to use various hints from the# contents of the file itself to determine its type. The MIMEMagicFile# directive tells the module where the hint definitions are located.# mod_mime_magic is not part of the default server (you have to add# it yourself with a LoadModule [see the DSO paragraph in the 'Global# Environment' section], or recompile the server and include mod_mime_magic# as part of the configuration), so it's enclosed in an <IfModule> container.# This means that the MIMEMagicFile directive will only be processed if the# module is part of the server.#<IfModule mod_mime_magic.c> MIMEMagicFile conf/magic</IfModule>## HostnameLookups: Log the names of clients or just their IP addresses# e.g., www.apache.org (on) or 204.62.129.132 (off).# The default is off because it'd be overall better for the net if people# had to knowingly turn this feature on, since enabling it means that# each client request will result in AT LEAST one lookup request to the# nameserver.#HostnameLookups Off## LogRotateDaily: If set to 'on' log files rotate daily.# LogRotateInterval n: If set, log files rotate after n minutes.# The LogRotateDaily and LogRotateInterval directives are mutually# exclusive. The rotated log file name adds the date suffix of # YYYYMMDD to identify when the log was rotated.## LogRotateDaily on# LogRotateInterval 86400## ErrorLog: The location of the error log file.# If you do not specify an ErrorLog directive within a <VirtualHost># container, error messages relating to that virtual host will be# logged here. If you *do* define an error logfile for a <VirtualHost># container, that host's errors will be logged there and not here.#ErrorLog logs/error_log## LogLevel: Control the number of messages logged to the error_log.# Possible values include: debug, info, notice, warn, error, crit,# alert, emerg.#LogLevel warn## The following directives define some format nicknames for use with# a CustomLog directive (see below).#LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combinedLogFormat "%h %l %u %t \"%r\" %>s %b" commonLogFormat "%{Referer}i -> %U" refererLogFormat "%{User-agent}i" agent## The location and format of the access logfile (Common Logfile Format).# If you do not define any access logfiles within a <VirtualHost># container, they will be logged here. Contrariwise, if you *do*# define per-<VirtualHost> access logfiles, transactions will be# logged therein and *not* in this file.#CustomLog logs/access_log common#
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -