![[APACHE DOCUMENTATION]](../images/sub.gif)
이 환경 변수(configuration parameters)들은 주요 아파치 기능(features)을 제어합니다. 그리고 특별한 모듈없이 항상 가능한 선언들 입니다.
AccessConfig conf/access.conf액서스(접근)을
제어하기 위한 환경설정파일을 지정합니다 .
서버는
ResourceConfig 파일을 읽어 들인 후에
이곳에서 지정한 파일을 읽어 들입니다.Filename 은 ServerRoot
에 상대적인 경로 입니다. 이 기능은 다음과 같이 하여
사용하지 않을 수 있습니다.(win32에서는 해당 없음)
AccessConfig /dev/nullAccessFileName .htaccess해당 디렉토리에 위치하여 문서에 대한 접근을 제어 하는 파일에 대한 선언입니다. 다음과 같이 사용하면 디렉토리에 대한 사용자 접근(Access)를 제어할 파일을 지정 할 수 있습니다.
AccessFileName .acl
<Directory />
AllowOverride None
</Directory>win32 에서는 .으로 시작하는 파일이름으로 새로만들기를 할 수 없습니다. _acl 이나 다른 이름을 지정할 수 있습니다.
AddDefaultCharset Off이 선언은 문자집합의 기본값을 지정합니다. 이 문자
집합은 HTTP headers 안의 문서 형식에서 어떤 매개변수도 갖고
있지 않은 응답에 추가됩니다. 이것은 META tag 를
경유해서 문서의 body 에서 지정된 문자집합이 있을 경우 그
값으로 덥어씌어(Override) 집니다. AddDefaultCharset Off
로 셋팅하면 이 기능은 사용하지 않으며, AddDefaultCharset On
으로 셋팅할 경우 아파치 내부 기본값인 iso-8859-1
문자집합을 사용합니다.as required by the
directive. 또한 다른 언어집합을 지정할 수도 있습니다. ;
e.g. AddDefaultCharset utf-8 , AddDefaultCharset euc-kr.
모듈을 추가하는 선언. 아파치 서버는
활성화 되지 않은 채로 컴파일된 모듈을 가지고 있습니다.
이 선언은 그런 모듈을 사용할 수 있도록 합니다. 서버는
활성화된 모듈은 저절로 로드되는데 이 리스트는 ClearModuleList
선언을 사용해서 지울수 있습니다.
참고) windows용 아파치에 컴파일시 포함된 모듈 ( apache -l 로
확인 가능 , 전부 모듈로 활성화 되어 있음)
http_core.c mod_so.c mod_mime.c mod_access.c mod_auth.c mod_negotiation.c mod_include.c mod_autoindex.c mod_dir.c mod_cgi.c mod_userdir.c
mod_alias.c mod_env.c mod_log_config.c mod_asis.c mod_imap.c mod_actions.c mod_setenvif.c mod_isapi.c
AllowOverride All서버가 디렉토리별 액서스를 제어하는 .htaccess 파일(AccessFileName 에서 지정됨)이 있을 경우, 이 파일에서 지정된 액서스 정보를 기존에 지정된 정보와 비교하여 적용되어질 것인지 아닌지에 대한 선언 입니다.
덥어쓰기( Override ) 는 None
으로 셋팅할 경우 서버는 이 액서스 정보가 들어
있는 파일을 읽지 않습니다. All 로 셋팅할
경우에는 모든 선언에 대해서 읽어 적용시키며, 다음과 같이
부분적으로 적용 시킬 수도 있습니다.
인증이름(도메인) 선언. 이 선언은 어떤 디렉토리에 대한 인증 realm 의 이름을 지정합니다. realm 은 사용자 이름과 패스워드를 알고 있는 사용자(클라이언트) 에게 주어지는 것입니다(팦업으로 인증창이 떠오를때 표시됨). AuthName 은 하나의 인수로 사용합니다. 만약 이곳에 공란(Space)이 들어 간다면 " (따옴표) 를 사용하여 묶어 주면 됩니다. 이 선언은 받드시 AuthType 와 require 선언을 동반합니다. 그리고 AuthUserFile 이나 AuthGroupFile 과 같은 선언을 통해 작동 합니다.
인증형식 지정. 이 선언은
디렉토리별 사용자 인증의 형식을 선택합니다. Basic
과 Digest 중 하나를 선택할 수 있습니다.
반드시 AuthName
과
require 선언을 수반하며,
AuthUserFile 과
AuthGroupFile 와 같은 선언을
통해 작동합니다.
BindAddress *유닉스 http 서버 에서 해당 되는 사항입니다.
A Unix® http server can either listen for connections to every IP address of the server machine, or just one IP address of the server machine. Saddr can be
BindAddress 선언은 단지 하나의 IP에 대해서만
사용될 수 있습니다. 아파치가 주의를 기울일 주소나 포트
가 많다면 대신 Listen 선언을
사용하여 제어 하도록 합니다. ( Only one can be used. For more
control over which address and ports Apache listens to, use the
Listen directive instead of
BindAddress. )
BindAddress 는 virtual hosts(가상호스트)를
지원하기 위해 사용됩니다.(<VirtualHost> 섹션(sections)을
사용하는 대신)
See Also:
DNS Issues
See Also:
Setting which addresses and ports Apache uses
BS2000Account
선언은 BS2000 hosts 에서만 가능한 선언 입니다. It must be used to define the account number for the non-privileged
apache server user (which was configured using the
User directive).
This is required by the BS2000 POSIX subsystem (to change the underlying
BS2000 task environment by performing a sub-LOGON) to prevent CGI scripts
from accessing resources of the privileged account which started the
server, usually SYSROOT.
Only one BS2000Account directive can be used.
See Also: Apache EBCDIC port
모듈을 지우는 선언. 서버는 컴파일시 활성화된 모듈들을 가지고 있습니다. 이 선언은 그러한 모듈을 전부 지웁니다. 이 선언을 사용한 다음에는 AddModule 선언을 사용해서 필요한 모듈은 다시 추가해 주어야 합니다.
ContentDigest off
이 선언은 Content-MD5 헤더를 생성합니다. 이 Content-MD5
헤더는 RFC1864, RFC2068.에서 각각 정의 되었습니다.
MD5 는 임의의 길이를 갖는 DATA의 "message digest"("fingerprint",지문이라 불리기도 함) 를 컴퓨팅 하기 위한 알고리즘 입니다. 어떤 DATA 의 변경은 'message digest.'의 변경에 반영 됩니다.
Content-MD5 header 는 End-To-End
MIC(message
integrity check)제공합니다. 프락시나 클라이언트는 전체
내용이 전송되는 동안 일어날수 있는 수정사항에 대해서
감지하기 위해 이 헤더를 체크할 것입니다. 헤더의 예를
들면 다음과 같습니다.
Content-MD5: AuLb7Dp1rqtRtxz2m9kRpA==
이 기능은 message digest 가 모든 요청에 대해 계산(compute)할 때 까지 퍼포먼스(수행능력) 문제를 일으킬수 있습니다. ( 이 값은 캐쉬되지 않음 )
Content-MD5 는 아파치 주(core) 기능에만 제공됩니다(다른
모듈에서는 서비스되지 않음). 예를 들면 SSI documents,
CGI scripts 로 부터의 출력, 그리고 and 바이트(byte) 범위의
응답에 대해서는 이 헤더를 갖지 않습니다.
This controls the directory to which Apache attempts to switch before dumping core. The default is in the ServerRoot directory, however since this should not be writable by the user the server runs as, core dumps won't normally get written. If you want a core dump for debugging, you can use this directive to place it in a different location.
덤프(dump) : 파일 내용을 다른 장치 또는 다른 파일로 보내는 것을 말함 . 만약 디버깅을 위해서 코어 덤프를 원한다면 , 이 선언에서 directory 에 다른 위치를 지정해 주면 됩니다.
DefaultType text/html기본 컨텐츠 형식 선언. MIME 형식에 매핑되어 있지 않은 확장자에 대해서 주어진 기본값을 사용합니다.
서버는 문서의 컨텐츠-형식을
알려주게 되어 있습니다. 그래서 알수 없는 형식의 확장자에
대해서는 DefaultType 을 사용합니다. 예를 들면,
DefaultType image/gif디렉토리 기능 선언. <Directory> 와 </Directory> 는 디렉토리의 그룹을 둘러싸는데 사용됩니다. 여기서 지정된 디렉토리는 그 디렉토리와 하위 디렉토리에 적용됩니다. directory context 로 혀용되는 모든 선언을 사용할 수 있습니다. Directory 는 디렉토리의 전체경로(실제디렉토리)를 써주며, 와일드 카드를 사용할 수 있습니다. 와일드 카드 사용에 있어서, '?' 는 하나의 문자와 매치되고 '*' 는 어떤 문자로도 대치될 수 있습니다. Apache 1.3 이상에서는 `[]' 문자열을 사용할 수도 있으며 또한 와일드 카드없이는 `/' 문자에 매치 되지 않습니다. 예를 들면:
<Directory /usr/local/httpd/htdocs> Options Indexes FollowSymLinks </Directory>
Apache 1.2 와 그이상:
확장된 regular expressions 을 ~ 문자와 함께 사용될
수 있습니다. . 예를 들면:
<Directory ~ "^/www/.*/[0-9]{3}">
이것은 /www/ 하위에 있는 디렉토리중 3개의 숫자로
구성된 디렉토리와 일치 합니다.만약 복수의 디렉토리 섹션에있어서(non-regular expression) 적용되는 순서는 루트(가장 짧은 디렉토리)가 가장 먼저 적용되며 하위디렉토리 에 대한 선언이나 해당디렉토리의 액서스(접근)을 제어하는 파일(기본값은 .htaccess) 에 의해서 다시 적용됩니다. 아래의 예를 가지고 설명을 하자면,
<Directory />
AllowOverride None
</Directory>
<Directory /home/*>
AllowOverride FileInfo
</Directory>
/home/web/dir/doc.html 라는 문서에 대해서:
AllowOverride None 이 적용(disabling
.htaccess 파일에 의해서 액서스 제어가 불가).
AllowOverride FileInfo 가 적용 (directory
/home/web 에 대해서) .
/home/web/.htaccess 에 선언된 파일정보에
대해서만 적용됨
Regular expression directory sections are handled slightly differently by Apache 1.2 and 1.3. In Apache 1.2 they are interspersed with the normal directory sections and applied in the order they appear in the configuration file. They are applied only once, and apply when the shortest match possible occurs. In Apache 1.3 regular expressions are not considered until after all of the normal sections have been applied. Then all of the regular expressions are tested in the order they appeared in the configuration file. For example, with
<Directory ~ abc$>
... directives here ...
</Directory>
/home/abc/public_html/abc/index.html. The server
considers each of /, /home, /home/abc,
/home/abc/public_html, and /home/abc/public_html/abc
in that order. In Apache 1.2, when
/home/abc is considered, the regular expression will match
and be applied. In Apache 1.3 the regular expression isn't considered
at all at that point in the tree. It won't be considered until after
all normal <Directory>s and .htaccess files have
been applied. Then the regular expression will
match on /home/abc/public_html/abc and be applied.
Note that the default Apache access for <Directory /> is Allow from All. This means that Apache will serve any file mapped from an URL. It is recommended that you change this with a block such as
아파치는 <Directory /> 에서 액서스 제어의 기본값을 선언 하고 있습니다. 배포되는 httpd.conf 에서 Allow from All 이라고 되어 있는데.. 이것은 어떤 URL 에 매핑되어 있는 어떤 파일도 제공한다는 것을 의미 합니다. 보안상 이 부분을 아래와 같이 바꾸어 주길 권장 합니다.
<Directory />
Order Deny,Allow
Deny from All
</Directory>
그리고 나서 액서스를 허용하는 디렉터리만 따로 액서스를 허용하도록 합니다. Security Tips 에서 자세한 설명을 보실 수 있습니다.
이 디렉터리 섹션은 전통적으로 access.conf 파일에서 선언 됩니다. 하지만 어떤 설정파일에서도 사용할 수는 있습니다. <Directory> 선언은 중첩해서 사용할 수 없으며, <Limit> 이나 <LimitExcept> 섹션 사이에서는 사용할 수 없습니다.See also: How Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is received
<DirectoryMatch> 와 </DirectoryMatch> 는 <Directory>와 같이 지정된 디렉터리와 그 하위 디렉터리에 적용될 선언들을 그룹지어 주는데 사용합니다. 이 선언은 정규표현을 인수(argument) 로 사용합니다. 예를 들면,
<DirectoryMatch "^/www/.*/[0-9]{3}">
/www/ 아래에 있는 3개의 숫자로 구성된 디렉터리에 매치됩니다.
See Also:
<Directory> ( 정규표현을 normal <Directory>에서
혼합해서 사용하는 방법에 대한 요약 )
See also: How Directory,
Location and Files sections work ( 요청이 있을때 이 서로다른
섹션들이 어떻게 조합이 되는지에 대한 설명 )
DocumentRoot
/usr/local/apache/htdocs이 선언은 아파치 웹 서버가 제공할 문서의 최상위디렉토리를 지정합니다. 만약 다음과 같이 선언 하였을 경우,
DocumentRoot d:/usr/web
http://www.my.host.com/index.html 라는 주소로
접속하는 것은 d:/usr/web/index.html 에 있는
파일을 보게 되는 것입니다.
주의 할 것은 DocumentRoot 선언에서 마지막에 디렉토리를
구분하는 슬래쉬('/')를 쓰지 않는 다는 것입니다. (i.e., "DocumentRoot
d:/usr/web/" 와 같이 선언 하였을 경우 d:/usr/web//index.html
를 찾을 수 없기 때문에 버그 처럼 보일수도 있습니다.)
문가 있는 경우나 에러가 발생 했을때, 아파치는 다음 네가지 중 의 하나로 설정될 수 있습니다.
첫번째 옵션은 기본값으로, 아무 설정도 되어 있지 않을
경우 아파치에서 출력하게 됩니다. 나머지는 ErrorDocument
선언을 사용해서 설정 할 수 있습니다. 이 선언 뒤에는 HTTP response code
와 URL 이 따라오게 됩니다. 아파치는 때로 문제/에러 에
대해서 추가적인 정보를 제공할 수 있습니다.
URL 은 슬래쉬(/) 로 시작하여 로컬(내부) 문서를 참고하거나. 또는 전체 URL을 사용할 수도 있습니다, 무료 호스팅 서비스를 제공하는 업체의 경우 페이지를 찾을 수 없는 잘못된 URL 요청이나 오류에 대해서 자사의 홈페이지로 설정을 하는 등으로 응용할 수 있습니다. 예:
ErrorDocument 500 http://foo.example.com/cgi-bin/tester
ErrorDocument 404 /cgi-bin/bad_urls.pl
ErrorDocument 401 /subscription_info.html
ErrorDocument 403 "Sorry can't allow you access today"
원격(외부) URL 로 설정한 ErrorDocument 를 지정할때(http로
시작), 아파치는 클라이언트에게 같은 서버에 존재하는
문서가 끝날때 까지 리디렉트 될 문서를 찾을 수 있는
위치를 알려주고 있게 됩니다. 이것과 관련된 몇가지가
있는데 중요한 것은 "ErrorDocument 401" 에 대해서는
반드니 내부 문서를 참조하도록 해야 한다는 것입니다.이것은 HTTP basic authentication
scheme의 본질 때문입니다.
Prior to version 2.0, messages were indicated by prefixing them with a single unmatched double quote character.
See Also: documentation of customizable responses.
syslog[:facility]
ErrorLog logs/error_log (Unix)ErrorLog logs/error.log
(Windows and OS/2)에러 로그 를 기록하는 파일의 이름을 지정하는 선언입니다. 절대경로를 쓰지 않는 경우에는 ServerRoot 의 상대적인 경로 에 있는 파일로 간주 됩니다. , 만약 파일이름에 pipe (|) 로 시작하는 경우 에러 로그를 spawn 에서 처리하도록 명령하는 것으로 간주 됩니다.
Apache 1.3 and above:
Using syslog instead of a filename enables logging via syslogd(8)
if the system supports it. The default is to use syslog facility
local7, but you can override this by using the
syslog:facility syntax where facility can be
one of the names usually documented in syslog(1).
SECURITY: See the security tips document for details on why your security could be compromised if the directory where logfiles are stored is writable by anyone other than the user that starts the server.
See also: LogLevel
The <Files> directive provides for access control by
filename. It is comparable to the <Directory> directive and
<Location> directives. It
should be matched with a </Files> directive. The
directives given within this section will be applied to any
object with a basename (last component of filename) matching
the specified filename.
<Files> sections are processed in the
order they appear in the configuration file, after the
<Directory> sections and .htaccess files are
read, but before <Location> sections. Note that
<Files> can be nested inside <Directory>
sections to restrict the portion of the filesystem they
apply to.
The filename argument should include a filename, or a
wild-card string, where `?' matches any single character, and `*' matches any
sequences of characters. Extended regular expressions can also be used,
with the addition of
the ~ character. For example:
<Files ~ "\.(gif|jpe?g|png)$">would match most common Internet graphics formats. In Apache 1.3 and later, <FilesMatch> is preferred, however.
Note that unlike <Directory> and <Location> sections,
<Files> sections can be used inside .htaccess
files. This allows users to control access to their own files, at a
file-by-file level.
See also: How Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is received
The <FilesMatch> directive provides for access control by filename, just as the <Files> directive does. However, it accepts a regular expression. For example:
<FilesMatch "\.(gif|jpe?g|png)$">
would match most common Internet graphics formats.
See also: How Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is receivedGroup #-1The 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:
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 offdouble available only in
Apache
1.3 and above.on prior to
Apache 1.3.
This directive enables DNS lookups so that host names can be logged (and
passed to CGIs/SSIs in REMOTE_HOST).
The value double refers to doing double-reverse DNS.
That is, after a reverse lookup is performed, a forward lookup is then
performed on that result. At least one of the ip addresses in the forward
lookup must match the original address. (In "tcpwrappers" terminology
this is called PARANOID.)
Regardless of the setting, when mod_access
is used for controlling access by hostname, a double reverse lookup
will be performed. This is necessary for security. Note that the
result of this double-reverse isn't generally available unless
you set HostnameLookups double. For example, if only
HostnameLookups on and a request is made to an object that
is protected by hostname restrictions, regardless of whether the
double-reverse fails or not, CGIs will still be passed the single-reverse
result in REMOTE_HOST.
The default for this directive was previously on in
versions of Apache prior to 1.3. It was changed to off
in order to save the network traffic for those sites that don't truly
need the reverse lookups done. It is also better for the end users
because they don't have to suffer the extra latency that a lookup
entails.
Heavily loaded sites should leave this directive off, since DNS
lookups can take considerable amounts of time. The utility logresolve,
provided in the /support directory, can be used to look up host names
from logged IP addresses offline.
IdentityCheck off
This directive enables RFC1413-compliant logging of the remote user name
for each connection, where the client machine runs identd or something similar.
This information is logged in the access log. Boolean is either
on or off.
The information should not be trusted in any way except for rudimentary usage tracking.
Note that this can cause serious latency problems accessing your server since every request requires one of these lookups to be performed. When firewalls are involved each lookup might possibly fail and add 30 seconds of latency to each hit. So in general this is not very useful on public servers accessible from the Internet.
The <IfDefine test>...</IfDefine> section is used to mark directives that are conditional. The directives within an IfDefine section are only processed if the test is true. If test is false, everything between the start and end markers is ignored.
The test in the <IfDefine> section directive can be one of two forms:
!parameter-name
In the former case, the directives between the start and end markers are only processed if the parameter named parameter-name is defined. The second format reverses the test, and only processes the directives if parameter-name is not defined.
The parameter-name argument is a define as given on the
httpd command line via -Dparameter-, at the
time the server was started.
<IfDefine> sections are nest-able, which can be used to implement simple multiple-parameter tests. Example:
$ httpd -DReverseProxy ... # httpd.conf <IfDefine ReverseProxy> LoadModule rewrite_module libexec/mod_rewrite.so LoadModule proxy_module libexec/libproxy.so </IfDefine>
The <IfModule test>...</IfModule> section is used to mark directives that are conditional. The directives within an IfModule section are only processed if the test is true. If test is false, everything between the start and end markers is ignored.
The test in the <IfModule> section directive can be one of two forms:
In the former case, the directives between the start and end markers are only processed if the module named module name is compiled in to Apache. The second format reverses the test, and only processes the directives if module name is not compiled in.
The module name argument is a module name as given as the file
name of the module, at the time it was compiled. For example,
mod_rewrite.c.
<IfModule> sections are nest-able, which can be used to implement simple multiple-module tests.
이 선언은 C/C++ 과 같은 언어 에서 처럼 서버설정파일 안으로 다른 설정 파일을 포함할 수 있도록 하는 선언 입니다.
KeepAlive 5KeepAlive On이 선언은 Keep-Alive 지원을 가능하게 하는 선언 입니다..
Apache 1.1: Set max-requests
to the maximum number of requests you want Apache to entertain per
request. A limit is imposed to prevent a client from hogging your
server resources. Set this to 0 to disable support.
Apache 1.2 and later: Set to "On" to enable persistent connections, "Off" to disable. See also the MaxKeepAliveRequests directive.
KeepAliveTimeout 15
이 선언은 몇 초 동안 커넥션을 닫기 전에 하위 요청을
기다릴 것인지에 대한 선언 입니다. 한번 요청이 받아 들여
지면 Timeout 선언에서 지정된
시간제한 값이 적용됩니다.
보통 액서스 제어는 모든 액서스
방법(method )에 대하여 적용시킵니다. 이런
일반적인 경우에는
<limit> 섹션에서 액서스 제어 선언을 할
필요가 없습니다.
<Limit> 선언의 목적은 지정된(nominated) HTTP methods 를 제한하기 위한 것입니다. <Limit> 으로 둘러쌓인 해당 methods 들은 아무런 효과를 갖지 못합니다. 다음의 예는 POST, PUT, 그리고 DELETE 라는 메써드에 대해서 valid-user 에게만 허용하며, 다른 메써드들은 보호되지 않은 채로 남겨져 있게 됩니다.
메써드 이름 목록 : GET, POST, PUT, DELETE, CONNECT, OPTIONS, TRACE, PATCH, PROPFIND, PROPPATCH, MKCOL, COPY, MOVE, LOCK, and UNLOCK. Method name 은 대소문자를 구분합니다. If 만약 GET 이 사용되었다면 또한 HEAD requests 를 제한 합니다.
<Limit POST PUT DELETE>
require valid-user
</Limit>
<LimitExcept> and </LimitExcept> are used to enclose a group of access control directives which will then apply to any HTTP access method not listed in the arguments; i.e., it is the opposite of a <Limit> section and can be used to control both standard and nonstandard/unrecognized methods. See the documentation for <Limit> for more details.
LimitRequestBody 0
Number is a long integer from 0 (meaning unlimited) to 2147483647
(2GB). The default value is defined by the compile-time constant
DEFAULT_LIMIT_REQUEST_BODY (0 as distributed).
The LimitRequestBody directive allows the user to set a limit on the allowed size of an HTTP request message body within the context in which the directive is given (server, per-directory, per-file or per-location). If the client request exceeds that limit, the server will return an error response instead of servicing the request. The size of a normal request message body will vary greatly depending on the nature of the resource and the methods allowed on that resource. CGI scripts typically use the message body for passing form information to the server. Implementations of the PUT method will require a value at least as large as any representation that the server wishes to accept for that resource.
This directive gives the server administrator greater control over abnormal client request behavior, which may be useful for avoiding some forms of denial-of-service attacks.
LimitRequestFields 100
Number is an integer from 0 (meaning unlimited) to 32767.
The default value is defined by the compile-time constant
DEFAULT_LIMIT_REQUEST_FIELDS (100 as distributed).
The LimitRequestFields directive allows the server administrator to modify the limit on the number of request header fields allowed in an HTTP request. A server needs this value to be larger than the number of fields that a normal client request might include. The number of request header fields used by a client rarely exceeds 20, but this may vary among different client implementations, often depending upon the extent to which a user has configured their browser to support detailed content negotiation. Optional HTTP extensions are often expressed using request header fields.
This directive gives the server administrator greater control over abnormal client request behavior, which may be useful for avoiding some forms of denial-of-service attacks. The value should be increased if normal clients see an error response from the server that indicates too many fields were sent in the request.
LimitRequestFieldsize 8190
Number is an integer size in bytes from 0 to the value of the
compile-time constant DEFAULT_LIMIT_REQUEST_FIELDSIZE
(8190 as distributed).
The LimitRequestFieldsize directive allows the server administrator to reduce the limit on the allowed size of an HTTP request header field below the normal input buffer size compiled with the server. A server needs this value to be large enough to hold any one header field from a normal client request. The size of a normal request header field will vary greatly among different client implementations, often depending upon the extent to which a user has configured their browser to support detailed content negotiation.
This directive gives the server administrator greater control over abnormal client request behavior, which may be useful for avoiding some forms of denial-of-service attacks. Under normal conditions, the value should not be changed from the default.
LimitRequestLine 8190
Number is an integer size in bytes from 0 to the value of the
compile-time constant DEFAULT_LIMIT_REQUEST_LINE
(8190 as distributed).
The LimitRequestLine directive allows the server administrator to reduce the limit on the allowed size of a client's HTTP request-line below the normal input buffer size compiled with the server. Since the request-line consists of the HTTP method, URI, and protocol version, the LimitRequestLine directive places a restriction on the length of a request-URI allowed for a request on the server. A server needs this value to be large enough to hold any of its resource names, including any information that might be passed in the query part of a GET request.
This directive gives the server administrator greater control over abnormal client request behavior, which may be useful for avoiding some forms of denial-of-service attacks. Under normal conditions, the value should not be changed from the default.
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.
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 8000To 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 511The 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.
The <Location> 선언은 URL 에 대한 액서스를
제어 합니다. 이것은 <Directory> 선언과 유사합니다. 그리고 </Location>
directive(선언) 으로 종결시킵니다. <Location>
섹션은 설정파일에서 쓰이며,
<Directory> sections 과 .htaccess files 을 읽어 들이고,
<Files> 섹션을 처리하고 난 다음에 수행됩니다.
URL 은 파일시스템과 전혀 상관이 없습니다. 이것은 <Location> 연산이 완전히 파일시스템의 외부에서 이루어 진다는 것을 강조합니다.
모든 요청의 기원(non-proxy)에서, URL은 /path/
로 부터 매치가 됩니다. 그리고 어떤 http://servername
접두사(prefix)를 쓸 수는 없습니다. 프락시 요청에 대해서 URL
은 scheme://servername/path 와 같은 형식으로
매치시킬수 있으며 반드시 prefix(접두사)를 포함해야 합니다.
URL 에는 와이들카드 문자를 사용할 수 있습니다. ? 는 하나의 문자에 , * 는 하나이상의 문자와 매치 됩니다.
Apache 1.2 and above: ~ 를 사용해서 정규 표현식으로 확장 해서 사용할 수 있습니다. 예를들면,
<Location ~ "/(extra|special)/data">
이것은 "/extra/data" 또는 "/special/data" 이라는 URL과
매치 됩니다. Apache 1.3 이상에서의 정규표현식을
사용할때는 <LocationMatch>
선언을 사용할 수 있습니다.(
<Location>의 정규표현 버전.)
The Location functionality is especially useful when
combined with the SetHandler directive. For example,
to enable status requests, but allow them only
from browsers at foo.com, you might use:
Location
기능은 특별히 SetHandler 선언과 같이
사용할때 유용합니다. 예를 들면 status 요청에 대한 예를
들면, foo.com 에서의 브라우징에 대해서만 허용하려고
한다면, 다음과 같이 설정할 것입니다.
<Location /status>
SetHandler server-status
order deny,allow
deny from all
allow from .foo.com
</Location>
Apache 1.3 이상에서 / (슬래쉬) 에 대한 주의: The slash
character has special
meaning depending on where in a URL it appears. People may be used
to its behaviour in the filesystem where multiple adjacent slashes are
frequently collapsed to a single slash (i.e., /home///foo
is the same as /home/foo). In URL-space this is not
necessarily true. The <LocationMatch> directive
and the regex version of <Location> require you
to explicitly specify multiple slashes if that is your intention.
For example, <LocationMatch ^/abc> would match the
request URL /abc but not the request URL //abc.
The (non-regex) <Location> directive behaves
similarly when used for proxy requests. But when (non-regex)
<Location> is used for non-proxy requests it will
implicitly match multiple slashes with a single slash. For example,
if you specify <Location /abc/def> and the request
is to /abc//def then it will match.
See also: How Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is received
<LocationMatch> 선언은 URL 에 의한 액서스 제어를 제공하며, <Location>과 동일한 박식 입니다. 어째든 이 선언은 단순한 문자열 대신 정규표현(regex) 을 사용해서 선언합니다. 예를 들면:
<LocationMatch "/(extra|special)/data">
"/extra/data" 이나 "/special/data" 에 매칭 됩니다.
See also: How Directory, Location and Files sections work for an explanation of how these different sections are combined when a request is receivedLockFile logs/accept.lock
The LockFile directive sets the path to the lockfile used when
Apache is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be
left at its default value. The main reason for changing it is if
the logs directory is NFS mounted, since the lockfile
must be stored on a local disk. The PID of the main
server process is automatically appended to the filename.
SECURITY: It is best to avoid putting this file in a
world writable directory such as /var/tmp because someone
could create a denial of service attack and prevent the server from
starting by creating a lockfile with the same name as the one the
server will try to create.
LogLevel errorLogLevel adjusts the verbosity of the messages recorded in the error logs (see ErrorLog directive). The following levels are available, in order of decreasing significance:
| Level | Description |
|---|---|
| Example | |
emerg
| Emergencies - system is unusable. |
| "Child cannot open lock file. Exiting" | |
alert
| Action must be taken immediately. |
| "getpwuid: couldn't determine user name from uid" | |
crit
| Critical Conditions. |
| "socket: Failed to get a socket, exiting child" | |
error
| Error conditions. |
| "Premature end of script headers" | |
warn
| Warning conditions. |
| "child process 1234 did not exit, sending another SIGHUP" | |
notice
| Normal but significant condition. |
| "httpd: caught SIGBUS, attempting to dump core in ..." | |
info
| Informational. |
| "Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..." | |
debug
| Debug-level messages |
| "Opening config file ..." |
When a particular level is specified, messages from all other levels
of higher significance will be reported as well. E.g., when
LogLevel info is specified, then messages with log levels of
notice and warn will also be posted.
Using a level of at least crit is recommended.
MaxClients 256
The MaxClients directive sets the limit on the number of simultaneous requests that can be supported; not more than this number of child server processes will be created. To configure more than 256 clients, you must edit the HARD_SERVER_LIMIT entry in httpd.h and recompile.
Any connection attempts over the MaxClients limit will normally be queued, up to a number based on the ListenBacklog directive. Once a child process is freed at the end of a different request, the connection will then be serviced.
MaxKeepAliveRequests 100The MaxKeepAliveRequests directive limits the number of requests
allowed per connection when KeepAlive is
on. If it is set to "0", unlimited requests will be
allowed. We recommend that this setting be kept to a high value for
maximum server performance.
MaxRequestsPerChild 0The MaxRequestsPerChild directive sets the limit on the number of requests that an individual child server process will handle. After MaxRequestsPerChild requests, the child process will die. If MaxRequestsPerChild is 0, then the process will never expire.
Setting MaxRequestsPerChild to a non-zero limit has two beneficial effects:
This directive has no effect on Win32.
NOTE: For KeepAlive requests, only the first request is counted towards this limit. In effect, it changes the behavior to limit the number of connections per child.
MaxSpareServers 10The MaxSpareServers directive sets the desired maximum number of idle child server processes. An idle process is one which is not handling a request. If there are more than MaxSpareServers idle, then the parent process will kill off the excess processes.
Tuning of this parameter should only be necessary on very busy sites. Setting this parameter to a large number is almost always a bad idea.
This directive has no effect when used with the Apache Web server on a Microsoft Windows platform.
See also MinSpareServers and StartServers.
MinSpareServers 5The MinSpareServers directive sets the desired minimum number of idle child server processes. An idle process is one which is not handling a request. If there are fewer than MinSpareServers idle, then the parent process creates new children at a maximum rate of 1 per second.
Tuning of this parameter should only be necessary on very busy sites. Setting this parameter to a large number is almost always a bad idea.
This directive has no effect on Microsoft Windows.
See also MaxSpareServers and StartServers.
The NameVirtualHost directive is a required directive if you want to configure name-based virtual hosts.
Although addr can be hostname it is recommended that you always use an IP address, e.g.
NameVirtualHost 111.22.33.44Note: the "main server" and any _default_ servers will never be served for a request to a NameVirtualHost IP Address (unless for some reason you specify NameVirtualHost but then don't define any VirtualHosts for that address).
Optionally you can specify a port number on which the name-based virtual hosts should be used, e.g.
NameVirtualHost 111.22.33.44:8080이 Options 선언은 각각의 디렉토리의 기능을 제어합니다.
option 을 None,으로 지정하면, 아무기능도
사용할 수 없습니다. 아래는 옵션으로 주어 질수 있는 값들
이며, +/- 를 사용할 수 있고, 중복해서 사용할 수 도
있습니다.
<Directory>
sections 에 대응하는 경로는 바뀌지 않습니다..
Normally, if multiple Options could apply to a directory,
then the most specific one is taken complete; the options are not
merged. However if all the options on the Options
directive are preceded by a + or - symbol, the options are
merged. Any options preceded by a + are added to the options
currently in force, and any options preceded by a - are removed from
the options currently in force.
+/- 기호를 사용하지 않은 예입니다.:
<Directory /web/docs>
Options Indexes FollowSymLinks
</Directory>
<Directory /web/docs/spec>
Options Includes
</Directory>
Includes 기능만 /web/docs/spec
디렉터리에서 지정되었습니다. 어째든 두번째 선언되는
옵션은 다음의 예에서 처럼 +/- 를 사용해야 합니다.:
<Directory /web/docs>
Options Indexes FollowSymLinks
</Directory>
<Directory /web/docs/spec>
Options +Includes -Indexes
</Directory>
FollowSymLinks 와 Includes
기능이 /web/docs/spec directory 에 주어 졌습니다..
Note: Using -IncludesNOEXEC 나
-Includes
의 사용은 불가능 합니다. SSI(server-side includes)는 이전의
셋팅과는 아무런 상관이 없습니다.
아무런 선언이 없는
경우, 기본값인 All 로 셋팅되어 지게
됩니다.
PidFile logs/httpd.pid이 선언은 데몬 프로그램의 프로세스 아이디를 기록해 놓는 파일을 지정하는 것입니다.
The PidFile directive sets the file to which the server records the process id of the daemon. If the filename does not begin with a slash (/) then it is assumed to be relative to the ServerRoot. The PidFile is only used in standalone mode.
It is often useful to be able to send the server a signal, so that it closes and then reopens its ErrorLog and TransferLog, and re-reads its configuration files. This is done by sending a SIGHUP (kill -1) signal to the process id listed in the PidFile.
The PidFile is subject to the same warnings about log file placement and security.
Port 80
Number 는 0 에서 65535 까지의 숫자를 사용할 수
있습니다.; 80 을 기본값으로 갖지만 1024 와 같이 포트번호를
다르게 할 수도 있습니다. c:\windows\services 파일(확장자
없음)을 보면 몇가지 정의된 포트번호가 나열되어 있습니다.
이곳에 정의된 포트번호를 제외하고는 어느 번호라도 사용
가능합니다.
The Port directive has two behaviors, the first of which is necessary for NCSA backwards compatibility (and which is confusing in the context of Apache).
:number then Port has no effect on what address the server
listens at.
SERVER_PORT environment variable (for
CGI and SSI),
and is used when the server must generate a URL that refers to itself
(for example when creating an external redirect to itself). This
behaviour is modified by
UseCanonicalName.
The primary behaviour of Port should be considered to be similar to that of the ServerName directive. The ServerName and Port together specify what you consider to be the canonical address of the server. (See also UseCanonicalName.)
Port 80 is one of Unix's special ports. All ports numbered below 1024 are reserved for system use, i.e., regular (non-root) users cannot make use of them; instead they can only use higher port numbers. To use port 80, you must start the server from the root account. After binding to the port and before accepting requests, Apache will change to a low privileged user as set by the User directive.
If you cannot use port 80, choose any other unused port. Non-root users will have to choose a port number higher than 1023, such as 8000.
SECURITY: if you do start the server as root, be sure not to set User to root. If you run the server as root whilst handling connections, your site may be open to a major security attack.
이 선언은 디렉토리에 접근할 수 있는 인증된 사용자를 선택할 수 있습니다. :
단지 이곳에 지정된 이름을 가진 사용자만이 해당 디렉토리에 접근가능 합니다.
단지 이곳에 지정된 그룹에 속한 사용자만이 해당 디렉토리에 접근 가능합니다..
타당한 사용자만 해당 디렉토리에 접근 가능합니다.
Require 은 반드시 must be accompanied by AuthName 과 AuthType 선언을 동반해야 합니다., 그리고 AuthUserFile 과 AuthGroupFile 과 같은 선언은(사용자와 사용자 그룹을 정의) 정확하게 작동하는 순서대로 선언 합니다. 예를 들면:
AuthType Basic
AuthName "Restricted Directory"
AuthUserFile /web/users
AuthGroupFile /web/groups
require group admin
require statement into a <Limit> section
See also Satisfy and mod_access.
ResourceConfig conf/srm.confThe server will read this file for more directives after reading the httpd.conf file. Filename is relative to the ServerRoot. This feature can be disabled using:
ResourceConfig /dev/nullSee also AccessConfig.
Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all processes and the second parameter sets the maximum resource limit. Either parameter can be a number, or max to indicate to the server that the limit should be set to the maximum allowed by the operating system configuration. Raising the maximum resource limit requires that the server is running as root, or in the initial startup phase.
This applies to processes forked off from Apache children servicing requests, not the Apache children themselves. This includes CGI scripts and SSI exec commands, but not any processes forked off from the Apache parent such as piped logs.
CPU resource limits are expressed in seconds per process.
See also RLimitMEM or RLimitNPROC.
Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all processes and the second parameter sets the maximum resource limit. Either parameter can be a number, or max to indicate to the server that the limit should be set to the maximum allowed by the operating system configuration. Raising the maximum resource limit requires that the server is running as root, or in the initial startup phase.
This applies to processes forked off from Apache children servicing requests, not the Apache children themselves. This includes CGI scripts and SSI exec commands, but not any processes forked off from the Apache parent such as piped logs.
Memory resource limits are expressed in bytes per process.
See also RLimitCPU or RLimitNPROC.
Takes 1 or 2 parameters. The first parameter sets the soft resource limit for all processes and the second parameter sets the maximum resource limit. Either parameter can be a number, or max to indicate to the server that the limit should be set to the maximum allowed by the operating system configuration. Raising the maximum resource limit requires that the server is running as root, or in the initial startup phase.
This applies to processes forked off from Apache children servicing requests, not the Apache children themselves. This includes CGI scripts and SSI exec commands, but not any processes forked off from the Apache parent such as piped logs.
Process limits control the number of processes per user.
Note: If CGI processes are not running under userids other than the web server userid, this directive will limit the number of processes that the server itself can create. Evidence of this situation will be indicated by cannot fork messages in the error_log.
See also RLimitMEM or RLimitCPU.
Access policy if both allow and require used. The parameter can be either 'all' or 'any'. This directive is only useful if access to a particular area is being restricted by both username/password and client host address. In this case the default behavior ("all") is to require that the client passes the address access restriction and enters a valid username and password. With the "any" option the client will be granted access if they either pass the host restriction or enter a valid username and password. This can be used to password restrict an area, but to let clients from particular addresses in without prompting for a password.
See also require and mod_access.
ScoreBoardFile logs/apache_status
The ScoreBoardFile directive is required on some architectures to place a file that the server will use to communicate between its children and the parent. The easiest way to find out if your architecture requires a scoreboard file is to run Apache and see if it creates the file named by the directive. If your architecture requires it then you must ensure that this file is not used at the same time by more than one invocation of Apache.
If you have to use a ScoreBoardFile then you may see improved speed by placing it on a RAM disk. But be careful that you heed the same warnings about log file placement and security.
Apache 1.2 and above:
Linux 1.x users might be able to add
-DHAVE_SHMGET -DUSE_SHMGET_SCOREBOARD to
the EXTRA_CFLAGS in your Configuration. This
might work with some 1.x installations, but won't work with all of
them. (Prior to 1.3b4, HAVE_SHMGET would have sufficed.)
SVR4 users should consider adding
-DHAVE_SHMGET -DUSE_SHMGET_SCOREBOARD to the
EXTRA_CFLAGS in your Configuration. This
is believed to work, but we were unable to test it in time for 1.2
release. (Prior to 1.3b4, HAVE_SHMGET would have sufficed.)
See Also: Stopping and Restarting Apache
ScriptInterpreterSource script
This directive is used to control how Apache 1.3.5 and later finds the interpreter used to run CGI scripts. The default technique is to use the interpreter pointed to by the #! line in the script. Setting ScriptInterpreterSource registry will cause the Windows Registry to be searched using the script file extension (e.g., .pl) as a search key.
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)
The ServerAdmin sets the e-mail address that the server includes in any error messages it returns to the client.
It may be worth setting up a dedicated address for this, e.g.
ServerAdmin www-admin@foo.bar.comThe ServerAlias directive sets the alternate names for a host, for use with name-based virtual hosts.
See also: Apache Virtual Host documentation
The ServerName directive sets the hostname of the server; this is used when creating redirection URLs. If it is not specified, then the server attempts to deduce it from its own IP address; however this may not work reliably, or may not return the preferred hostname. For example:
ServerName www.example.comsimple.example.com.
If you are using name-based
virtual hosts, the ServerName inside a
<VirtualHost>
section specifies what hostname must appear in the request's
Host: header to match this virtual host.
See Also:
DNS Issues
Apache virtual host documentation
UseCanonicalName
NameVirtualHost
ServerAlias
The ServerPath directive sets the legacy URL pathname for a host, for use with name-based virtual hosts.
See also: Apache Virtual Host documentation
ServerRoot /usr/local/apache
The ServerRoot directive sets the directory in which the server lives.
Typically it will contain the subdirectories conf/ and
logs/. Relative paths for other configuration files are taken
as relative to this directory.
See also the -d option to httpd.
See also the security tips for information on how to properly set permissions on the ServerRoot.
ServerSignature Off
The ServerSignature directive allows the configuration of a trailing
footer line under server-generated documents (error messages,
mod_proxy ftp directory listings, mod_info output, ...). The reason
why you would want to enable such a footer line is that in a chain
of proxies, the user often has no possibility to tell which of the
chained servers actually produced a returned error message.
The Off setting, which is the default, suppresses the
error line (and is therefore compatible with the behavior of
Apache-1.2 and below). The On setting simply adds a
line with the server version number and ServerName of the serving virtual host, and
the EMail setting additionally creates a "mailto:"
reference to the ServerAdmin of the
referenced document.
ServerTokens FullProductOnly keyword is
only available in versions later than 1.3.12
This directive controls whether Server response header field which is sent back to clients includes a description of the generic OS-type of the server as well as information about compiled-in modules.
ServerTokens Prod[uctOnly]
ServerTokens Min[imal]
ServerTokens OS
ServerTokens Full (or not specified)
This setting applies to the entire server, and cannot be enabled or disabled on a virtualhost-by-virtualhost basis.
ServerType standaloneThe ServerType directive sets how the server is executed by the system. Type is one of
/etc/inetd.conf
/etc/rc.local or
/etc/rc3.d/....)
Standalone is the most common setting for ServerType since it is far more efficient. The server is started once, and services all subsequent connections. If you intend running Apache to serve a busy site, standalone will probably be your only option.
StartServers 5The StartServers directive sets the number of child server processes created on startup. As the number of processes is dynamically controlled depending on the load, there is usually little reason to adjust this parameter.
When running under Microsoft Windows, this directive has no effect. There is always one child which handles all requests. Within the child requests are handled by separate threads. The ThreadsPerChild directive controls the maximum number of child threads handling requests, which will have a similar effect to the setting of StartServers on Unix.
See also MinSpareServers and MaxSpareServers.
ThreadsPerChild 50This directive tells the server how many threads it should use. This is the maximum number of connections the server can handle at once; be sure and set this number high enough for your site if you get a lot of hits.
This directive has no effect on Unix systems. Unix users should look at StartServers and MaxRequestsPerChild.
ThreadStackSize 65536This directive tells the server what stack size to use for each of the running threads. If you ever get a stack overflow you will need to bump this number to a higher setting.
This directive has no effect on other systems.
TimeOut 300The TimeOut directive currently defines the amount of time Apache will wait for three things:
UseCanonicalName on
In many situations Apache has to construct a self-referential
URL. That is, a URL which refers back to the same server.
With UseCanonicalName on (and in all versions prior to
1.3) Apache will use the ServerName and Port directives to construct a canonical name for the
server. This name is used in all self-referential URLs, and for the
values of SERVER_NAME and SERVER_PORT in CGIs.
With UseCanonicalName off Apache will form
self-referential URLs using the hostname and port supplied
by the client if any are supplied (otherwise it will use the
canonical name). These values are the same that are used to
implement name based virtual
hosts, and are available with the same clients. The CGI variables
SERVER_NAME and SERVER_PORT will be constructed
from the client supplied values as well.
An example where this may be useful is on an intranet server where
you have users connecting to the machine using short names such as
www. You'll notice that if the users type a shortname,
and a URL which is a directory, such as http://www/splat,
without the trailing slash then Apache will redirect them to
http://www.domain.com/splat/. If you have authentication
enabled, this will cause the user to have to reauthenticate twice (once
for www and once again for www.domain.com).
But if UseCanonicalName is set off, then Apache will redirect
to http://www/splat/.
There is a third option, UseCanonicalName DNS, which
is intended for use with mass IP-based virtual hosting to support
ancient clients that do not provide a Host: header. With
this option Apache does a reverse DNS lookup on the server IP address
that the client connected to in order to work out self-referential URLs.
Warning: if CGIs make assumptions about the values of
SERVER_NAME they may be broken by this option. The client
is essentially free to give whatever value they want as a hostname.
But if the CGI is only using SERVER_NAME to construct
self-referential URLs then it should be just fine.
See also: ServerName, Port
User #-1The 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:
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> and </VirtualHost> are used to enclose a group of directives which will apply only to a particular virtual host. Any directive which is allowed in a virtual host context may be used. When the server receives a request for a document on a particular virtual host, it uses the configuration directives enclosed in the <VirtualHost> section. Addr can be
<VirtualHost 10.1.2.3>
ServerAdmin webmaster@host.foo.com
DocumentRoot /www/docs/host.foo.com
ServerName host.foo.com
ErrorLog logs/host.foo.com-error_log
TransferLog logs/host.foo.com-access_log
</VirtualHost>
Each VirtualHost must correspond to a different IP address, different port
number or a
different host name for the server, in the latter case the server
machine must be configured to accept IP packets for multiple
addresses. (If the machine does not have multiple network interfaces,
then this can be accomplished with the ifconfig alias
command (if your OS supports it), or with kernel patches like VIF (for SunOS(TM) 4.1.x)).
The special name _default_ can be specified in which case
this virtual host will match any IP address that is not explicitly listed
in another virtual host. In the absence of any _default_ virtual host
the "main" server config, consisting of all those definitions outside
any VirtualHost section, is used when no match occurs.
You can specify a :port to change the port that is matched.
If unspecified then it defaults to the same port as the most recent
Port statement of the main server. You
may also specify :* to match all ports on that address.
(This is recommended when used with _default_.)
SECURITY: See the security tips document for details on why your security could be compromised if the directory where logfiles are stored is writable by anyone other than the user that starts the server.
NOTE: The use of <VirtualHost> does not affect what addresses Apache listens on. You may need to ensure that Apache is listening on the correct addresses using either BindAddress or Listen.
See also:
Apache Virtual Host documentation
See also:
Warnings about DNS and Apache
See also:
Setting which addresses and ports Apache uses
See also: How Directory,
Location and Files sections work for an explanation of how these
different sections are combined when a request is received
