From 5dff2d61cc1c27747ee398e04d8e02843aabb1f8 Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Tue, 7 May 2024 04:04:06 +0200 Subject: Adding upstream version 2.4.38. Signed-off-by: Daniel Baumann --- docs/manual/platform/ebcdic.html | 9 + docs/manual/platform/ebcdic.html.en | 616 +++++++++++++++++ docs/manual/platform/ebcdic.html.ko.euc-kr | 585 +++++++++++++++++ docs/manual/platform/index.html | 17 + docs/manual/platform/index.html.en | 124 ++++ docs/manual/platform/index.html.fr.utf8 | 130 ++++ docs/manual/platform/index.html.ko.euc-kr | 109 ++++ docs/manual/platform/index.html.zh-cn.utf8 | 103 +++ docs/manual/platform/netware.html | 13 + docs/manual/platform/netware.html.en | 693 ++++++++++++++++++++ docs/manual/platform/netware.html.fr.utf8 | 763 ++++++++++++++++++++++ docs/manual/platform/netware.html.ko.euc-kr | 609 +++++++++++++++++ docs/manual/platform/perf-hp.html | 13 + docs/manual/platform/perf-hp.html.en | 131 ++++ docs/manual/platform/perf-hp.html.fr.utf8 | 143 ++++ docs/manual/platform/perf-hp.html.ko.euc-kr | 128 ++++ docs/manual/platform/rpm.html | 9 + docs/manual/platform/rpm.html.en | 248 +++++++ docs/manual/platform/rpm.html.fr.utf8 | 264 ++++++++ docs/manual/platform/win_compiling.html | 13 + docs/manual/platform/win_compiling.html.en | 517 +++++++++++++++ docs/manual/platform/win_compiling.html.fr.utf8 | 603 +++++++++++++++++ docs/manual/platform/win_compiling.html.ko.euc-kr | 448 +++++++++++++ docs/manual/platform/windows.html | 13 + docs/manual/platform/windows.html.en | 664 +++++++++++++++++++ docs/manual/platform/windows.html.fr.utf8 | 718 ++++++++++++++++++++ docs/manual/platform/windows.html.ko.euc-kr | 716 ++++++++++++++++++++ 27 files changed, 8399 insertions(+) create mode 100644 docs/manual/platform/ebcdic.html create mode 100644 docs/manual/platform/ebcdic.html.en create mode 100644 docs/manual/platform/ebcdic.html.ko.euc-kr create mode 100644 docs/manual/platform/index.html create mode 100644 docs/manual/platform/index.html.en create mode 100644 docs/manual/platform/index.html.fr.utf8 create mode 100644 docs/manual/platform/index.html.ko.euc-kr create mode 100644 docs/manual/platform/index.html.zh-cn.utf8 create mode 100644 docs/manual/platform/netware.html create mode 100644 docs/manual/platform/netware.html.en create mode 100644 docs/manual/platform/netware.html.fr.utf8 create mode 100644 docs/manual/platform/netware.html.ko.euc-kr create mode 100644 docs/manual/platform/perf-hp.html create mode 100644 docs/manual/platform/perf-hp.html.en create mode 100644 docs/manual/platform/perf-hp.html.fr.utf8 create mode 100644 docs/manual/platform/perf-hp.html.ko.euc-kr create mode 100644 docs/manual/platform/rpm.html create mode 100644 docs/manual/platform/rpm.html.en create mode 100644 docs/manual/platform/rpm.html.fr.utf8 create mode 100644 docs/manual/platform/win_compiling.html create mode 100644 docs/manual/platform/win_compiling.html.en create mode 100644 docs/manual/platform/win_compiling.html.fr.utf8 create mode 100644 docs/manual/platform/win_compiling.html.ko.euc-kr create mode 100644 docs/manual/platform/windows.html create mode 100644 docs/manual/platform/windows.html.en create mode 100644 docs/manual/platform/windows.html.fr.utf8 create mode 100644 docs/manual/platform/windows.html.ko.euc-kr (limited to 'docs/manual/platform') diff --git a/docs/manual/platform/ebcdic.html b/docs/manual/platform/ebcdic.html new file mode 100644 index 0000000..a48afa8 --- /dev/null +++ b/docs/manual/platform/ebcdic.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: ebcdic.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: ebcdic.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/ebcdic.html.en b/docs/manual/platform/ebcdic.html.en new file mode 100644 index 0000000..d4adede --- /dev/null +++ b/docs/manual/platform/ebcdic.html.en @@ -0,0 +1,616 @@ + + + + + +The Apache EBCDIC Port - Apache HTTP Server Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.4

+
+
<-
+

The Apache EBCDIC Port

+
+

Available Languages:  en  | + ko 

+
+ + +
Warning: This document + has not been updated to take into account changes made in + the 2.0 version of the Apache HTTP Server. Some of the + information may still be relevant, but please use it with care. +
+ +
+ +
top
+
+

Overview of the Apache EBCDIC Port

+ + + +

Version 1.3 of the Apache HTTP Server was the first version + which included a port to a (non-ASCII) mainframe machine which + uses the EBCDIC character set as its native codeset.

+ +

(It is the SIEMENS family of mainframes running the BS2000/OSD + operating system. This mainframe OS nowadays features a + SVR4-derived POSIX subsystem).

+ +

The port was started initially to

+ +
    +
  • prove the feasibility of porting the Apache HTTP server to + this platform
    • + +
  • find a "worthy and capable" successor for the venerable + CERN-3.0 daemon + (which was ported a couple of years ago), and to
    • + +
  • prove that Apache's preforking process model can on this + platform easily outperform the accept-fork-serve model used + by CERN by a factor of 5 or more.
    • +
+ +

This document serves as a rationale to describe some of the + design decisions of the port to this machine.

+ +
top
+
+

Design Goals

+ + + +

One objective of the EBCDIC port was to maintain enough + backwards compatibility with the (EBCDIC) CERN server to make + the transition to the new server attractive and easy. This + required the addition of a configurable method to define + whether a HTML document was stored in ASCII (the only format + accepted by the old server) or in EBCDIC (the native document + format in the POSIX subsystem, and therefore the only realistic + format in which the other POSIX tools like grep or + sed could operate on the documents). The current + solution to this is a "pseudo-MIME-format" which is intercepted + and interpreted by the Apache server (see below). Future versions + might solve the problem by defining an "ebcdic-handler" for all + documents which must be converted.

+ +
top
+
+

Technical Solution

+ + + +

Since all Apache input and output is based upon the BUFF + data type and its methods, the easiest solution was to add the + conversion to the BUFF handling routines. The conversion must + be settable at any time, so a BUFF flag was added which defines + whether a BUFF object has currently enabled conversion or not. + This flag is modified at several points in the HTTP + protocol:

+ +
    +
  • set before a request is received + (because the request and the request header lines are always + in ASCII format)
    • + +
  • set/unset when the request body is + received - depending on the content type of the request body + (because the request body may contain ASCII text or a binary + file)
    • + +
  • set before a reply header is sent + (because the response header lines are always in ASCII + format)
    • + +
  • set/unset when the response body is sent + - depending on the content type of the response body (because + the response body may contain text or a binary file)
    • +
+ +
top
+
+

Porting Notes

+ + + +
    +
  1. +

    The relevant changes in the source are #ifdef'ed + into two categories:

    + +
    +
    #ifdef + CHARSET_EBCDIC
    + +
    +

    Code which is needed for any EBCDIC based machine. + This includes character translations, differences in + contiguity of the two character sets, flags which + indicate which part of the HTTP protocol has to be + converted and which part doesn't etc.

    +
    + +
    #ifdef _OSD_POSIX
    + +
    +

    Code which is needed for the SIEMENS BS2000/OSD + mainframe platform only. This deals with include file + differences and socket implementation topics which are + only required on the BS2000/OSD platform.

    +
    +
    +
    2. + +
  2. +

    The possibility to translate between ASCII and EBCDIC at + the socket level (on BS2000 POSIX, there is a socket option + which supports this) was intentionally not chosen, + because the byte stream at the HTTP protocol level consists + of a mixture of protocol related strings and non-protocol + related raw file data. HTTP protocol strings are always + encoded in ASCII (the GET request, any Header: lines, + the chunking information etc.) whereas the file transfer + parts (i.e., GIF images, CGI output etc.) + should usually be just "passed through" by the server. This + separation between "protocol string" and "raw data" is + reflected in the server code by functions like bgets() + or rvputs() for strings, and functions like + bwrite() for binary data. A global translation + of everything would therefore be inadequate.

    + +

    (In the case of text files of course, provisions must be + made so that EBCDIC documents are always served in + ASCII)

    +
    3. + +
  3. +

    This port therefore features a built-in protocol level + conversion for the server-internal strings (which the + compiler translated to EBCDIC strings) and thus for all + server-generated documents. The hard coded ASCII escapes + \012 and \015 which are ubiquitous + in the server code are an exception: they are already the binary + encoding of the ASCII \n and \r and + must not be converted to ASCII a second time. + This exception is only relevant for server-generated strings; + and external EBCDIC documents are not expected to + contain ASCII newline characters.

    +
    4. + +
  4. +

    By examining the call hierarchy for the BUFF management + routines, I added an "ebcdic/ascii conversion layer" which + would be crossed on every puts/write/get/gets, and a + conversion flag which allowed enabling/disabling the + conversions on-the-fly. Usually, a document crosses this + layer twice from its origin source (a file or CGI output) to + its destination (the requesting client): file -> + Apache, and Apache -> client.

    + +

    The server can now read the header lines of a CGI-script + output in EBCDIC format, and then find out that the remainder + of the script's output is in ASCII (like in the case of the + output of a WWW Counter program: the document body contains a + GIF image). All header processing is done in the native + EBCDIC format; the server then determines, based on the type + of document being served, whether the document body (except + for the chunking information, of course) is in ASCII already + or must be converted from EBCDIC.

    +
    5. + +
  5. +

    For Text documents (MIME types text/plain, text/html + etc.), an implicit translation to ASCII can be + used, or (if the users prefer to store some documents in + raw ASCII form for faster serving, or because the files + reside on a NFS-mounted directory tree) can be served + without conversion.

    + +

    Example:

    + +

    to serve files with the suffix .ahtml as a + raw ASCII text/html document without implicit + conversion (and suffix .ascii as ASCII + text/plain), use the directives:

    + +

    + AddType text/x-ascii-html .ahtml
    + AddType text/x-ascii-plain .ascii +

    + +

    Similarly, any text/foo MIME type can be + served as "raw ASCII" by configuring a MIME type + "text/x-ascii-foo" for it using + AddType.

    +
    6. + +
  6. +

    Non-text documents are always served "binary" without + conversion. This seems to be the most sensible choice for, + .e.g., GIF/ZIP/AU file types. This of course + requires the user to copy them to the mainframe host using + the "rcp -b" binary switch.

    +
    7. + +
  7. +

    Server parsed files are always assumed to be in native + (i.e., EBCDIC) format as used on the machine, and + are converted after processing.

    +
    8. + +
  8. +

    For CGI output, the CGI script determines whether a + conversion is needed or not: by setting the appropriate + Content-Type, text files can be converted, or GIF output can + be passed through unmodified. An example for the latter case + is the wwwcount program which we ported as well.

    +
    9. + +
+ +
top
+
+

Document Storage Notes

+ + + +

Binary Files

+ + + +

All files with a Content-Type: which does not + start with text/ are regarded as binary + files by the server and are not subject to any conversion. + Examples for binary files are GIF images, gzip-compressed files + and the like.

+ +

When exchanging binary files between the mainframe host and + a Unix machine or Windows PC, be sure to use the ftp "binary" + (TYPE I) command, or use the + rcp -b command from the mainframe host (the + -b switch is not supported in unix + rcp's).

+ + + +

Text Documents

+ + + +

The default assumption of the server is that Text Files + (i.e., all files whose Content-Type: + starts with text/) are stored in the native + character set of the host, EBCDIC.

+ + + +

Server Side Included Documents

+ + + +

SSI documents must currently be stored in EBCDIC only. + No provision is made to convert it from ASCII before + processing.

+ + + +
top
+
+

Apache Modules' Status

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ModuleStatusNotes
core+ +
mod_access+ +
mod_actions+ +
mod_alias+ +
mod_asis+ +
mod_auth+ +
mod_authn_anon+ +
mod_authn_dbm?with own libdb.a
mod_authz_dbm?with own libdb.a
mod_autoindex+ +
mod_cern_meta? +
mod_cgi+ +
mod_digest+ +
mod_dir+ +
mod_so-no shared libs
mod_env+ +
mod_example-(test bed only)
mod_expires+ +
mod_headers+ +
mod_imagemap+ +
mod_include+ +
mod_info+ +
mod_log_agent+ +
mod_log_config+ +
mod_log_referer+ +
mod_mime+ +
mod_mime_magic?not ported yet
mod_negotiation+ +
mod_proxy+ +
mod_rewrite+untested
mod_setenvif+ +
mod_speling+ +
mod_status+ +
mod_unique_id+ +
mod_userdir+ +
mod_usertrack?untested
+ +
top
+
+

Third Party Modules' Status

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
ModuleStatusNotes
JK (Formerly mod_jserv) + -JAVA still being ported.
mod_php3+mod_php3 runs fine, with LDAP and GD + and FreeType libraries.
mod_put?untested
mod_session-untested
+ +
+
+

Available Languages:  en  | + ko 

+
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 diff --git a/docs/manual/platform/ebcdic.html.ko.euc-kr b/docs/manual/platform/ebcdic.html.ko.euc-kr new file mode 100644 index 0000000..6e7a0a3 --- /dev/null +++ b/docs/manual/platform/ebcdic.html.ko.euc-kr @@ -0,0 +1,585 @@ + + + + + +아파치 EBCDIC 포팅 - Apache HTTP Server Version 2.4 + + + + + + +
+

모듈 | 지시어들 | FAQ | 용어 | 사이트맵

+

Apache HTTP Server Version 2.4

+
+
<-
+

아파치 EBCDIC 포팅

+
+

가능한 언어:  en  | + ko 

+
+
이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.
+ + +
이 문서는 아파치 웹서버 2.0 버전에서 + 변경된 내용을 담고있지 않다. 아직도 유효한 정보가 있지만, + 주의해서 사용하길 바란다. +
+ +
+ +
top
+
+

아파치 EBCDIC 포팅 개요

+ + + +

아파치 웹서버는 1.3 버전때 처음으로 EBCDIC 문자집합을 + 기본 문자집합으로 사용하는 (비-ASCII) 메인플레임 컴퓨터로 + 포팅되었다.

+ +

(BS2000/OSD + 운영체제를 사용하는 SIEMENS 계열 메인플레임을 말한다. + 이 메인플레임 운영체제에는 현재 SVR4계열의 POSIX 하위시스템이 + 있다).

+ +

포팅은 처음에 다음과 같은 목적에서 시작되었다

+ +
    +
  • 이 플레폼으로도 아파치 + 웹서버를 포팅할 수 있다는 가능성을 보이기위해서
    • + +
  • (몇년 전에 포팅된) 오래된 CERN-3.0 서버를 대체할 + "쓸만하고 유능한" 후계자를 찾기위해
    • + +
  • 이 플레폼에서 아파치의 prefork 프로세스 방식이 CERN의 + accept-fork-serve 방식 보다 5배 이상 성능이 좋음을 + 보이기위해서.
    • +
+ +

이 문서는 포팅시 여러 설계상 결정의 이유를 설명한다.

+ +
top
+
+

설계 목표

+ + + +

EBCDIC 포팅의 목적중 하나는 새로운 서버로 전환을 유도하고 + 쉽게 전환할 수 있도록 가능한 (EBCDIC) CERN 서버와 호환성을 + 유지하는 것이다. 그래서 HTML 문서가 (이전 CERN 서버가 인식하는 + 유일한 형식인) ASCII와 (POSIX 하위시스템의 기본 문서 형식. + 그러므로 grep이나 sed 같은 POSIX + 도구를 사용할 수 있는 현실적인 형식인) EBCDIC 중 어느 형식인지 + 설정할 수 있어야 한다. 현재 해결책은 아파치 서버가 중간에서 + 문서를 가로채서 문서의 형식을 파악하는 "가상 MIME 형식"이다 + (아래 참고). 다음 버전에서는 변환해야할 모든 문서에 + "ebcdic-handler"를 정의하는 방법으로 문제를 해결할 것이다.

+ +
top
+
+

기술적 해결책

+ + + +

아파치가 BUFF 자료형과 메써드를 사용하여 모든 입출력을 + 하므로 가장 쉬운 방법은 BUFF 처리 함수에 변환기능을 추가하는 + 것이다. 언제든지 변환할 수 있어야 하기때문에 BUFF 객체를 + 변환해야 하는지 알려주는 BUFF 표시를 추가했다. 이 표시는 + HTTP 프로토콜의 여러 단계에서 변경될 수 있다:

+ +
    +
  • 요청을 받기 전에 변환 (요청과 요청헤더가 + 항상 ASCII 형식이기 때문에)
    • + +
  • 요청 내용을 받았을때 content type에 따라 + 변환/변환안함 (요청 내용이 ASCII 문자나 + 바이너리 파일인 경우 변환해야 하기때문에)
    • + +
  • 응답헤더를 보내기 전에 변환 (응답헤더는 + 항상 ASCII 형식이기때문에)
    • + +
  • 응답 내용을 보낼때 content type에 따라 + 변환/변환안함 (응답 내용이 문자 파일이거나 + 바이너리 파일이기때문에)
    • +
+ +
top
+
+

포팅에 대해서

+ + + +
    +
  1. +

    소스의 변화는 두가지 #ifdef로 구분할 + 수 있다:

    + +
    +
    #ifdef + CHARSET_EBCDIC
    + +
    +

    모든 EBCDIC기반 컴퓨터에 필요한 코드. 문자변환, + 두 문자집합간의 연속된 문자값 차이, 어떤 HTTP 프로토콜 + 부분이 변환되야 하는지를 알려주는 표시 등.

    +
    + +
    #ifdef _OSD_POSIX
    + +
    +

    SIEMENS BS2000/OSD 메인플레임 플레폼에만 필요한 + 코드. BS2000/OSD 플레폼에만 필요한 헤더파일 차이와 + 소켓 구현 문제를 다룬다.

    +
    +
    +
    2. + +
  2. +

    소켓 수준에서 ASCII와 EBCDIC간 변화는 (BS2000 POSIX에는 + 이 기능을 지원하는 소켓 옵션이 있다) HTTP 프로토콜 수준에서 + 전송되는 자료에 프로토콜관련 문자열과 프로토콜과 무관한 + 일반파일이 섞여있기때문에 의도적으로 사용하지 + 않았다. HTTP 프로토콜 문자열은 (GET + 요청, Header: 줄, 기타 정보 등.) 항상 ASCII + 형식이고, 파일전송 부분은 (즉, GIF 그림, CGI + 출력 등.) 서버가 항상 "변환하지않고 그냥" 보내야 + 한다. 서버 코드는 "프로토콜 문자열"과 "일반 자료"를, + 문자열에는 bgets()나 rvputs(), + 바이너리 자료에는 bgets()나 + rvputs() 함수를 사용하여 구별한다. 그러므로 + 무조건 모든 것을 변환하는 것은 적절하지 않다.

    + +

    (물론 문자파일의 경우 EBCDIC 문서를 항상 ASCII로 + 서비스하도록 준비해야 한다)

    +
    3. + +
  3. +

    그래서 포팅에는 (컴파일러가 EBCDIC 문자열로 변환한) + 서버 내부 문자열과 서버가 생성한 문서를 기본 프로토콜 + 수준에서 변환하는 기능이 있다. 서버 코드에 산재된 ASCII + escape문자 \012와 \015는 예외다: + 이들이 이미 ASCII \n과 \r의 + 바이너리 값이기때문에 ASCII로 두번 변환하면 안된다. + 이 예외는 서버가 생성한 문자열에만 적용된다; 외부 + EBCDIC 문서는 ASCII 줄바꿈문자를 포함하면 안된다.

    +
    4. + +
  4. +

    BUFF 관리함수를 사용하는 방법을 살펴본 후 나는 모든 + puts/write/get/gets가 거치게되는 "ebcdic/ascii 변환 + 계층"을 추가하고, 동적으로 변환유무를 설정할 수 있는 + 변환 표시를 추가했다. 문서가 원본(파일이나 CGI 출력)에서 + 대상(요청한 클라이언트)으로 이동할때 항상 이 계층을 + 두번 지난다: 파일 -> 아파치, 아파치 + -> 클라이언트.

    + +

    서버는 이제 EBCDIC 형식으로 된 CGI 스크립트 출력의 + 헤더줄을 읽고, 나머지 스크립트 출력이 ASCII임을 알아낼 + 수 있다 (WWW 방문자수를 세는 프로그램과 같은 경우: 문서 + 내용은 GIF 그림이다). 기본 EBCDIC 형식으로 모든 헤더를 + 처리한다; 그런 다음 서비스할 문서의 type에 따라 서버는 + 문서 내용이 이미 ASCII인지 혹은 EBCDIC에서 변환을 해야 + 하는지 결정한다.

    +
    5. + +
  5. +

    (MIME type이 text/plain, text/html 등) 내용이 + 일반 문자인 문서를 암묵적으로 ASCII로 변환하거나, (사용자에게 + 빠르게 서비스하기위해 미리 문서를 ASCII 형식으로 저장하였거나 + NFS로 마운트한 디렉토리에 파일이 있는 경우) 변환없이 + 서비스할 수 있다.

    + +

    예:

    + +

    이름이 .ahtml로 끝나는 파일을 암묵적인 + 변환없이 ASCII text/html 문서로 (그리고 + .ascii 확장자는 ASCII + text/plain으로) 서비스하려면 다음 지시어를 + 사용한다:

    + +

    + AddType text/x-ascii-html .ahtml
    + AddType text/x-ascii-plain .ascii +

    + +

    또, text/foo 식의 MIME type을 + AddType "text/x-ascii-foo" + 설정하여 "일반 ASCII"로 서비스할 수 있다.

    +
    6. + +
  6. +

    내용이 일반 문자가 아닌 문서는 변환없이 항상 "바이너리"로 + 서비스한다. 예를 들어, GIF/ZIP/AU 파일형식에 + 가장 적합한 선택이다. 물론 사용자는 "rcp -b" + 바이너리 옵션을 사용하여 파일을 메인플레임 호스트로 + 복사했어야 한다.

    +
    7. + +
  7. +

    서버파싱 파일은 항상 컴퓨터가 사용하는 기본 형식으로 + (즉, EBCDIC) 저장되었다고 가정하고, 처리후에 + 변환한다.

    +
    8. + +
  8. +

    CGI 출력의 경우 CGI 스크립트가 변환이 필요한지 결정한다: + 적절한 Content-Type을 설정하여, 문자파일은 변환하고, + GIF 출력은 변환없이 보낼 수 있다. 우리가 포팅한 wwwcount + 프로그램이 후자의 경우다.

    +
    9. + +
+ +
top
+
+

문서 저장에 대해서

+ + + +

바이너리 파일

+ + + +

서버는 Content-Type:이 text/로 + 시작하는 않는 파일을 바이너리 파일로 간주하여 + 어떤 변환도 하지 않는다. 바이너리 파일에는 GIF 그림, gzip으로 + 압축한 파일 등이 있다.

+ +

메인플레임 호스트와 유닉스 혹은 윈도우즈 PC간에 바이너리 + 파일을 전송할 때는 ftp "binary" (TYPE I) 명령어나 + 메인플레임 호스트에서 (유닉스 rcp는 + -b 옵션을 지원하지 않는다) rcp -b + 명령어를 반드시 사용하라.

+ + + +

문자 문서

+ + + +

기본적으로 서버는 문자파일이 (즉, + Content-Type:이 text/로 시작하는 + 모든 파일) 호스트의 기본 문자집합인 EBCDIC으로 저장되었다고 + 가정한다.

+ + + +

Server Side Include 문서

+ + + +

SSI 문서는 현재 EBCDIC 형식으로만 저장해야 한다. 처리하기 + 전에 ASCII를 변환하지 않는다.

+ + + +
top
+
+

아파치 모듈의 상태

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
모듈상태비고
core+ +
mod_access+ +
mod_actions+ +
mod_alias+ +
mod_asis+ +
mod_auth+ +
mod_auth_anon+ +
mod_auth_dbm?자체 libdb.a를 사용하여
mod_autoindex+ +
mod_cern_meta? +
mod_cgi+ +
mod_digest+ +
mod_dir+ +
mod_so-공유라이브러리가 없음
mod_env+ +
mod_example-(시험 단계)
mod_expires+ +
mod_headers+ +
mod_imagemap+ +
mod_include+ +
mod_info+ +
mod_log_agent+ +
mod_log_config+ +
mod_log_referer+ +
mod_mime+ +
mod_mime_magic?아직 포팅안됨
mod_negotiation+ +
mod_proxy+ +
mod_rewrite+테스트안됨
mod_setenvif+ +
mod_speling+ +
mod_status+ +
mod_unique_id+ +
mod_userdir+ +
mod_usertrack?테스트안됨
+ +
top
+
+

제삼자가 만든 모듈의 상태

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
모듈상태비고
JK (mod_jserv) + -JAVA는 포팅중이다.
mod_php3+mod_php3는 LDAP, GD, FreeType 라이브러리와 + 함께 잘 동작한다.
mod_put?테스트안됨
mod_session-테스트안됨
+ +
+
+

가능한 언어:  en  | + ko 

+
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 diff --git a/docs/manual/platform/index.html b/docs/manual/platform/index.html new file mode 100644 index 0000000..c770297 --- /dev/null +++ b/docs/manual/platform/index.html @@ -0,0 +1,17 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: index.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: index.html.fr.utf8 +Content-Language: fr +Content-type: text/html; charset=UTF-8 + +URI: index.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR + +URI: index.html.zh-cn.utf8 +Content-Language: zh-cn +Content-type: text/html; charset=UTF-8 diff --git a/docs/manual/platform/index.html.en b/docs/manual/platform/index.html.en new file mode 100644 index 0000000..91b250d --- /dev/null +++ b/docs/manual/platform/index.html.en @@ -0,0 +1,124 @@ + + + + + +Platform Specific Notes - Apache HTTP Server Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.4

+
+
<-
+

Platform Specific Notes

+
+

Available Languages:  en  | + fr  | + ko  | + zh-cn 

+
+
+ +
top
+
+

Microsoft Windows

+ + + +
+
Using Apache
+
+

This document explains how to install, configure and run Apache 2.4 + under Microsoft Windows.

+ +

See: Using Apache with Microsoft Windows

+
+
+ +
+
Compiling Apache
+
+

There are many important points before you begin compiling Apache. + This document explain them.

+ +

See: Compiling Apache for Microsoft Windows

+
+
+ +
top
+
+

Unix Systems

+ + + +
+
RPM Based Systems (Redhat / CentOS / Fedora)
+
+

This document explains how to build, install, and run Apache 2.4 + on systems supporting the RPM packaging format.

+ +

See: Using Apache With RPM Based Systems

+
+
+ +
top
+
+

Other Platforms

+ + + +
+
Novell NetWare
+
+

This document explains how to install, configure and run Apache 2.4 + under Novell NetWare 5.1 and above.

+ +

See: Using Apache With Novell NetWare

+
+
+ +
+
EBCDIC
+
+

Version 1.3 of the Apache HTTP Server is the first version which + includes a port to a (non-ASCII) mainframe machine which uses the + EBCDIC character set as its native codeset.

+ +
Warning: This document + has not been updated to take into account changes made in + the 2.4 version of the Apache HTTP Server. Some of the + information may still be relevant, but please use it + with care.
+ +

See: The Apache EBCDIC Port

+
+
+ +
+
+

Available Languages:  en  | + fr  | + ko  | + zh-cn 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/index.html.fr.utf8 b/docs/manual/platform/index.html.fr.utf8 new file mode 100644 index 0000000..330cd50 --- /dev/null +++ b/docs/manual/platform/index.html.fr.utf8 @@ -0,0 +1,130 @@ + + + + + +Notes sp챕cifiques aux diff챕rentes plateformes. - Serveur HTTP Apache Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur HTTP Apache Version 2.4

+
+
<-
+

Notes sp챕cifiques aux diff챕rentes plateformes.

+
+

Langues Disponibles:  en  | + fr  | + ko  | + zh-cn 

+
+
+ +
top
+
+

Microsoft Windows

+ + + +
+
Utilisation d'Apache
+
+

Ce document explique comment installer, configurer et + ex챕cuter Apache 2.4 sous Microsoft Windows.

+ +

Voir : Utilisation d'Apache avec Microsoft Windows

+
+
+ +
+
Compilation d'Apache
+
+

Il y a de nombreux points importants 횪 conna챤tre avant de se + lancer dans la compilation d'Apache. Ce document en donne la + description.

+ +

Voir : Compilation d'Apache pour Microsoft Windows

+
+
+ +
top
+
+

Syst챔mes de type Unix

+ + + +
+
Syst챔mes 횪 base de paquets RPM (Redhat / CentOS / Fedora)
+
+

Ce document explique comment installer, configurer et + ex챕cuter Apache 2.4 sur des syst챔mes qui supportent le format de + paquet RPM.

+ +

Voir : Utilisation d'Apache avec les + syst챔mes 횪 base de paquets RPM

+
+
+ +
top
+
+

Autres plateformes

+ + + +
+
Novell NetWare
+
+

Ce document explique comment installer, configurer et + ex챕cuter Apache 2.4 sous Novell NetWare versions 5.1 et + sup챕rieures.

+ +

Voir : Utilisation d'Apache avec Novell NetWare

+
+
+ +
+
EBCDIC
+
+

La version 1.3 du serveur HTTP Apache est la premi챔re 횪 + avoir 챕t챕 port챕e vers une machine de type mainframe (non-ASCII) + qui utilisait le jeu de caract챔res EBCDIC comme jeu de + caract챔res natif.

+ +
Avertissement :Ce document + n'a pas fait l'objet d'une mise 횪 jour pour int챕grer les + modifications intervenues 횪 partir de la version 2.4 du serveur + HTTP Apache. Certaines des informations qu'il contient sont + toujours pertinentes, mais il est conseill챕 de les utiliser avec + prudence.
+ +

Voir : Le portage d'Apache vers EBCDIC

+
+
+ +
+
+

Langues Disponibles:  en  | + fr  | + ko  | + zh-cn 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/index.html.ko.euc-kr b/docs/manual/platform/index.html.ko.euc-kr new file mode 100644 index 0000000..b777f5c --- /dev/null +++ b/docs/manual/platform/index.html.ko.euc-kr @@ -0,0 +1,109 @@ + + + + + +플래폼별 설명 - Apache HTTP Server Version 2.4 + + + + + + +
+

모듈 | 지시어들 | FAQ | 용어 | 사이트맵

+

Apache HTTP Server Version 2.4

+
+
<-
+

플래폼별 설명

+
+

가능한 언어:  en  | + fr  | + ko  | + zh-cn 

+
+
이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.
+
+ +
top
+
+

Microsoft Windows

+ + + +
+
아파치 사용법
+
+

이 문서는 Microsoft Windows에서 아파치 2.0을 설치, + 설정, 실행하는 방법을 설명한다.

+ +

문서: Microsoft Windows에서 + 아파치 사용법

+
+
+ +
+
아파치 컴파일
+
+

아파치를 컴파일하기 전에 주의할 점이 많다. 이 문서는 + 이점을 설명한다.

+ +

문서: Microsoft Windows용 아파치 컴파일

+
+
+ +
top
+
+

기타 플래폼

+ + + +
+
Novell NetWare
+
+

이 문서는 Novell NetWare 5.1 이상에서 아파치 2.0을 + 설치, 설정, 실행하는 방법을 설명한다.

+ +

문서: Novell NetWare에서 아파치 + 사용하기

+
+
+ +
+
EBCDIC
+
+

아파치 웹서버는 1.3 버전때 처음으로 EBCDIC 문자집합을 + 기본 문자집합으로 사용하는 (비-ASCII) 메인플레임 컴퓨터로 + 포팅되었다.

+ +
경고: 이 문서는 + 아파치 웹서버 2.0 버전에서 변경된 내용을 담고있지 않다. + 아직도 유효한 정보가 있지만, 주의해서 사용하길 바란다.
+ +

문서: 아파치 EBCDIC 포팅

+
+
+ +
+
+

가능한 언어:  en  | + fr  | + ko  | + zh-cn 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/index.html.zh-cn.utf8 b/docs/manual/platform/index.html.zh-cn.utf8 new file mode 100644 index 0000000..b29f33d --- /dev/null +++ b/docs/manual/platform/index.html.zh-cn.utf8 @@ -0,0 +1,103 @@ + + + + + +亮녑룿�쎑�뀽瑥닸삇 - Apache HTTP �쐨�뒦�솳 �뎵�쑍 2.4 + + + + + + +
+

與▼쓼 | �뙁餓� | 躍멱쭅�뿮窯� | �쑐瑥� | 營묊쳶野쇠닼

+

Apache HTTP �쐨�뒦�솳�뎵�쑍 2.4

+
+
<-
+

亮녑룿�쎑�뀽瑥닸삇

+
+

�룾�뵪瑥�鼇�:  en  | + fr  | + ko  | + zh-cn 

+
+
閭ㅷ옐瑥묈룾�꺗瓦뉑쐿��귟쫨雅녻㎗���瓦묊쉪�쎍�뵻竊뚩�룬쁾瑥삭떛�뻼�뎵���
+
+ +
top
+
+

Microsoft Windows

+ + + +
+
鵝욜뵪 Apache
+
+

瓦숂칶�뻼旅ｈ㎗�뇢雅녶쫩鵝뺝쑉 Microsoft Windows 訝�若됭즳竊뚪뀓營�竊뚥빳�룋瓦먫죱 Apache 2.0 ���

+ +

�뢿鰲�: �쑉 Microsoft Windows 訝�鵝욜뵪 Apache

+
+
+ +
+
煐뽬캂 Apache
+
+

瓦숂칶�뻼旅ｈ㎗�뇢雅녺폋瑥� Apache �쉪誤곭궧���

+ +

�뢿鰲�: 訝� Microsoft Windows 煐뽬캂 Apache

+
+
+ +
top
+
+

�끀若껃뭄�룿

+ + + +
+
Novell NetWare
+
+

瓦숂칶�뻼旅ｈ㎗�뇢雅녶쫩鵝뺝쑉 Novell NetWare 5.1 �닑�쎍�뼭�쉪�뎵�쑍訝�竊뚦쫩鵝뺝츎獒낉펽�뀓營�竊뚥빳�룋瓦먫죱 + Apache 2.0 ��� +

+ +

�뢿鰲�: �쑉 Novell NetWare 訝�鵝욜뵪 Apache

+
+
+ +
+
EBCDIC
+
+

餓� Apache HTTP �뎵�쑍 1.3 凉�冶뗦뵱�똻鵝욜뵪 EBCDIC 耶쀧Е�썓鵝쒍맏�렅�뵟耶쀧Е�썓�쉪(�씆 ASCII)訝삥쑛���

+ +
鈺��몜: + 瓦숂칶�뻼旅ｅ컶�쑋若뚦뀲�쎍�뼭竊뚥빳�룏�삝�눎 Apache HTTP �쐨�뒦�솳�뎵�쑍 2.0 + 阿뗥릮�쉪岳��뵻��귝윇雅쎽에�겘�룾�꺗餓띷뿧��귞뵪竊뚥퐜瑥룟컦恙껂슴�뵪若껁��
+ +

�뢿鰲�: Apache 訝� EBCDIC 楹사퍨

+
+
+ +
+
+

�룾�뵪瑥�鼇�:  en  | + fr  | + ko  | + zh-cn 

+
+ \ No newline at end of file diff --git a/docs/manual/platform/netware.html b/docs/manual/platform/netware.html new file mode 100644 index 0000000..988e468 --- /dev/null +++ b/docs/manual/platform/netware.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: netware.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: netware.html.fr.utf8 +Content-Language: fr +Content-type: text/html; charset=UTF-8 + +URI: netware.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/netware.html.en b/docs/manual/platform/netware.html.en new file mode 100644 index 0000000..3862777 --- /dev/null +++ b/docs/manual/platform/netware.html.en @@ -0,0 +1,693 @@ + + + + + +Using Apache With Novell NetWare - Apache HTTP Server Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.4

+
+
<-
+

Using Apache With Novell NetWare

+
+

Available Languages:  en  | + fr  | + ko 

+
+ + +

This document explains how to install, configure and run + Apache 2.0 under Novell NetWare 6.0 and above. If you find any bugs, + or wish to contribute in other ways, please use our + bug reporting + page.

+ +

The bug reporting page and dev-httpd mailing list are + not provided to answer questions about configuration or + running Apache. Before you submit a bug report or request, first + consult this document, the Frequently Asked + Questions page and the other relevant documentation topics. If + you still have a question or problem, post it to the + novell.devsup.webserver newsgroup, where many Apache users are + more than willing to answer new and obscure questions about using + Apache on NetWare.

+ +

Most of this document assumes that you are installing Apache + from a binary distribution. If you want to compile Apache + yourself (possibly to help with development, or to track down + bugs), see the section on Compiling Apache for + NetWare below.

+ +
+ +
top
+
+

Requirements

+ + + +

Apache 2.0 is designed to run on NetWare 6.0 service pack 3 + and above. If you are running a service pack less + than SP3, you must install the latest + NetWare Libraries + for C (LibC).

+ +

NetWare service packs are available here.

+ +

Apache 2.0 for NetWare can also be run in a NetWare 5.1 environment + as long as the latest service pack or the latest version + of the NetWare Libraries + for C (LibC) has been installed . WARNING: Apache 2.0 + for NetWare has not been targeted for or tested in this environment.

+ +
top
+
+

Downloading Apache for NetWare

+ + + +

Information on the latest version of Apache can be found on + the Apache web server at http://www.apache.org/. This + will list the current release, any more recent alpha or + beta-test releases, together with details of mirror web and + anonymous ftp sites. Binary builds of the latest releases of + Apache 2.0 for NetWare can be downloaded from + here.

+ +
top
+
+

Installing Apache for NetWare

+ + + +

There is no Apache install program for NetWare currently. If you + are building Apache 2.0 for NetWare from source, you will need to + copy the files over to the server manually.

+ +

Follow these steps to install Apache on NetWare from the + binary download (assuming you will install to + sys:/apache2):

+ +
    +
  • Unzip the binary download file to the root of the SYS: + volume (may be installed to any volume)
    • + +
  • Edit the httpd.conf file setting ServerRoot and ServerName along with any file path values + to reflect your correct server settings
    • + +
  • Add SYS:/APACHE2 to the search path, for example: +

    SEARCH ADD SYS:\APACHE2

    +
    • + +
+ +

Follow these steps to install Apache on NetWare manually + from your own build source (assuming you will install to + sys:/apache2):

+ +
    +
  • Create a directory called Apache2 on a + NetWare volume
    • + +
  • Copy APACHE2.NLM, APRLIB.NLM + to SYS:/APACHE2
    • + +
  • Create a directory under SYS:/APACHE2 + called BIN
    • + +
  • Copy HTDIGEST.NLM, HTPASSWD.NLM, + HTDBM.NLM, LOGRES.NLM, ROTLOGS.NLM + to SYS:/APACHE2/BIN
    • + +
  • Create a directory under SYS:/APACHE2 + called CONF
    • + +
  • Copy the HTTPD-STD.CONF file to the + SYS:/APACHE2/CONF directory and rename to + HTTPD.CONF
    • + +
  • Copy the MIME.TYPES, CHARSET.CONV and + MAGIC files to SYS:/APACHE2/CONF directory
    • + +
  • Copy all files and subdirectories in \HTTPD-2.0\DOCS\ICONS + to SYS:/APACHE2/ICONS
    • + +
  • Copy all files and subdirectories in \HTTPD-2.0\DOCS\MANUAL + to SYS:/APACHE2/MANUAL
    • + +
  • Copy all files and subdirectories in \HTTPD-2.0\DOCS\ERROR + to SYS:/APACHE2/ERROR
    • + +
  • Copy all files and subdirectories in \HTTPD-2.0\DOCS\DOCROOT + to SYS:/APACHE2/HTDOCS
    • + +
  • Create the directory SYS:/APACHE2/LOGS + on the server
    • + +
  • Create the directory SYS:/APACHE2/CGI-BIN + on the server
    • + +
  • Create the directory SYS:/APACHE2/MODULES + and copy all nlm modules into the modules directory
    • + +
  • Edit the HTTPD.CONF file searching for all + @@Value@@ markers and replacing them with the + appropriate setting
    • + +
  • Add SYS:/APACHE2 to the search path, for example: +

    SEARCH ADD SYS:\APACHE2

    +
    • +
+ +

Apache may be installed to other volumes besides the default SYS volume.

+ +

During the build process, adding the keyword "install" to the makefile command line + will automatically produce a complete distribution package under the subdirectory + DIST. Install Apache by simply copying the distribution that was produced + by the makfiles to the root of a NetWare volume (see: Compiling Apache for + NetWare below).

+ +
top
+
+

Running Apache for NetWare

+ + + +

To start Apache just type apache at the + console. This will load apache in the OS address space. If you + prefer to load Apache in a protected address space you may + specify the address space with the load statement as follows:

+ +

+ load address space = apache2 apache2 +

+ +

This will load Apache into an address space called apache2. + Running multiple instances of Apache concurrently on NetWare is + possible by loading each instance into its own protected + address space.

+ +

After starting Apache, it will be listening to port 80 + (unless you changed the Listen + directive in the configuration files). + To connect to the server and access the default page, + launch a browser and enter the server's name or address. This + should respond with a welcome page, and a link to the Apache + manual. If nothing happens or you get an error, look in the + error_log file in the logs + directory.

+ +

Once your basic installation is working, you should + configure it properly by editing the files in the + conf directory.

+ +

To unload Apache running in the OS address space just type + the following at the console:

+ +

+ unload apache2 +

+ +

or

+ +

+ apache2 shutdown +

+ +

If apache is running in a protected address space specify the + address space in the unload statement:

+ +

+ unload address space = apache2 apache2 +

+ +

When working with Apache it is important to know how it will + find the configuration files. You can specify a configuration + file on the command line in two ways:

+ +
    +
  • -f specifies a path to a particular + configuration file
    • +
+ +

+ apache2 -f "vol:/my server/conf/my.conf" +

+ +

+ apache -f test/test.conf +

+ +

In these cases, the proper ServerRoot + should be set in the configuration file.

+ +

If you don't specify a configuration file name with -f, + Apache will use the file name compiled into the server, usually + conf/httpd.conf. Invoking Apache with the -V + switch will display this value labeled as SERVER_CONFIG_FILE. + Apache will then determine its ServerRoot + by trying the following, in this order:

+ +
    +
  • A ServerRoot directive via a + -C switch.
    • + +
  • The -d switch on the command line.
    • + +
  • Current working directory
    • + +
  • The server root compiled into the server.
    • +
+ +

The server root compiled into the server is usually sys:/apache2. + invoking apache with the -V switch will display this value labeled as + HTTPD_ROOT.

+ +

Apache 2.0 for NetWare includes a set of command line directives that can + be used to modify or display information about the running instance of the + web server. These directives are only available while Apache is running. Each + of these directives must be preceded by the keyword APACHE2.

+ +
+
RESTART
+
Instructs Apache to terminate all running worker + threads as they become idle, reread the configuration file and restart each + worker thread based on the new configuration.
+ +
VERSION
+
Displays version information about the currently + running instance of Apache.
+ +
MODULES
+
Displays a list of loaded modules both built-in + and external.
+ +
DIRECTIVES
+
Displays a list of all available directives.
+ +
SETTINGS
+
Enables or disables the thread status display + on the console. When enabled, the state of each running threads is displayed + on the Apache console screen.
+ +
SHUTDOWN
+
Terminates the running instance of the Apache + web server.
+ +
HELP
+
Describes each of the runtime directives.
+
+ +

By default these directives are issued against the instance of Apache running + in the OS address space. To issue a directive against a specific instance running + in a protected address space, include the -p parameter along with the name of the + address space. For more information type "apache2 Help" on the command line.

+ +
top
+
+

Configuring Apache for NetWare

+ + + +

Apache is configured by reading configuration files usually stored + in the conf directory. These are the same as files used + to configure the Unix version, but there are a few different directives for + Apache on NetWare. See the Apache module + documentation for all the available directives.

+ +

The main differences in Apache for NetWare are:

+ +
    +
  • +

    Because Apache for NetWare is multithreaded, it does not + use a separate process for each request, as Apache does on some Unix + implementations. Instead there are only threads running: a parent + thread, and multiple child or worker threads which handle the requests.

    + +

    Therefore the "process"-management directives are different:

    + +

    MaxConnectionsPerChild - + Like the Unix directive, this controls how many connections + a worker thread will serve before exiting. The recommended default, + MaxConnectionsPerChild 0, causes the thread to continue servicing + request indefinitely. It is recommended on NetWare, unless there is some + specific reason, that this directive always remain set to 0.

    + +

    StartThreads - + This directive tells the server how many threads it should start initially. + The recommended default is StartThreads 50.

    + +

    MinSpareThreads - + This directive instructs the server to spawn additional worker threads + if the number of idle threads ever falls below this value. The recommended + default is MinSpareThreads 10.

    + +

    MaxSpareThreads - + This directive instructs the server to begin terminating worker threads + if the number of idle threads ever exceeds this value. The recommended + default is MaxSpareThreads 100.

    + +

    MaxThreads - + This directive limits the total number of work threads to a maximum + value. The recommended default is ThreadsPerChild 250.

    + +

    ThreadStackSize - + This directive tells the server what size of stack to use + for the individual worker thread. The recommended default + is ThreadStackSize 65536.

    +
    • + +
  • +

    The directives that accept filenames as arguments must use + NetWare filenames instead of Unix names. However, because Apache + uses Unix-style names internally, forward slashes must be used + rather than backslashes. It is recommended that all rooted file paths + begin with a volume name. If omitted, Apache will assume the + SYS: volume which may not be correct.

    +
    • + +
  • +

    Apache for NetWare has the ability to load modules at + runtime, without recompiling the server. If Apache is + compiled normally, it will install a number of optional + modules in the \Apache2\modules directory. + To activate these, or other modules, the LoadModule directive + must be used. For example, to active the status module, use + the following:

    + +

    + LoadModule status_module modules/status.nlm +

    + +

    Information on creating loadable + modules is also available.

    +
    • +
+ +

Additional NetWare specific directives:

+ + + +
    +
  • CGIMapExtension - + This directive maps a CGI file extension to a script interpreter.
    • +
+
    +
  • SecureListen - + Enables SSL encryption for a specified port.
    • +
+
    +
  • NWSSLTrustedCerts - + Adds trusted certificates that are used to create secure connections to proxied servers.
    • +
+
    +
  • NWSSLUpgradeable - + Allow a connection created on the specified address/port to be upgraded to an SSL connection.
    • +
+ + + +
top
+
+

Compiling Apache for NetWare

+ + + +

Compiling Apache requires MetroWerks CodeWarrior 6.x or higher. Once + Apache has been built, it can be installed to the root of any NetWare + volume. The default is the sys:/Apache2 directory.

+ +

Before running the server you must fill out the conf + directory. Copy the file HTTPD-STD.CONF from the distribution + conf directory and rename it to HTTPD.CONF. + Edit the HTTPD.CONF file searching for all @@Value@@ + markers and replacing them with the appropriate setting. Copy over + the conf/magic and conf/mime.types files as well. + Alternatively, a complete distribution can be built by including the keyword + install when invoking the makefiles.

+ +

Requirements:

+ + + +

The following development tools are required to build + Apache 2.0 for NetWare:

+ + + + + +

Building Apache using the NetWare makefiles:

+ + + +
    +
  • Set the environment variable NOVELLLIBC to the + location of the NetWare Libraries for C SDK, for example: +

    Set NOVELLLIBC=c:\novell\ndk\libc

    +
    • + +
  • Set the environment variable METROWERKS to the + location where you installed the Metrowerks CodeWarrior compiler, + for example: +

    Set METROWERKS=C:\Program Files\Metrowerks\CodeWarrior

    + If you installed to the default location C:\Program + Files\Metrowerks\CodeWarrior, you don't need to set this.
    • + +
  • Set the environment variable LDAPSDK to the + location where you installed the LDAP Libraries for C, for example: +

    Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc

    +
    • + +
  • Set the environment variable ZLIBSDK to the + location where you installed the source code for the ZLib Library, + for example: +

    Set ZLIBSDK=D:\NOVELL\zlib

    +
    • + +
  • Set the environment variable PCRESDK to the location + where you installed the source code for the PCRE Library, for example: +

    Set PCRESDK=D:\NOVELL\pcre

    +
    • + +
  • Set the environment variable AP_WORK to the full path of + the httpd source code directory. +

    Set AP_WORK=D:\httpd-2.0.x

    +
    • + +
  • Set the environment variable APR_WORK to the full path of + the apr source code directory. Typically \httpd\srclib\apr + but the APR project can be outside of the httpd directory structure. +

    Set APR_WORK=D:\apr-1.x.x

    +
    • + +
  • Set the environment variable APU_WORK to the full path of + the apr-util source code directory. Typically \httpd\srclib\apr-util + but the APR-UTIL project can be outside of the httpd directory structure. +

    Set APU_WORK=D:\apr-util-1.x.x

    +
    • + +
  • Make sure that the path to the AWK utility and the GNU make utility + (gmake.exe) have been included in the system's + PATH environment variable.
    • + +
  • Download the source code and unzip to an appropriate directory on + your workstation.
    • + +
  • Change directory to \httpd-2.0 and build the prebuild utilities + by running "gmake -f nwgnumakefile prebuild". This target will create + the directory \httpd-2.0\nwprebuild and copy each of the utilities + to this location that are necessary to complete the following build steps. +
    • + +
  • Copy the files \httpd-2.0\nwprebuild\GENCHARS.nlm and + \httpd-2.0\nwprebuild\DFTABLES.nlm to the SYS: volume of a + NetWare server and run them using the following commands: +

    + SYS:\genchars > sys:\test_char.h
    + SYS:\dftables sys:\chartables.c
    +

    +
    • + +
  • Copy the files test_char.h and chartables.c + to the directory \httpd-2.0\os\netware on the build machine.
    • + +
  • Change directory to \httpd-2.0 and build Apache by running + "gmake -f nwgnumakefile". You can create a distribution directory by + adding an install parameter to the command, for example: +

    gmake -f nwgnumakefile install

    +
    • +
+ + + +

Additional make options

+ + + +
    +
  • gmake -f nwgnumakefile

    Builds release versions of all of the + binaries and copies them to a \release destination directory.

    • + +
  • gmake -f nwgnumakefile DEBUG=1

    Builds debug versions of all of the + binaries and copies them to a \debug destination directory.

    • + +
  • gmake -f nwgnumakefile install

    Creates a complete Apache + distribution with binaries, docs and additional support files in a + \dist\Apache2 directory.

    • + +
  • gmake -f nwgnumakefile prebuild

    Builds all of the prebuild utilities + and copies them to the \nwprebuild directory.

    • + +
  • gmake -f nwgnumakefile installdev

    Same as install but also creates a + \lib and \include directory in the destination directory + and copies headers and import files.

    • + +
  • gmake -f nwgnumakefile clean

    Cleans all object files and binaries + from the \release.o or \debug.o build areas depending on whether + DEBUG has been defined.

    • + +
  • gmake -f nwgnumakefile clobber_all

    Same as clean and also deletes + the distribution directory if it exists.

    • +
+ + + +

Additional environment variable options

+ + + +
    +
  • To build all of the experimental modules, set the environment + variable EXPERIMENTAL: +

    Set EXPERIMENTAL=1

    +
    • + +
  • To build Apache using standard BSD style sockets rather than + Winsock, set the environment variable USE_STDSOCKETS: +

    Set USE_STDSOCKETS=1

    +
    • + +
+ + + +

Building mod_ssl for the NetWare platform

+ + + +

By default Apache for NetWare uses the built-in module + mod_nw_ssl to provide SSL services. This module + simply enables the native SSL services implemented in NetWare OS + to handle all encryption for a given port. Alternatively, mod_ssl + can also be used in the same manner as on other platforms.

+ +

Before mod_ssl can be built for the NetWare platform, the OpenSSL + libraries must be provided. This can be done through the following + steps:

+ +
    +
  • Download the recent OpenSSL 0.9.8 release source code from the + OpenSSL Source + page (older 0.9.7 versions need to be patched and are therefore not + recommended).
    • + +
  • Edit the file NetWare/set_env.bat and modify any + tools and utilities paths so that they correspond to your build + environment.
    • + +
  • From the root of the OpenSSL source directory, run the following + scripts: +

    + Netware\set_env netware-libc
    + Netware\build netware-libc +

    + For performance reasons you should enable to build with ASM code. + Download NASM from the SF site. + Then configure OpenSSL to use ASM code: +

    + Netware\build netware-libc nw-nasm enable-mdc2 enable-md5 +

    + Warning: dont use the CodeWarrior Assembler - it produces broken code! +
    • + +
  • Before building Apache, set the environment variable + OSSLSDK to the full path to the root of the openssl + source code directory, and set WITH_MOD_SSL to 1. +

    + Set OSSLSDK=d:\openssl-0.9.8x
    + Set WITH_MOD_SSL=1 +

    • + +
+ + + +
+
+

Available Languages:  en  | + fr  | + ko 

+
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 diff --git a/docs/manual/platform/netware.html.fr.utf8 b/docs/manual/platform/netware.html.fr.utf8 new file mode 100644 index 0000000..4083dc6 --- /dev/null +++ b/docs/manual/platform/netware.html.fr.utf8 @@ -0,0 +1,763 @@ + + + + + +Utilisation d'Apache avec Novell NetWare - Serveur HTTP Apache Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur HTTP Apache Version 2.4

+
+
<-
+

Utilisation d'Apache avec Novell NetWare

+
+

Langues Disponibles:  en  | + fr  | + ko 

+
+ + +

Ce document explique l'installation, la configuration et le + lancement d'Apache 2.0 sous Novell NetWare 6.0 et les versions + ult챕rieures. Si vous trouvez une bogue, ou voulez tout simplement + contribuer de quelque mani챔re que ce soit, utilisez s'il vous plait + notre page des + rapports de bogues.

+ +

La page des rapports de bogues et la liste de diffusion dev-httpd + ne doivent pas 챗tre utilis챕es pour poser des questions 횪 propos de + la configuration ou du lancement d'Apache. Avant de soumettre un + rapport de bogue ou une question, consultez ce document, la FAQ ou tout autre sujet de la + documentation en rapport avec votre probl챔me. Si vous n'avez + toujours pas r챕solu votre probl챔me, postez votre question dans le + newsgroup + novell.devsup.webserver, o첫 de nombreux utilisateurs d'Apache + sont pr챗ts 횪 r챕pondre 횪 toutes les nouvelles et obscures questions 횪 + propos de l'utilisation d'Apache sous Netware.

+ +

Dans la majeure partie de ce document, vous 챗tes sens챕 avoir + install챕 Apache 횪 partir d'une distribution binaire. Si vous voulez + compiler Apache vous-m챗me (par exemple pour aider au d챕veloppement, + ou pour rechercher des bogues), reportez-vous 횪 la section traitant + de la Compilation d'Apache pour Netware + ci-dessous.

+ +
+ +
top
+
+

Pr챕requis

+ + + +

Apache 2.0 n챕cessite NetWare 6.0 service pack 3 et sup챕rieurs + pour fonctionner. Si vous utilisez un service pack ant챕rieur 횪 SP3, + vous devez installer les derni챔res Biblioth챔ques + Netware pour C (LibC).

+ +

Vous trouverez les service packs Netware ici.

+ +

Apache 2.0 pour NetWare peut aussi fonctionner dans un + environnement NetWare 5.1, 횪 partir du moment o첫 le dernier service + pack ou la derni챔re version des Biblioth챔ques + Netware pour C (LibC) ont 챕t챕 install챕s. ATTENTION + : Apache 2.0 pour NetWare n'a pas 챕t챕 test챕 dans cet + environnement car il n'a pas 챕t챕 con챌u pour ce dernier.

+ +
top
+
+

T챕l챕chargement d'Apache pour NetWare

+ + + +

Les informations 횪 propos de la derni챔re version + d'Apache sont disponibles sur le site web d'Apache 횪 http://www.apache.org/. Vous y + trouverez la version courante, des versions alpha ou b챗ta-test plus + r챕centes, ainsi que des sites miroirs et des sites FTP anonymes. Les + distributions binaires des derni챔res versions d'Apache 2.0 pour + NetWare sont disponibles ici.

+ +
top
+
+

Installation d'Apache pour NetWare

+ + + +

Il n'existe pas actuellement de programme d'installation d'Apache + pour Netware. Si vous installez Apache 2.0 pour NetWare 횪 partir des + sources, vous devrez copier les fichiers sur le serveur + manuellement.

+ +

Suivez ces instructions pour installer Apache sous Netware 횪 + partir de la distribution binaire (en supposant que vous effectuez + l'installation dans sys:/apache2) :

+ +
    +
  • D챕compressez le fichier binaire t챕l챕charg챕 횪 la racine du + volume SYS: (vous pouvez cependant l'installer dans + tout volume)
    • + +
  • Editez le fichier httpd.conf et d챕finissez les + directives ServerRoot et + ServerName avec les valeurs + correctes des chemins de fichiers qui correspondent 횪 la + configuration de votre serveur.
    • + +
  • Ajoutez SYS:/APACHE2 au chemin de recherche, par + une commande du style :

    SEARCH ADD + SYS:\APACHE2

    • + +
+ +

Suivez ces instructions pour installer Apache pour Netware + manuellement 횪 partir de votre propre r챕pertoire de sources (en + supposant que vous effectuez l'installation dans + sys:/apache2) :

+ +
    +
  • Cr챕ez un r챕pertoire que vous appellerez Apache2 + dans un volume Netware.
    • + +
  • Copiez APACHE2.NLM, APRLIB.NLM dans + SYS:/APACHE2.
    • + +
  • Cr챕ez un r챕pertoire que vous appellerez BIN dans + SYS:/APACHE2.
    • + +
  • Copiez HTDIGEST.NLM, HTPASSWD.NLM, + HTDBM.NLM, LOGRES.NLM, + ROTLOGS.NLM dans SYS:/APACHE2/BIN.
    • + +
  • Cr챕ez un r챕pertoire que vous appellerez CONF dans + SYS:/APACHE2.
    • + +
  • Copiez le fichier HTTPD-STD.CONF dans le + r챕pertoire SYS:/APACHE2/CONF et renommez-le en + HTTPD.CONF.
    • + +
  • Copiez les fichiers MIME.TYPES, + CHARSET.CONV et MAGIC dans le r챕pertoire + SYS:/APACHE2/CONF.
    • + +
  • Copiez tous les fichiers et sous-r챕pertoires de + \HTTPD-2.0\DOCS\ICONS dans + SYS:/APACHE2/ICONS.
    • + +
  • Copiez tous les fichiers et sous-r챕pertoires de + \HTTPD-2.0\DOCS\MANUAL dans + SYS:/APACHE2/MANUAL.
    • + +
  • Copiez tous les fichiers et sous-r챕pertoires de + \HTTPD-2.0\DOCS\ERROR dans + SYS:/APACHE2/ERROR.
    • + +
  • Copiez tous les fichiers et sous-r챕pertoires de + \HTTPD-2.0\DOCS\DOCROOT dans + SYS:/APACHE2/HTDOCS.
    • + +
  • Cr챕ez le r챕pertoire SYS:/APACHE2/LOGS sur le + serveur.
    • + +
  • Cr챕ez le r챕pertoire SYS:/APACHE2/CGI-BIN sur le + serveur.
    • + +
  • Cr챕ez le r챕pertoire SYS:/APACHE2/MODULES et + copiez tous les modules nlm dans le r챕pertoire + modules.
    • + +
  • Editez le fichier HTTPD.CONF, et recherchez + toutes les marques @@Value@@ afin de les remplacer + par les valeurs appropri챕es.
    • + +
  • Ajoutez SYS:/APACHE2 au chemin de recherche, par + une commande du style :

    SEARCH ADD + SYS:\APACHE2

    .
    • +
+ +

Outre le volume par d챕faut SYS, Apache peut 챗tre + install챕 dans tout autre volume.

+ +

Au cours du processus d'installation, l'ajout du mot-cl챕 + "install" 횪 la ligne de commande du makefile va provoquer la + construction d'une distribution compl챔te sous forme d'un paquetage + dans le sous-r챕pertoire DIST. Vous pouvez simplement + installer Apache en copiant la distribution cr챕챕e pr챕c챕demment 횪 la + racine d'un volume Netware (voir Compilation + d'Apache pour NetWare ci-dessous).

+ +
top
+
+

Ex챕cuter Apache pour NetWare

+ + + +

Pour d챕marrer Apache, tapez simplement apache dans + la console. Ceci aura pour effet de charger Apache dans l'espace + d'adressage du syst챔me d'exploitation. Si vous pr챕f챕rez charger + Apache dans un espace d'adressage prot챕g챕, vous pouvez sp챕cifier cet + espace d'adressage 횪 l'aide de l'instruction de chargement suivante + :

+ +

+ load address space = apache2 apache2 +

+ +

Cette instruction va charger Apache dans un espace d'adressage + appel챕 apache2. Il est possible d'ex챕cuter plusieurs instances + simultan챕es d'Apache sous Netware, en chargeant chacune d'entre + elles dans son propre espace d'adressage prot챕g챕.

+ +

Une fois d챕marr챕, Apache 챕coute le port 80 (횪 moins que vous + n'ayez modifi챕 la directive Listen dans les fichiers de + configuration). Pour vous connecter au serveur et afficher la page + par d챕faut, lancez un navigateur et entrez le nom du serveur ou son + adresse IP. Vous devriez voir une page de bienvenue, et un lien vers + le manuel Apache. Si rien ne se produit, ou si vous obtenez un + message d'erreur, consultez le fichier error_log dans + le r챕pertoire logs.

+ +

Lorsque votre installation de base fonctionne, vous devez la + configurer correctement en 챕ditant les fichiers du r챕pertoire + conf.

+ +

Pour arr챗ter une instance d'Apache s'ex챕cutant dans l'espace + d'adressage du syst챔me d'exploitation, entrez simplement dans la + console :

+ +

+ unload apache2 +

+ +

ou

+ +

+ apache2 shutdown +

+ +

Si Apache s'ex챕cute dans un espace d'adressage prot챕g챕, sp챕cifiez + cet espace d'adressage dans l'instruction d'arr챗t :

+ +

+ unload address space = apache2 apache2 +

+ +

Lorsqu'on travaille avec Apache, il est important de savoir + comment il trouve ses fichiers de configuration. Vous pouvez + sp챕cifier un fichier de configuration sur la ligne de commande de + deux mani챔res :

+ +
    +
  • -f sp챕cifie un chemin vers un fichier de + configuration particulier
    • +
+ +

+ apache2 -f "vol:/nom-serveur/conf/fich-conf.conf" +

+ +

+ apache -f test/test.conf +

+ +

Dans ces cas, la directive ServerRoot doit 챗tre correctement d챕finie + dans le fichier de configuration.

+ +

Si vous ne sp챕cifiez pas de nom de fichier de configuration avec + l'option -f, Apache utilisera le nom de fichier cod챕 en + dur dans le serveur, en g챕n챕ral conf/httpd.conf. + L'invocation d'Apache avec l'option -V indiquera ce nom + comme valeur de l'챕tiquette SERVER_CONFIG_FILE. Apache + va ensuite d챕terminer son ServerRoot en effectuant les tests + suivants, dans cet ordre

+ +
    +
  • Une directive ServerRoot via une option + -C switch.
    • + +
  • L'option de ligne de commande -d.
    • + +
  • Le contenu du r챕pertoire courant.
    • + +
  • La racine du r챕pertoire d'installation cod챕e en dur dans le + serveur.
    • +
+ +

La racine du r챕pertoire d'installation cod챕e en dur dans le + serveur est en g챕n챕ral sys:/apache2. L'invocation + d'Apache avec l'option -V indiquera ce chemin comme + valeur de l'챕tiquette HTTPD_ROOT.

+ +

Apache 2.0 pour Netware comporte un jeu d'options de ligne de + commande permettant d'afficher ou de modifier certaines + caract챕ristiques de l'instance du serveur web en cours d'ex챕cution. + Ces options ne sont disponibles que lorsqu'Apache est en cours + d'ex챕cution. Chacune de ces options doit 챗tre pr챕c챕d챕e du mot-cl챕 + APACHE2.

+ +
+
RESTART
+
Demande 횪 Apache d'arr챗ter tout worker thread en cours + d'ex챕cution lorsqu'il devient inactif, de recharger le fichier de + configuration, et de red챕marrer chaque worker thread en fonction + de la nouvelle configuration.
+ +
VERSION
+
Affiche des informations 횪 propos de la version de l'instance + d'Apache en cours d'ex챕cution.
+ +
MODULES
+
Affiche la liste des modules charg챕s (int챕gr챕s et + externes).
+ +
DIRECTIVES
+
Affiche la liste des directives disponibles.
+ +
SETTINGS
+
Active ou d챕sactive l'affichage du statut des threads sur la + console. En cas d'activation, l'챕tat de chaque thread en cours + d'ex챕cution s'affiche sur l'챕cran de la console Apache.
+ +
SHUTDOWN
+
Arr챗te l'instance du serveur web Apache en cours + d'ex챕cution.
+ +
HELP
+
D챕crit chacune des options disponibles au cours de l'ex챕cution + d'Apache.
+
+ +

Par d챕faut, ces options sont pass챕es 횪 l'instance d'apache + s'ex챕cutant dans l'espace d'adressage du syst챔me d'exploitation. + Pour passer une option 횪 une instance d'Apache sp챕cifique + s'ex챕cutant dans un espace d'adressage prot챕g챕, ajouter le param챔tre + -p suivi du nom de l'espace d'adressage. Pour plus d'informations, + tapez "apache2 Help" sur la ligne de commande.

+ +
top
+
+

Configuration d'Apache pour NetWare

+ + + +

Apache lit en g챕n챕ral ses fichiers de configuration dans le + r챕pertoire conf. Ces fichiers sont les m챗mes que ceux + de la version Unix, mais quelques directives sont diff챕rentes sous + Netware. Voir la Documentation Apache pour + l'ensemble des directives disponibles.

+ +

Les principales diff챕rences propres 횪 Apache pour NetWare sont + :

+ +
    +
  • +

    Comme Apache pour Netware est une application multithread, + elle n'utilise pas de processus s챕par챕 pour chaque requ챗te, + comme c'est le cas pour certaines impl챕mentations sous Unix. Il + n'y a que des threads en cours d'ex챕cution : un thread parent, + et plusieurs threads enfants ou worker qui traitent les + requ챗tes.

    + +

    En cons챕quence, les directives de gestion des "processus" + sont diff챕rentes :

    + +

    MaxConnectionsPerChild - comme sous + Unix, cette directive contr척le le nombre maximum de connexions + qu'un worker thread peut traiter avant de s'arr챗ter. Avec la + valeur par d챕faut MaxConnectionsPerChild 0, + le thread va pouvoir traiter un nombre illimit챕 de requ챗tes. + Cette valeur est recommand챕e sous Netware, 횪 moins que vous + n'ayez des raisons particuli챔res de la modifier.

    + +

    StartThreads - + Cette directive indique au serveur le nombre de threads qu'il + doit lancer au d챕marrage. Il est recommand챕 de conserver la + valeur par d챕faut StartThreads 50.

    + +

    MinSpareThreads - + Cette directive indique au serveur le nombre de worker threads + additionnels qu'il doit lancer si le nombre de threads inactifs + tombe en dessous de cette valeur. Il est recommand챕 de conserver la + valeur par d챕faut MinSpareThreads 10.

    + +

    MaxSpareThreads - + Cette directive indique au serveur qu'il doit commencer 횪 + arr챗ter des worker threads si le nombre de threads inactifs + passe au dessus de cette valeur. Il est recommand챕 de conserver + la valeur par d챕faut MaxSpareThreads 100.

    + +

    MaxThreads - + Cette directive impose un nombre maximum de worker threads. Il + est recommand챕 de conserver la valeur par d챕faut + ThreadsPerChild 250.

    + +

    ThreadStackSize - + Cette directive indique au serveur la taille de la pile 횪 + utiliser pour un worker thread individuel. Il est recommand챕 de + conserver la valeur par d챕faut ThreadStackSize + 65536.

    +
    • + +
  • +

    Les directives qui acceptent des noms de fichiers comme + arguments ne doivent pas utiliser des noms de fichiers Unix, + mais des noms de fichiers Netware. Cependant, comme Apache + utilise des noms de style Unix en interne, on doit utiliser des + slashes et non des antislashes. Il est recommand챕 de pr챕fixer + tous les chemins de fichiers racines par un nom de volume. Si ce + dernier est omis, Apache supposera que le volume est + SYS:, ce qui n'est pas forc챕ment correct.

    +
    • + +
  • +

    Apache pour Netware a la possibilit챕 de charger des modules + en cours d'ex챕cution, sans avoir 횪 recompiler le serveur. Si + Apache est compil챕 avec les options par d챕faut, il va installer + de nombreux modules optionnels dans le r챕pertoire + \Apache2\modules. Pour les activer, ou en activer + d'autres, on doit utiliser la directive LoadModule. Par exemple, pour + activer le module status, ajoutez la ligne suivante :

    + +

    + LoadModule status_module modules/status.nlm +

    + +

    Des informations 횪 propos de la cr챕ation de modules + chargeables sont aussi disponibles.

    +
    • +
+ +

Autres directives sp챕cifiques 횪 Netware :

+ + + +
    +
  • CGIMapExtension - + Cette directive associe une extension de fichier CGI 횪 un + interpr챕teur de script.
    • +
+
    +
  • SecureListen - + Cette directive active le chiffrement SSL pour un port + sp챕cifique.
    • +
+
    +
  • NWSSLTrustedCerts - + Cette directive permet d'ajouter des certificats de confiance + pouvant 챗tre utilis챕s pour cr챕er des connexions s챕curis챕es vers + des serveurs mandataires.
    • +
+
    +
  • NWSSLUpgradeable - + Cette directive permet de faire passer en SSL une connexion + initialis챕e sur les adresse IP et Port sp챕cifi챕s.
    • +
+ + + +
top
+
+

Compilation d'Apache pour NetWare

+ + + +

La compilation d'Apache n챕cessite MetroWerks CodeWarrior 6.x ou + sup챕rieur. Une fois compil챕, Apache peut 챗tre install챕 횪 la racine + de tout volume Netware. Le r챕pertoire d'installation par d챕faut est + sys:/Apache2.

+ +

Avant de d챕marrer Apache, vous devez remplir le r챕pertoire + conf. Copiez le fichier HTTPD-STD.CONF + depuis le r챕pertoire conf de la distribution et + renommez-le en HTTPD.CONF. Editez le fichier + HTTPD.CONF en recherchant les rep챔res + @@Value@@, et remplacez ces derniers par la valeur + appropri챕e. Copiez de m챗me les fichiers conf/magic et + conf/mime.types. Vous pouvez aussi construire une + distribution compl챔te en ajoutant le mot-cl챕 install + lors de l'invocation des makefiles.

+ +

Pr챕requis :

+ + + +

Les outils de d챕veloppement suivants sont n챕cessaires pour la + compilation d'Apache pour Netware :

+ + + + + +

Compiler Apache en utilisant les makefiles Netware + :

+ + + +
    +
  • D챕finissez la variable d'environnement + NOVELLLIBC avec le chemin des biblioth챔ques Netware + pour C SDK ; par exemple :

    Set + NOVELLLIBC=c:\novell\ndk\libc

    • + +
  • D챕finissez la variable d'environnement + METROWERKS avec le chemin de votre compilateur + Metrowerks CodeWarrior ; par exemple :

    Set + METROWERKS=C:\Program Files\Metrowerks\CodeWarrior

    . Si + vous l'avez install챕 dans le r챕pertoire par d챕faut + C:\Program Files\Metrowerks\CodeWarrior, vous + n'avez pas besoin de d챕finir cette variable.
    • + +
  • D챕finissez la variable d'environnement LDAPSDK + avec le chemin des biblioth챔ques LDAP pour C ; par exemple : +

    Set + LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc

    • + +
  • D챕finissez la variable d'environnement ZLIBSDK + avec le chemin du code source de la biblioth챔que Zlib ; par + exemple :

    Set ZLIBSDK=D:\NOVELL\zlib

    • + +
  • D챕finissez la variable d'environnement PCRESDK + avec le chemin d'installation du code source de la biblioth챔que + PCRE ; par exemple : +

    Set PCRESDK=D:\NOVELL\pcre

    +
    • + +
  • D챕finissez la variable d'environnement AP_WORK + avec le chemin du code source de httpd. +

    Set AP_WORK=D:\httpd-2.0.x

    • + +
  • D챕finissez la variable d'environnement APR_WORK + avec le chemin du code source d'apr ; en g챕n챕ral + \httpd\srclib\apr, mais le projet APR peut se + trouver en dehors de la structure des r챕pertoires de httpd. +

    Set APR_WORK=D:\apr-1.x.x

    • + +
  • D챕finissez la variable d'environnement APU_WORK + avec le chemin du code source d'apr-util ; en + g챕n챕ral \httpd\srclib\apr-util, mais le projet + APR-UTIL peut se trouver en dehors de la structure des + r챕pertoires de httpd.

    Set + APU_WORK=D:\apr-util-1.x.x

    • + +
  • V챕rifiez que les chemins des utilitaires AWK et GNU make + (gmake.exe) ont bien 챕t챕 inclus dans la variable + d'environnement syst챔me PATH.
    • + +
  • T챕l챕chargez le code source et d챕compressez-le dans un + r챕pertoire de votre choix sur votre station de travail.
    • + +
  • Positionnez-vous dans le r챕pertoire \httpd-2.0 + et compilez les utilitaires pr챕compil챕s 횪 l'aide de la commande + "gmake -f nwgnumakefile prebuild". Cette cible va + cr챕er le r챕pertoire \httpd-2.0\nwprebuild, et y + copier tous les utilitaires n챕cessaires au franchissement des + 챕tapes suivantes de la compilation.
    • + +
  • Copiez les fichiers + \httpd-2.0\nwprebuild\GENCHARS.nlm et + \httpd-2.0\nwprebuild\DFTABLES.nlm vers le volume + SYS: d'un serveur Netware et ex챕cutez-les 횪 l'aide + des commandes suivantes : +

    + SYS:\genchars > sys:\test_char.h
    + SYS:\dftables sys:\chartables.c
    +

    +
    • + +
  • Copiez les fichiers test_char.h et + chartables.c vers le r챕pertoire + \httpd-2.0\os\netware de la machine o첫 s'effectue + la compilation.
    • + +
  • Positionnez-vous dans le r챕pertoire \httpd-2.0 + et compilez Apache 횪 l'aide de la commande "gmake -f + nwgnumakefile". Vous pouvez cr챕er un r챕pertoire pour la + distribution en ajoutant le param챔tre install 횪 la commande ; + par exemple : +

    gmake -f nwgnumakefile install

    +
    • +
+ + + +

Options de make suppl챕mentaires

+ + + +
    +
  • gmake -f nwgnumakefile

    Compile les versions + de distribution de tous les binaires et les copie dans un + r챕pertoire \release.

    • + +
  • gmake -f nwgnumakefile DEBUG=1

    Compile les versions + de d챕bogage de tous les binaires et les copie dans un + r챕pertoire \debug.

    • + +
  • gmake -f nwgnumakefile install

    Cr챕e une + distribution compl챔te d'Apache avec les binaires, la + documentation et les fichiers support dans un r챕pertoire + \dist\Apache2.

    • + +
  • gmake -f nwgnumakefile prebuild

    Compile tous + les utilitaires pr챕compil챕s et les copie dans le r챕pertoire + \nwprebuild.

    • + +
  • gmake -f nwgnumakefile installdev

    M챗me effet + que l'option install, mais en plus, les r챕pertoires + \lib et \include sont cr챕챕s dans le + r챕pertoire de destination, et les en-t챗tes et fichiers d'import + y sont copi챕s.

    • + +
  • gmake -f nwgnumakefile clean

    Supprime tous + les fichiers objets et les binaires de la zone de compilation + \release.o, ou \debug.o si + DEBUG a 챕t챕 d챕fini.

    • + +
  • gmake -f nwgnumakefile clobber_all

    M챗me effet + que clean, mais en plus, le r챕pertoire de la distribution est + supprim챕 s'il existe.

    • +
+ + + +

Variables d'environnement suppl챕mentaires

+ + + +
    +
  • Pour compiler tous les modules exp챕rimentaux, d챕finissez la + variable d'environnement EXPERIMENTAL : +

    Set EXPERIMENTAL=1

    +
    • + +
  • Pour compiler Apache en utilisant les sockets de style BSD + standard, plut척t que Winsock, d챕finissez la variable + d'environnement USE_STDSOCKETS : +

    Set USE_STDSOCKETS=1

    +
    • + +
+ + + +

Compilation de mod_ssl pour la plate-forme Netware

+ + + +

Pour fournir les services SSL, Apache pour Netware utilise par + d챕faut le module int챕gr챕 mod_nw_ssl. Ce module ne + fournit que les services SSL impl챕ment챕s par le syst챔me + d'exploitation Netware lui-m챗me pour g챕rer tous les chiffrements + pour un port donn챕. Cependant, on peut aussi utiliser mod_ssl de + la m챗me mani챔re que sur les autres plate-formes.

+ +

Afin de pouvoir compiler mod_ssl pour la plate-forme Netware, + les biblioth챔ques OpenSSL doivent 챗tre disponibles. Elles peuvent + 챗tre install챕es de la mani챔re suivante :

+ +
    +
  • T챕l챕chargez la derni챔re distribution du code source + d'OpenSSL 0.9.8 depuis la page OpenSSL Source (les + versions 0.9.7 doivent 챗tre patch챕es, et ne sont donc pas + recommand챕es).
    • + +
  • Editez le fichier NetWare/set_env.bat, et + effectuez toutes modifications n챕cessaires des chemins des + outils et utilitaires en fonction de votre environnement de + d챕veloppement.
    • + +
  • Ex챕cutez les scripts suivants depuis la racine du + r챕pertoire des sources d'OpenSSL : +

    + Netware\set_env netware-libc
    + Netware\build netware-libc +

    + Pour des raisons de performances, vous devez activer la + compilation avec le code ASM. T챕l챕charger NASM depuis le site SF. Configurez + ensuite OpenSSL pour utiliser le code ASM : +

    + Netware\build netware-libc nw-nasm enable-mdc2 enable-md5 +

    + Attention : n'utilisez pas l'Assembleur CodeWarrior - il + produit un code de mauvaise qualit챕 !
    • + +
  • Avant de compiler Apache, d챕finissez la variable + d'environnement OSSLSDK avec le chemin absolu de + la racine du r챕pertoire du code source d'openssl, et + d챕finissez WITH_MOD_SSL 횪 1. +

    + Set OSSLSDK=d:\openssl-0.9.8x
    + Set WITH_MOD_SSL=1 +

    • + +
+ + + +
+
+

Langues Disponibles:  en  | + fr  | + ko 

+
top

Commentaires

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 diff --git a/docs/manual/platform/netware.html.ko.euc-kr b/docs/manual/platform/netware.html.ko.euc-kr new file mode 100644 index 0000000..7c03952 --- /dev/null +++ b/docs/manual/platform/netware.html.ko.euc-kr @@ -0,0 +1,609 @@ + + + + + +Novell NetWare에서 아파치 사용하기 - Apache HTTP Server Version 2.4 + + + + + + +
+

모듈 | 지시어들 | FAQ | 용어 | 사이트맵

+

Apache HTTP Server Version 2.4

+
+
<-
+

Novell NetWare에서 아파치 사용하기

+
+

가능한 언어:  en  | + fr  | + ko 

+
+
이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.
+ + +

이 문서는 Novell NetWare 6.0 이상에서 아파치 2.0을 설치, + 설정, 실행하는 방법을 설명한다. 버그를 찾았거나 다른 방법으로 + 돕고싶다면, 버그 + 보고 페이지를 이용하길 바란다.

+ +

버그 보고 페이지나 dev-httpd 메일링리스트는 아파치 설정과 + 실행에 대한 질문을 답하지 않는다. 버그를 보고하기 + 전에 먼저 이 문서와 자주 물어보는 질문 + (FAQ) 페이지, 다른 관련문서를 살펴봐라. 그래도 궁금한 + 점이나 문제가 있다면, NetWare에서 아파치 사용에 대한 어렵고 + 새로운 질문을 답해줄 많은 아파치 사용자가 있는 + novell.devsup.webserver 뉴스그룹에 글을 올리길 바란다.

+ +

이 문서는 바이너리 배포본으로 아파치를 설치했다고 가정한다. + (아마도 개발에 도움을 주거나 버그를 찾기위해) 직접 아파치를 + 컴파일하려면 아래 NetWare에서 아파치 + 컴파일하기 절을 참고하라.

+ +
+ +
top
+
+

요구조건

+ + + +

아파치 2.0은 NetWare 6.0 service pack 3 이상에서 동작하도록 + 설계되었다. SP3보다 낮은 service pack을 사용한다면 최신 + NetWare + Libraries for C (LibC)를 설치해야 한다.

+ +

NetWare service pack은 여기에 + 있다.

+ +

최신 service pack이나 최신 버전 NetWare + Libraries for C (LibC)를 설치했다면 NetWare 5.1 환경에서도 + NetWare용 아파치 2.0을 실행할 수 있다. 경고: + NetWare용 아파치 2.0은 이 환경을 고려하지 않았고 테스트하지 + 않았다.

+ +
top
+
+

NetWare용 아파치 다운받기

+ + + +

아파치 최신 버전에 대한 정보는 http://www.apache.org/에서 + (아파치 웹서버) 찾을 수 있다. 여기에는 현재 버전과 최근 + 알파/베타테스트 버전, 미러 웹사이트와 ftp 사이트 정보가 + 있다. NetWare용 아파치 2.0의 최신 바이너리 배포본은 여기에서 + 다운받을 수 있다.

+ +
top
+
+

NetWare용 아파치 설치하기

+ + + +

현재 NetWare용 아파치 설치프로그램은 없다. NetWare용 + 아파치 2.0 소스를 직접 컴파일한다면 파일을 서버로 직접 + 복사해줘야 한다.

+ +

바이너리로 다운받은 NetWare용 아파치를 설치하는 과정은 + 다음과 같다 (sys:/apache2에 설치한다고 가정한다):

+ +
    +
  • 바이너리로 다운받은 압축파일을 SYS: 볼륨 + 최상위 디렉토리에 푼다 (다른 볼륨에 설치해도 된다)
    • + +
  • httpd.conf 파일을 수정하여 ServerRoot와 ServerName과 파일경로 값을 서버에 + 알맞게 지정한다
    • + +
  • 예를 들어

    SEARCH ADD SYS:\APACHE2

    와 + 같이 검색경로에 SYS:/APACHE2를 추가한다 +
    • + +
+ +

직접 소스를 컴파일한 경우 NetWare에 아파치를 설치하는 + 방법은 다음과 같다 (sys:/apache2에 설치한다고 + 가정한다):

+ +
    +
  • NetWare 볼륨에 Apache2라는 디렉토리를 + 만든다
    • + +
  • APACHE2.NLM과 APRLIB.NLM을 + SYS:/APACHE2에 복사한다
    • + +
  • SYS:/APACHE2 아래에 BIN이라는 + 디렉토리를 만든다
    • + +
  • HTDIGEST.NLM, HTPASSWD.NLM, + HTDBM.NLM, LOGRES.NLM, + ROTLOGS.NLM을 SYS:/APACHE2/BIN에 + 복사한다
    • + +
  • SYS:/APACHE2 아래에 CONF라는 + 디렉토리를 만든다
    • + +
  • HTTPD-STD.CONF 파일을 + SYS:/APACHE2/CONF에 복사하고 파일명을 + HTTPD.CONF로 변경한다
    • + +
  • MIME.TYPES, CHARSET.CONV, + MAGIC 파일을 SYS:/APACHE2/CONF + 디렉토리에 복사한다
    • + +
  • \HTTPD-2.0\DOCS\ICONS에 있는 모든 파일과 + 하위디렉토리를 SYS:/APACHE2/ICONS로 복사한다
    • + +
  • \HTTPD-2.0\DOCS\MANUAL에 있는 모든 파일과 + 하위디렉토리를 SYS:/APACHE2/MANUAL로 복사한다
    • + +
  • \HTTPD-2.0\DOCS\ERROR에 있는 모든 파일과 + 하위디렉토리를 SYS:/APACHE2/ERROR로 복사한다
    • + +
  • \HTTPD-2.0\DOCS\DICROOT에 있는 모든 파일과 + 하위디렉토리를 SYS:/APACHE2/HTDOCS로 복사한다
    • + +
  • 서버에 SYS:/APACHE2/LOGS 디렉토리를 만든다
    • + +
  • 서버에 SYS:/APACHE2/APACHE2/CGI-BIN이란 + 디렉토리를 만든다
    • + +
  • SYS:/APACHE2/MODULES 디렉토리를 만들고 + 모든 nlm 모듈을 modules 디렉토리로 복사한다
    • + +
  • HTTPD.CONF 파일의 모든 @@Value@@ + 표시를 적절한 설정으로 대체한다
    • + +

  • SEARCH ADD SYS:\APACHE2

    같이 검색경로에 + SYS:/APACHE2를 추가한다 +
    • +
+ +

기본 SYS 볼륨이 아닌 다른 볼륨에도 아파치를 + 설치할 수 있다.

+ +

makefile 명령어에 "install" 키워드를 사용하면 컴파일시 + 자동으로 DIST 하위디렉토리에 완전한 배포본을 + 만든다. makefile로 만든 배포본을 NetWare 볼륨 최상위 디렉토리로 + 복사하면 아파치가 설치된다 (아래 NetWare용 + 아파치 컴파일하기 참고).

+ +
top
+
+

NetWare용 아파치 실행하기

+ + + +

아파치를 시작하려면 콘솔에서 apache를 입력하면 + 된다. 그러면 운영체제 주소영역에 아파치를 읽어들인다. + 보호주소영역에 아파치를 읽어들이려면 다음과 같이 load 명령어로 + 주소영역을 지정한다:

+ +

+ load address space = apache2 apache2 +

+ +

그러면 아파치를 apache2라는 주소영역에 읽어들인다. + NetWare는 여러 아파치를 각각 다른 보호주소영역에 읽어들여서 + 여러 아파치를 동시에 실행할 수 있다.

+ +

아파치가 시작하면 (설정파일에서 Listen 지시어를 수정하지 + 않는한) 포트 80번을 기다린다. 브라우저를 시작하여 서버명 + 혹은 서버 주소를 입력하면 서버에 접속하여 기본페이지에 + 접근한다. 아파치 설명서 링크가 있는 환영페이지가 나와야 + 한다. 아무 일도 없거나 오류가 발생하면 logs + 디렉토리에 있는 error_log 파일을 살펴봐라.

+ +

기본 설치가 동작하면 conf 디렉토리에 있는 + 파일을 적절히 설정한다.

+ +

운영체제 주소영역에서 실행중인 아파치를 내릴려면 콘솔에 + 다음과 같이 입력한다:

+ +

+ unload apache2 +

+ +

혹은

+ +

+ apache2 shutdown +

+ +

보호주소영역에서 아파치를 실행했다면 unload 명령어에 + 주소영역을 지정한다:

+ +

+ unload address space = apache2 apache2 +

+ +

아파치가 설정파일 위치를 찾는 방법을 알아두어야 한다. + 명령행에서 설정파일을 지정하는 방법은 두가지다:

+ +
    +
  • -f는 특정 설정파일 경로를 지정한다
    • +
+ +

+ apache2 -f "vol:/my server/conf/my.conf" +

+ +

+ apache -f test/test.conf +

+ +

이 경우 설정파일은 올바른 ServerRoot를 설정해야 한다.

+ +

-f로 설정파일명을 지정하지 않으면, 아파치는 + 서버에 컴파일된 파일명을 (보통 conf/httpd.conf) + 사용한다. -V 옵션으로 아파치를 시작하면 + SERVER_CONFIG_FILE이라는 항목을 보여준다. + 아파치는 다음 순서대로 ServerRoot를 찾는다:

+ +
    +
  • -C 옵션의 ServerRoot 지시어.
    • + +
  • 명령행의 -d 옵션.
    • + +
  • 현재 디렉토리
    • + +
  • 서버에 컴파일된 server root.
    • +
+ +

서버에 컴파일된 server root는 보통 + sys:/apache2이다. -V 옵션으로 + 아파치를 시작하면 HTTPD_ROOT라는 항목을 보여준다.

+ +

NetWare용 아파치 2.0에는 실행중인 웹서버를 죽이거나 정보를 + 알려주는 명령행 지시어가 있다. 이들 지시어는 아파치 동작중에만 + 사용할 수 있다. 지시어 앞에는 APACHE2 키워드를 + 붙여야 한다.

+ +
+
RESTART
+
모든 쓰레드가 쉬는 상태일때 아파치를 죽이고, 설정파일을 + 다시 읽은후 새로운 설정에 따라 worker 쓰레드들을 재시작한다.
+ +
VERSION
+
현재 실행중인 아파치 버전 정보를 출력한다.
+ +
MODULES
+
기본 모듈과 외부 모듈 목록을 출력한다.
+ +
DIRECTIVES
+
모든 지시어 목록을 출력한다.
+ +
SETTINGS
+
콘솔에 쓰레드 상태 표시를 보이거나 없앤다. 상태를 + 보이면, 아파치 콘솔창에 동작하는 쓰레드들의 상태가 나온다.
+ +
SHUTDOWN
+
실행중인 아파치 웹서버를 죽인다.
+ +
HELP
+
실행 옵션들을 설명한다.
+
+ +

기본적으로 이 지시어들은 운영체제 주소영역에서 실행중인 + 아파치를 대상으로 한다. 아파치가 보호주소영역에서 실행중이라면, + -p와 주소영역 이름을 추가한다. 더 많은 정보를 보려면 명령행에 + "apache2 Help"를 입력한다.

+ +
top
+
+

NetWare용 아파치 설정하기

+ + + +

아파치는 보통 conf 디렉토리에 있는 설정파일로 + 설정한다. 이 파일은 유닉스용과 같지만, NetWare용 아파치에는 + 조금 다른 지시어들이 있다. 사용가능한 모든 지시어에 대해서는 + 아파치 문서를 참고하라.

+ +

NetWare용 아파치의 주된 차이점은:

+ +
    +
  • +

    NetWare용 아파치는 다중쓰레드 방식을 사용하기때문에, + 유닉스와 같이 요청마다 다른 프로세스를 사용하지 않는다. + 대신 여러 쓰레드를 실행한다: 부모 쓰레드와 요청을 처리하는 + 여러 자식 혹은 worker 쓰레드들.

    + +

    그러므로 "프로세스"-관리 지시어가 다르다:

    + +

    MaxRequestsPerChild - + 유닉스와 같이 worker 쓰레드가 요청을 얼마만큼 처리하고 + 죽을지를 조정한다. 권장하는 기본값 + MaxRequestsPerChild 0을 사용하면 쓰레드는 + 죽지않고 영원히 요청을 서비스한다. 특별한 이유가 없다면 + NetWare에서는 이 지시어를 0으로 설정하길 + 권한다.

    + +

    StartThreads - + 이 지시어는 서버가 처음에 시작할 쓰레드 개수를 결정한다. + 권장하는 기본값은 StartThreads 50이다.

    + +

    MinSpareThreads - + 서버는 쉬는(idle) 쓰레드 개수가 이 값보다 적으면 worker + 쓰레드를 더 만든다. 권장하는 기본값은 + MinSpareThreads 10이다.

    + +

    MaxSpareThreads - + 서버는 쉬는 쓰레드 개수가 이 값보다 많으면 worker 쓰레드를 + 죽이기 시작한다. 권장하는 기본값은 + MaxSpareThreads 100이다.

    + +

    MaxThreads - + 이 지시어는 worker 쓰레드의 최대 개수를 제한한다. 권장하는 + 기본값은 ThreadsPerChild 250이다.

    + +

    ThreadStackSize - + 한 worker 쓰레드가 사용할 스택 크기를 지시한다. 권장하는 + 기본값은 ThreadStackSize 65536이다.

    +
    • + +
  • +

    아규먼트로 파일명을 받는 지시어에는 유닉스 파일명이 + 아닌 NetWare 파일명을 사용해야 한다. 그러나 아파치가 + 내부적으로 유닉스식 파일명을 사용하기때문에 백슬래쉬 + 대신 슬래쉬를 사용해야 한다. 모든 절대경로에 볼륨명을 + 포함하길 바란다. 볼륨명을 생략하면 아파치는 + SYS: 볼륨이라고 잘못 가정할 수 있다.

    +
    • + +
  • +

    NetWare용 아파치는 서버를 다시 컴파일하지 않고 실행할때 + 모듈을 읽어들일 수 있다. 보통 아파치를 컴파일하면 + \Apache2\modules 디렉토리에 여러 추가 모듈을 + 설치한다. 이들 혹은 다른 모듈을 사용하려면 LoadModule 지시어를 사용한다. + 예를 들어 status 모듈을 사용한다면:

    + +

    + LoadModule status_module modules/status.nlm +

    + +

    읽어들일 수 + 있는 모듈 만들기에 대한 정보도 있다.

    +
    • +
+ +

이외의 NetWare 전용 지시어들:

+ + + +
    +
  • CGIMapExtension - + CGI 파일 확장자를 스크립트 인터프리터와 연결한다.
    • +
+
    +
  • SecureListen - + 특정 포트를 SSL 암호화한다.
    • +
+
    +
  • NWSSLTrustedCerts - + 프록시하는 서버에 보안연결할때 사용할 신뢰하는 + 인증서(certificate)를 추가한다.
    • +
+
    +
  • NWSSLUpgradeable - + 특정 주소/포트로 맺어진 연결을 SSL 연결로 변경할 수 + 있다.
    • +
+ + + +
top
+
+

Netware용 아파치 컴파일하기

+ + + +

아파치를 컴파일하려면 MetroWerks CodeWarrior 6.x 이상이 + 필요하다. 아파치를 컴파일하면 어떤 Netware 볼륨에라도 설치할 + 수 있다. 기본값은 sys:/Apache2 디렉토리다.

+ +

서버를 실행하기 전에 conf 디렉토리를 작성해야 + 한다. 배포본의 conf 디렉토리에 있는 + HTTPD-STD.CONF 파일명을 HTTPD.CONF로 + 변경한다. HTTPD.CONF 파일에서 @@Value@@ + 표시를 찾아서 적절한 설정으로 대체한다. conf/magic과 + conf/mime.types 파일도 복사한다. 아니면 makefile을 + 실행할때 install 키워드를 사용하면 완전한 배포본을 + 만든다.

+ +

요구사항:

+ + + +

NetWare용 아파치 2.0을 컴파일하려면 다음 개발도구가 + 필요하다:

+ + + + + +

NetWare makefile을 사용하여 아파치 컴파일하기:

+ + + +
    +
  • NOVELLLIBC 환경변수를 +

    Set NOVELLLIBC=c:\novell\ndk\libc

    와 + 같이 NetWare Libraries for C SDK 위치로 설정한다. +
    • + +
  • METROWERKS 환경변수를 +

    Set METROWERKS=C:\Program Files\Metrowerks\CodeWarrior

    와 + 같이 Metrowerks CodeWarrior 컴파일러를 설치한 위치로 + 설정한다. 기본 위치인 + C:\Program Files\Metrowerks\CodeWarrior에 + 설치하였다면, 환경변수를 설정할 필요는 없다.
    • + +
  • LDAPSDK 환경변수를 +

    Set LDAPSDK=c:\Novell\NDK\cldapsdk\NetWare\libc

    와 + 같이 LDAP Libraries for C를 설치한 위치로 설정한다. +
    • + +
  • ZLIBSDK 환경변수를 +

    Set ZLIBSDK=D:\NOVELL\zlib

    과 같이 + ZLib 라이브러리 소스코드 위치로 설정한다. +
    • + +
  • AP_WORK 환경변수를 \httpd-2.0 + 디렉토리의 전체 경로로 설정한다.
    • + +
  • APR_WORK 환경변수를 + \httpd-2.0\srclib\apr 디렉토리의 전체 경로로 + 설정한다.
    • + +
  • AWK 도구와 GNU make (gmake.exe) 도구가 + 시스템의 PATH 환경변수에 포함되있는지 + 확인한다.
    • + +
  • 소스코드를 다운받아 적당한 디렉토리에 압축을 푼다.
    • + +
  • \httpd-2.0\srclib\apr-util\uri 디렉토리에서 + "gmake -f nwgnumakefile"을 실행하여 + GENURI.nlm을 컴파일한다.
    • + +
  • GENURI.nlm 파일을 NetWare 서버의 + SYS: 볼륨으로 복사하고 +

    SYS:\genuri > sys:\uri_delims.h

    + 명령을 실행한다. +
    • + +
  • uri_delims.h 파일을 컴파일하는 컴퓨터의 + \httpd-2.0\srclib\apr-util\uri 디렉토리로 + 복사한다.
    • + +
  • \httpd-2.0\srclib\apr 디렉토리에서 + "gmake -f nwgnumakefile"을 실행하여 APR을 + 컴파일한다.
    • + +
  • \httpd-2.0\srclib\pcre 디렉토리에서 + "gmake -f nwgnumakefile"을 실행하여 + DFTABLES.nlm을 컴파일한다.
    • + +
  • \httpd-2.0\server 디렉토리에서 + "gmake -f nwgnumakefile"을 실행하여 + GENCHARS.nlm을 컴파일한다.
    • + +
  • 각 디렉토리의 GENCHARS.nlm과 + DFTABLES.nlm 파일을 NetWare 서버의 + SYS: 볼륨으로 복사하고 다음과 같이 실행한다: +

    + SYS:\genchars > sys:\test_char.h
    + SYS:\dftables > sys:\chartables.c
    +

    +
    • + +
  • test_char.h와 chartables.c + 파일을 컴파일하는 컴퓨터의 \httpd-2.0\os\netware + 디렉토리로 복사한다.
    • + +
  • \httpd-2.0 디렉토리에서 + "gmake -f nwgnumakefile"을 실행하여 아파치를 + 컴파일한다. +

    gmake -f nwgnumakefile install

    과 + 같이 install 파라미터를 추가하면 배포용 디렉토리를 만들 + 수 있다. +
    • +
+ + + +

추가 make 옵션

+ + + +
    +
  • gmake -f nwgnumakefile

    일반 실행파일을 + 컴파일하여 \release 디렉토리로 복사한다.

    • + +
  • gmake -f nwgnumakefile DEBUG=1

    디버그용 + 실행파일을 컴파일하여 \debug 디렉토리로 + 복사한다.

    • + +
  • gmake -f nwgnumakefile install +

    \dist\Apache2 디렉토리에 실행파일, 문서, + 추가 지원파일을 포함한 완전한 아파치 배포본을 만든다.

    • + +
  • gmake -f nwgnumakefile installdev +

    install과 비슷하지만, \lib과 + \include 디렉토리를 만들고 헤더파일과 import + 파일을 복사한다.

    • + +
  • gmake -f nwgnumakefile clean +

    DEBUG 정의 유무에 따라 \release나 + \debug에 있는 오브젝트파일과 실행파일을 + 모두 지운다.

    • + +
  • gmake -f nwgnumakefile clobber_all

    clean과 + 비슷하지만 디렉토리도 지운다.

    • +
+ + + +
+
+

가능한 언어:  en  | + fr  | + ko 

+
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 diff --git a/docs/manual/platform/perf-hp.html b/docs/manual/platform/perf-hp.html new file mode 100644 index 0000000..5e254ac --- /dev/null +++ b/docs/manual/platform/perf-hp.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: perf-hp.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: perf-hp.html.fr.utf8 +Content-Language: fr +Content-type: text/html; charset=UTF-8 + +URI: perf-hp.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/perf-hp.html.en b/docs/manual/platform/perf-hp.html.en new file mode 100644 index 0000000..396793b --- /dev/null +++ b/docs/manual/platform/perf-hp.html.en @@ -0,0 +1,131 @@ + + + + + +Running a High-Performance Web Server on HPUX - Apache HTTP Server Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.4

+
+
<-
+

Running a High-Performance Web Server on HPUX

+
+

Available Languages:  en  | + fr  | + ko 

+
+ + +
Date: Wed, 05 Nov 1997 16:59:34 -0800
+From: Rick Jones <raj@cup.hp.com>
+Reply-To: raj@cup.hp.com
+Organization: Network Performance
+Subject: HP-UX tuning tips
+ +

Here are some tuning tips for HP-UX to add to the tuning page.

+ +

For HP-UX 9.X: Upgrade to 10.20
+ For HP-UX 10.[00|01|10]: Upgrade to 10.20

+ +

For HP-UX 10.20:

+ +

Install the latest cumulative ARPA Transport Patch. This + will allow you to configure the size of the TCP connection + lookup hash table. The default is 256 buckets and must be set + to a power of two. This is accomplished with adb against the + *disc* image of the kernel. The variable name is tcp_hash_size. + Notice that it's critically important that you use "W" + to write a 32 bit quantity, not "w" to write a 16 bit + value when patching the disc image because the tcp_hash_size + variable is a 32 bit quantity.

+ +

How to pick the value? Examine the output of ftp://ftp.cup.hp.com/dist/networking/tools/connhist + and see how many total TCP connections exist on the system. You + probably want that number divided by the hash table size to be + reasonably small, say less than 10. Folks can look at HP's + SPECweb96 disclosures for some common settings. These can be + found at http://www.specbench.org/. + If an HP-UX system was performing at 1000 SPECweb96 connections + per second, the TIME_WAIT time of 60 seconds would mean + 60,000 TCP "connections" being tracked.

+ +

Folks can check their listen queue depths with ftp://ftp.cup.hp.com/dist/networking/misc/listenq.

+ +

If folks are running Apache on a PA-8000 based system, they + should consider "chatr'ing" the Apache executable to have a + large page size. This would be "chatr +pi L <BINARY>". + The GID of the running executable must have MLOCK privileges. + Setprivgrp(1m) should be consulted for assigning + MLOCK. The change can be validated by running Glance + and examining the memory regions of the server(s) to make sure that + they show a non-trivial fraction of the text segment being locked.

+ +

If folks are running Apache on MP systems, they might + consider writing a small program that uses mpctl() + to bind processes to processors. A simple pid % numcpu + algorithm is probably sufficient. This might even go into the + source code.

+ +

If folks are concerned about the number of FIN_WAIT_2 + connections, they can use nettune to shrink the value of + tcp_keepstart. However, they should be careful there - + certainly do not make it less than oh two to four minutes. If + tcp_hash_size has been set well, it is probably OK to + let the FIN_WAIT_2's take longer to timeout (perhaps + even the default two hours) - they will not on average have a big + impact on performance.

+ +

There are other things that could go into the code base, but + that might be left for another email. Feel free to drop me a + message if you or others are interested.

+ +

sincerely,

+ +

rick jones

+ +

http://www.netperf.org/netperf/

+ +
+
+
+

Available Languages:  en  | + fr  | + ko 

+
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 diff --git a/docs/manual/platform/perf-hp.html.fr.utf8 b/docs/manual/platform/perf-hp.html.fr.utf8 new file mode 100644 index 0000000..273f627 --- /dev/null +++ b/docs/manual/platform/perf-hp.html.fr.utf8 @@ -0,0 +1,143 @@ + + + + + +Mise en oeuvre d'un serveur Web hautes performances sous + HPUX - Serveur HTTP Apache Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur HTTP Apache Version 2.4

+
+
<-
+

Mise en oeuvre d'un serveur Web hautes performances sous + HPUX

+
+

Langues Disponibles:  en  | + fr  | + ko 

+
+ + +
Date: Wed, 05 Nov 1997 16:59:34 -0800
+From: Rick Jones <raj@cup.hp.com>
+Reply-To: raj@cup.hp.com
+Organization: Network Performance
+Subject: HP-UX tuning tips
+ +

Traduction du corps du message cit챕 ci-dessus :

+ +

Voici quelques conseils de personnalisation pour HPUX 횪 ajouter 횪 + la page de personnalisation.

+ +

Pour HP-UX 9.X: mettre 횪 jour vers la version 10.20
+ Pour HP-UX 10.[00|01|10]: mettre 횪 jour vers la version 10.20

+ +

Pour HP-UX 10.20:

+ +

Installez le dernier patch cumulatif 횪 propos du transport ARPA. + Ceci va vous permettre de configurer la taille de la table de + hashage de recherche de connexion TCP. La valeur par d챕faut est 256 + conteneurs et doit 챗tre une puissance de deux. �� cet effet, utilisez + adb pour modifier l'image *disque* du noyau. Le nom de la variable + est tcp_hash_size. Notez qu'il est imp챕ratif d'utiliser + "W" pour sp챕cifier une quantit챕 sur 32 bits, et non + "w" qui indique une valeur sur 16 bits, lors de la + modification de l'image disque car la variable + tcp_hash_size est une quantit챕 sur 32 bits.

+ +

Comment d챕terminer cette valeur ? Examinez la sortie de ftp://ftp.cup.hp.com/dist/networking/tools/connhist, et + comptez le nombre total de connexions TCP existant sur le syst챔me. + Il est en g챕n챕ral souhaitable que ce nombre divis챕 par la taille de + la table de hashage soit raisonnablement petit, disons inf챕rieur 횪 + 10. Les administrateurs peuvent consulter le document SPECweb96 de + HP pour quelques r챕glages courants. On peut les trouver 횪 http://www.specbench.org/. Si + un syst챔me HP-UX traite 1000 connexions SPECweb96 par seconde, une + valeur de temps TIME_WAIT de 60 secondes permettrait le + suivi de 60000 connexions TCP.

+ +

Les administrateurs peuvent tester la profondeur de leur file + d'attente d'챕coute avec ftp://ftp.cup.hp.com/dist/networking/misc/listenq.

+ +

Si Apache s'ex챕cute sur un syst챔me 횪 base de PA-8000, il est + conseill챕 de modifier l'ex챕cutable Apache avec la commande chatr + afin d'utiliser une page de grande taille. La commande sera du style + "chatr +pi L <BINARY>". Le GID de l'ex챕cutable en + cours de fonctionnement doit poss챕der le privil챔ge + MLOCK. Pour assigner ce privil챔ge MLOCK, + consultez Setprivgrp(1m). La modification peut 챗tre + valid챕e en ex챕cutant Glance et en examinant les portions de m챕moire + du/des serveur(s) afin de s'assurer qu'elles montrent une fraction + non triviale du segment de texte verrouill챕.

+ +

Si Apache s'ex챕cute sur un syst챔me MP (multi-processeurs), il est + conseill챕 d'챕crire un petit programme qui utilise + mpctl() et permettant d'associer les processus aux + processeurs. Un simple algorithme pid % numcpu suffira + probablement. Cette modification peut aussi 챗tre ajout챕e dans le + code source.

+ +

Si l'administrateur s'int챕resse au nombre de connexions + FIN_WAIT_2, il peut utiliser nettune pour diminuer la + valeur de tcp_keepstart. Il devra cependant 챗tre + prudent - surtout ne pas diminuer cette valeur en dessous de, disons + deux 횪 quatre minutes. Si tcp_hash_size a 챕t챕 d챕fini, + il est probablement appropri챕 de laisser les connexions + FIN_WAIT_2 prendre plus de temps 횪 expirer (peut-챗tre + m챗me la valeur par d챕faut de deux heures) - elles n'auront en + g챕n챕ral pas un grand impact sur les performances.

+ +

On peut ajouter d'autres choses au code de base, mais elles + feront peut-챗tre l'objet d'un autre email. N'h챕sitez pas 횪 m'envoyer + un message si vous 챗tes int챕ress챕.

+ +

sinc챔rement ,

+ +

rick jones

+ +

http://www.netperf.org/netperf/

+ +
+
+
+

Langues Disponibles:  en  | + fr  | + ko 

+
top

Commentaires

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 diff --git a/docs/manual/platform/perf-hp.html.ko.euc-kr b/docs/manual/platform/perf-hp.html.ko.euc-kr new file mode 100644 index 0000000..d4484b1 --- /dev/null +++ b/docs/manual/platform/perf-hp.html.ko.euc-kr @@ -0,0 +1,128 @@ + + + + + +HPUX에서 고성능 웹서버 실행하기 - Apache HTTP Server Version 2.4 + + + + + + +
+

모듈 | 지시어들 | FAQ | 용어 | 사이트맵

+

Apache HTTP Server Version 2.4

+
+
<-
+

HPUX에서 고성능 웹서버 실행하기

+
+

가능한 언어:  en  | + fr  | + ko 

+
+
이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.
+ + +
Date: Wed, 05 Nov 1997 16:59:34 -0800
+From: Rick Jones <raj@cup.hp.com>
+Reply-To: raj@cup.hp.com
+Organization: Network Performance
+Subject: HP-UX tuning tips
+ +

이 글은 성능향상 페이지에 추가할 HP-UX 성능향상 팁이다.

+ +

HP-UX 9.X는: 10.20으로 업그레이드하라
+ HP-UX 10.[00|01|10]은: 10.20으로 업그레이드하라

+ +

HP-UX 10.20은:

+ +

최근 ARPA Transport 패치 모음을 설치한다. 그러면 TCP + 연결찾기 해쉬테이블 크기를 설정할 수 있다. 기본값은 + 256 개이고, 2의 거듭제곱값으로 지정해야 한다. adb로 커널의 + *disc* 이미지를 수정하여 설정한다. 변수명은 + tcp_hash_size이다. tcp_hash_size + 변수값이 32비트이므로 disc 이미지를 수정할때 반드시 16비트 + 값을 기록하는 "w" 대신 32비트 값을 기록하는 + "W"를 사용해야 한다.

+ +

어떤 값을 고를까? ftp://ftp.cup.hp.com/dist/networking/tools/connhist의 + 결과를 보고, 시스템에 존재하는 TCP 연결 총개수를 살펴봐라. + 이 숫자를 해쉬테이블 크기로 나눈 값이 상당히 (10 이하) 작으면 + 좋다. HP의 SPECweb96 결과에서 일반적인 설정을 볼 수 있다. + 결과는 http://www.specbench.org/에 + 있다. HP-UX 시스템이 초당 1000번 SPECweb96 연결을 하는 경우 + TIME_WAIT가 60초라면 60,000개의 TCP "연결"을 + 추적한다는 뜻이다.

+ +

ftp://ftp.cup.hp.com/dist/networking/misc/listenq를 + 실행하여 시스템의 연결대기행렬 깊이를 알 수 있다.

+ +

PA-8000기반 시스템에서 아파치를 실행한다면, 아파치 + 실행파일이 큰 페이지크기를 사용하도록 "chatr"한다. 명령은 + "chatr +pi L <실행파일>"이다. 실행파일을 + 실행하는 GID에 MLOCK 권한이 반드시 필요하다. + MLOCK 부여에 대해서는 Setprivgrp(1m)를 + 참고하라. 수정후 Glance를 실행하여 서버의 메모리영역을 살펴보면 + 상당한 text 세그먼트가 잠겨있음을 확인할 수 있다.

+ +

다중프로세스 시스템에서 아파치를 실행한다면, 프로세스를 + 프로세스에 배정하는 mpctl()를 사용한 작은 + 프로그램을 작성해봐라. 단순한 pid % numcpu + 알고리즘으로도 충분할 것이다. 이 부분은 앞으로 소스코드에 + 포함될 수 있다.

+ +

FIN_WAIT_2 연결의 개수가 걱정스럽다면, + nettune을 사용하여 tcp_keepstart 값을 줄일 + 수 있다. 그러나 조심해야 한다 - 4분 보다 작게 설정하지 마라. + tcp_hash_size를 잘 설정하였다면, + FIN_WAIT_2 값이 커도 (심지어 기본값인 2시간도) + 문제없다 - 보통 성능에 큰 영향을 주지 않는다.

+ +

앞으로 소스코드에 포함될 부분이 더 있지만, 여기서 줄인다. + 관심이 있다면 메일을 주길 바란다.

+ +

그럼 이만,

+ +

rick jones

+ +

http://www.cup.hp.com/netperf/NetperfPage.html

+ +
+
+
+

가능한 언어:  en  | + fr  | + ko 

+
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 diff --git a/docs/manual/platform/rpm.html b/docs/manual/platform/rpm.html new file mode 100644 index 0000000..c456f1f --- /dev/null +++ b/docs/manual/platform/rpm.html @@ -0,0 +1,9 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: rpm.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: rpm.html.fr.utf8 +Content-Language: fr +Content-type: text/html; charset=UTF-8 diff --git a/docs/manual/platform/rpm.html.en b/docs/manual/platform/rpm.html.en new file mode 100644 index 0000000..733fc91 --- /dev/null +++ b/docs/manual/platform/rpm.html.en @@ -0,0 +1,248 @@ + + + + + +Using Apache With RPM Based Systems (Redhat / CentOS / Fedora) - Apache HTTP Server Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.4

+
+
<-
+

Using Apache With RPM Based Systems (Redhat / CentOS / Fedora)

+
+

Available Languages:  en  | + fr 

+
+ + +

While many distributions make Apache httpd available as operating system + supported packages, it can sometimes be desirable to install and use the + canonical version of Apache httpd on these systems, replacing the natively + provided versions of the packages.

+ +

While the Apache httpd project does not currently create binary RPMs + for the various distributions out there, it is easy to build your own + binary RPMs from the canonical Apache httpd tarball.

+ +

This document explains how to build, install, configure and run + Apache httpd 2.4 under Unix systems supporting the RPM packaging format.

+ +
+ +
top
+
+

Creating a Source RPM

+ + +

The Apache httpd source tarball can be converted into an SRPM as + follows:

+ +

+ rpmbuild -ts httpd-2.4.x.tar.bz2 +

+ +
top
+
+

Building RPMs

+ + +

RPMs can be built directly from the Apache httpd source tarballs using + the following command:

+ +

+ rpmbuild -tb httpd-2.4.x.tar.bz2 +

+ +

Corresponding "-devel" packages will be required to be installed on your + build system prior to building the RPMs, the rpmbuild command + will automatically calculate what RPMs are required and will list any + dependencies that are missing on your system. These "-devel" packages will + not be required after the build is completed, and can be safely removed.

+ +

If successful, the following RPMs will be created:

+ +
+
httpd-2.4.x-1.i686.rpm
+
The core server and basic module set.
+ +
httpd-debuginfo-2.4.x-1.i686.rpm
+
Debugging symbols for the server and all modules.
+ +
httpd-devel-2.4.x-1.i686.rpm
+
Headers and development files for the server.
+ +
httpd-manual-2.4.x-1.i686.rpm
+
The webserver manual.
+ +
httpd-tools-2.4.x-1.i686.rpm
+
Supporting tools for the webserver.
+ +
mod_authnz_ldap-2.4.x-1.i686.rpm
+
mod_ldap and mod_authnz_ldap, with + corresponding dependency on openldap.
+ +
mod_lua-2.4.x-1.i686.rpm
+
mod_lua module, with + corresponding dependency on lua.
+ +
mod_proxy_html-2.4.x-1.i686.rpm
+
mod_proxy_html module, with + corresponding dependency on libxml2.
+ +
mod_socache_dc-2.4.x-1.i686.rpm
+
mod_socache_dc module, with + corresponding dependency on distcache.
+ +
mod_ssl-2.4.x-1.i686.rpm
+
mod_ssl module, with + corresponding dependency on openssl.
+ +
+ +
top
+
+

Installing the Server

+ + +

The httpd RPM is the only RPM necessary to get a basic + server to run. Install it as follows:

+ +

+ rpm -U httpd-2.4.x-1.i686.rpm +

+ +

Self contained modules are included with the server. Modules that + depend on external libraries are provided as separate RPMs to install + if needed.

+ +
top
+
+

Configuring the Default Instance of Apache httpd

+ + +

The default configuration for the server is installed by default + beneath the /etc/httpd directory, with logs written by + default to /var/log/httpd. The environment for the + webserver is set by default within the optional + /etc/sysconfig/httpd file.

+ +

Start the server as follows:

+ +

+ service httpd restart +

+ +
top
+
+

Configuring Additional Instances of Apache httpd on the Same Machine

+ + +

It is possible to configure additional instances of the Apache + httpd server running independently alongside each other on the same + machine. These instances can have independent configurations, and + can potentially run as separate users if so configured.

+ +

This was done by making the httpd startup script aware of its own + name. This name is then used to find the environment file for the + server, and in turn, the server root of the server instance.

+ +

To create an additional instance called + httpd-additional, follow these steps:

+ +
    +
  • Create a symbolic link to the startup script for the additional + server: + +

    + ln -s /etc/rc.d/init.d/httpd /etc/rc.d/init.d/httpd-additional
    + chkconfig --add httpd-additional +

    + +
    • + +
  • Create an environment file for the server, using the + /etc/sysconfig/httpd file as a template: + +

    + # template from httpd
    + cp /etc/sysconfig/httpd /etc/sysconfig/httpd-additional +

    + +

    + # blank template
    + touch /etc/sysconfig/httpd-additional +

    + + Edit /etc/sysconfig/httpd-additional and pass the + server root of the new server instance within the + OPTIONS environment variable. + +

    + OPTIONS="-d /etc/httpd-additional -f conf/httpd-additional.conf" +

    + +
    • + +
  • Edit the server configuration file + /etc/httpd-additional/conf/httpd-additional.conf to + ensure the correct ports and paths are configured. +
    • + +
  • Start the server as follows: + +

    + service httpd-additional restart +

    + +
    • + +
  • Repeat this process as required for each server instance.
    • +
+ +
+
+

Available Languages:  en  | + fr 

+
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 diff --git a/docs/manual/platform/rpm.html.fr.utf8 b/docs/manual/platform/rpm.html.fr.utf8 new file mode 100644 index 0000000..6af0511 --- /dev/null +++ b/docs/manual/platform/rpm.html.fr.utf8 @@ -0,0 +1,264 @@ + + + + + +Utiliser Apache sur les syst챔mes 횪 base de paquets RPM (Redhat + / CentOS / Fedora) - Serveur HTTP Apache Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur HTTP Apache Version 2.4

+
+
<-
+

Utiliser Apache sur les syst챔mes 횪 base de paquets RPM (Redhat + / CentOS / Fedora)

+
+

Langues Disponibles:  en  | + fr 

+
+ + +

Alors que de nombreuses distributions mettent 횪 disposition des + paquets Apache httpd support챕s par le syst챔me d'exploitation + sous-jacent, il peut s'av챕rer n챕cessaire d'installer et d'utiliser + la version de base d'Apache httpd en remplacement de la version des + paquets.

+ +

Bien que le projet Apache httpd ne cr챕e pas actuellement de + paquets RPM pour les diff챕rentes distributions, il est ais챕 de + construire votre propre paquet RPM 횪 partir du tarball de base + d'Apache httpd.

+ +

Ce document explique comment construire, installer, configurer et + ex챕cuter Apache httpd 2.4 sur les syst챔mes Unix 횪 base de paquets + RPM.

+ +
+ +
top
+
+

Cr챕ation d'un paquet RPM source

+ + +

Le tarball d'Apache httpd peut 챗tre converti en paquet SRPM de la + mani챔re suivante :

+ +

+ rpmbuild -ts httpd-2.4.x.tar.bz2 +

+ +
top
+
+

Cr챕ation d'un paquet RPM

+ + +

Le tarball d'Apache httpd peut 챗tre converti en paquet RPM de la + mani챔re suivante :

+ +

+ rpmbuild -tb httpd-2.4.x.tar.bz2 +

+ +

Il sera n챕cessaire d'installer les paquets "-devel" + correspondants avant de construire les RPMs ; 횪 cet effet, la + commande rpmbuild d챕tecte automatiquement les RPMs + requis et en donne la liste sous forme de d챕pendances manquantes sur + votre syst챔me. Ces paquets "-devel" ne seront d'ailleurs plus + n챕cessaires une fois la cr챕ation des RPMs termin챕e, et pourront + alors 챗tre supprim챕s sans risque.

+ +

Si tout va bien, les RPMs suivants seront cr챕챕s :

+ +
+
httpd-2.4.x-1.i686.rpm
+
Le serveur de base et le jeu de modules standards.
+ +
httpd-debuginfo-2.4.x-1.i686.rpm
+
Les symboles de d챕bogage pour le serveur et tous les modules.
+ +
httpd-devel-2.4.x-1.i686.rpm
+
Les en-t챗tes et fichiers de d챕veloppement pour le serveur.
+ +
httpd-manual-2.4.x-1.i686.rpm
+
Le manuel du serveur web.
+ +
httpd-tools-2.4.x-1.i686.rpm
+
Les utilitaires du serveur web.
+ +
mod_authnz_ldap-2.4.x-1.i686.rpm
+
Les modules mod_ldap et + mod_authnz_ldap avec les d챕pendances + correspondantes sur openldap.
+ +
mod_lua-2.4.x-1.i686.rpm
+
Le module mod_lua avec les d챕pendances + correspondantes sur lua.
+ +
mod_proxy_html-2.4.x-1.i686.rpm
+
Le module mod_proxy_html avec les + d챕pendances correspondantes sur libxml2.
+ +
mod_socache_dc-2.4.x-1.i686.rpm
+
Le module mod_socache_dc avec les + d챕pendances correspondantes sur distcache.
+ +
mod_ssl-2.4.x-1.i686.rpm
+
Le module mod_ssl avec les + d챕pendances correspondantes sur openssl.
+ +
+ +
top
+
+

Installation du serveur

+ + +

Le RPM httpd est le seul paquet n챕cessaire pour + obtenir un serveur de base fonctionnel. Vous pouvez l'installer + comme suit :

+ +

+ rpm -U httpd-2.4.x-1.i686.rpm +

+ +

Le jeu de modules standards est inclus dans le serveur. Les + modules qui d챕pendent de biblioth챔ques externes sont fournis en tant + que paquets RPM s챕par챕s et doivent 챗tre install챕s si n챕cessaire.

+ +
top
+
+

Configuration de l'instance par d챕faut d'Apache httpd

+ + +

Les r챕pertoires par d챕faut sont + /etc/httpd pour la configuration du serveur, et + /var/log/httpd pour la journalisation. L'environnement + par d챕faut du serveur web est d챕fini dans le r챕pertoire optionnel + /etc/sysconfig/httpd.

+ +

D챕marrez le serveur comme suit :

+ +

+ service httpd restart +

+ +
top
+
+

Configuration d'instances d'Apache httpd suppl챕mentaires sur + la m챗me machine

+ + +

Il est possible d'ex챕cuter simultan챕ment plusieurs instances du + serveur Apache httpd sur la m챗me machine. Chaque instance peut + poss챕der sa propre configuration et en fonction de cette derni챔re, + s'ex챕cuter sous un utilisateur diff챕rent.

+ +

Pour parvenir 횪 ce r챕sultat, on a fait en sorte que le script de + d챕marrage de httpd ait connaissance de son propre nom. Ce nom est + par la suite utilis챕 pour trouver le fichier d'environnement associ챕 + au serveur, et par cons챕quent, la racine de l'instance du serveur + consid챕r챕.

+ +

Pour cr챕er une instance suppl챕mentaire appel챕e + httpd-additional, suivez ces 챕tapes :

+ +
    +
  • Cr챕ez un lien symbolique vers le script de d챕marrage pour + l'instance suppl챕mentaire : + +

    + ln -s /etc/rc.d/init.d/httpd /etc/rc.d/init.d/httpd-additional
    + chkconfig --add httpd-additional +

    + +
    • + +
  • Cr챕ez un fichier d'environnement pour l'instance + suppl챕mentaire, en utilisant le fichier + /etc/sysconfig/httpd comme mod챔le : + +

    + # cr챕ation du fichier d'environnement 횪 partir du mod챔le httpd
    + cp /etc/sysconfig/httpd /etc/sysconfig/httpd-additional +

    + +

    + # cr챕ation du fichier d'environnement 횪 partir de z챕ro
    + touch /etc/sysconfig/httpd-additional +

    + + Editez le fichier /etc/sysconfig/httpd-additional et + d챕finissez la racine de la nouvelle instance du serveur via la + variable d'environnement OPTIONS. + +

    + OPTIONS="-d /etc/httpd-additional -f conf/httpd-additional.conf" +

    + +
    • + +
  • Editez le fichier de configuration du serveur suppl챕mentaire + /etc/httpd-additional/conf/httpd-additional.conf et + assurez-vous que les ports et chemins sont correctement d챕finis. +
    • + +
  • D챕marrez le serveur suppl챕mentaire comme suit : + +

    + service httpd-additional restart +

    + +
    • + +
  • R챕p챕tez ces op챕rations pour chaque instance suppl챕mentaire + souhait챕e.
    • +
+ +
+
+

Langues Disponibles:  en  | + fr 

+
top

Commentaires

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 diff --git a/docs/manual/platform/win_compiling.html b/docs/manual/platform/win_compiling.html new file mode 100644 index 0000000..a0870bb --- /dev/null +++ b/docs/manual/platform/win_compiling.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: win_compiling.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: win_compiling.html.fr.utf8 +Content-Language: fr +Content-type: text/html; charset=UTF-8 + +URI: win_compiling.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/win_compiling.html.en b/docs/manual/platform/win_compiling.html.en new file mode 100644 index 0000000..e71a132 --- /dev/null +++ b/docs/manual/platform/win_compiling.html.en @@ -0,0 +1,517 @@ + + + + + +Compiling Apache for Microsoft Windows - Apache HTTP Server Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.4

+
+
<-
+

Compiling Apache for Microsoft Windows

+
+

Available Languages:  en  | + fr  | + ko 

+
+ + +

There are many important points to consider before you begin compiling + Apache HTTP Server (httpd). See Using Apache HTTP + Server on Microsoft Windows before you begin.

+ +

httpd can be built on Windows using a cmake-based build system or with + Visual Studio project files maintained by httpd developers. The cmake-based + build system directly supports more versions of Visual Studio but currently + has considerable functional limitations.

+ +
+ +
top
+
+

Building httpd with the included Visual Studio project files

+ + +

Requirements

+ + + +

Compiling Apache requires the following environment to be + properly installed:

+ +
    +
  • +

    Disk Space

    + +

    Make sure you have at least 200 MB of free disk space + available. After installation Apache requires approximately + 80 MB of disk space, plus space for log and cache files, + which can grow rapidly. The actual disk space requirements + will vary considerably based on your chosen configuration and + any third-party modules or libraries, especially when OpenSSL + is also built. Because many files are text and very easily + compressed, NTFS filesystem compression cuts these requirements + in half.

    +
    • + +
  • +

    Appropriate Patches

    + +

    The httpd binary is built with the help of several patches to + third party packages, which ensure the released code is buildable + and debuggable. These patches are available and distributed from http://www.apache.org/dist/httpd/binaries/win32/patches_applied/ + and are recommended to be applied to obtain identical results as the + "official" ASF distributed binaries.

    +
    • + +
  • +

    Microsoft Visual C++ 6.0 (Visual Studio 97) or later.

    + +

    Apache can be built using the command line tools, or from + within the Visual Studio IDE Workbench. The command line + build requires the environment to reflect the PATH, + INCLUDE, LIB and other variables + that can be configured with the vcvars32.bat script.

    + +
    You may want the Visual Studio Processor Pack for your older + version of Visual Studio, or a full (not Express) version of newer + Visual Studio editions, for the ml.exe assembler. This will allow + you to build OpenSSL, if desired, using the more efficient assembly + code implementation.
    + +
    Only the Microsoft compiler tool chain is actively supported by + the active httpd contributors. Although the project regularly accepts + patches to ensure MinGW and other alternative builds work and improve + upon them, they are not actively maintained and are often broken in + the course of normal development.
    +
    • + +
  • +

    Updated Microsoft Windows Platform SDK, February 2003 or later.

    + +

    An appropriate Windows Platform SDK is included by default in the + full (not express/lite) versions of Visual C++ 7.1 (Visual Studio 2002) + and later, these users can ignore these steps unless explicitly choosing + a newer or different version of the Platform SDK.

    + +

    To use Visual C++ 6.0 or 7.0 (Studio 2000 .NET), the Platform SDK + environment must be prepared using the setenv.bat + script (installed by the Platform SDK) before starting the command + line build or launching the msdev/devenv GUI environment. Installing + the Platform SDK for Visual Studio Express versions (2003 and later) + should adjust the default environment appropriately.

    + +

    + "c:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32"
    + "c:\Program Files\Platform SDK\setenv.bat" +

    +
    • + +
  • +

    Perl and awk

    + +

    Several steps recommended here require a perl interpreter during + the build preparation process, but it is otherwise not required.

    + +

    To install Apache within the build system, several files are + modified using the awk.exe utility. awk was chosen since + it is a very small download (compared with Perl or WSH/VB) and + accomplishes the task of modifying configuration files upon + installation. Brian Kernighan's + http://www.cs.princeton.edu/~bwk/btl.mirror/ + site has a compiled native Win32 binary, + http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe which + you must save with the name awk.exe (rather than + awk95.exe).

    + +
    If awk.exe is not found, Makefile.win's install target + will not perform substitutions in the installed .conf files. + You must manually modify the installed .conf files to allow + the server to start. Search and replace all "@token@" tags + as appropriate.
    + +
    The Visual Studio IDE will only find awk.exe + from the PATH, or executable path specified in the menu option + Tools -> Options -> (Projects ->) Directories. Ensure + awk.exe is in your system path.
    + +
    Also note that if you are using Cygwin tools + (http://www.cygwin.com/) + the awk utility is named gawk.exe and that the file + awk.exe is really a symlink to the gawk.exe + file. The Windows command shell does not recognize symlinks, and + because of this building InstallBin will fail. A workaround is + to delete awk.exe from the cygwin installation and + copy gawk.exe to awk.exe. Also note the + cygwin/mingw ports of gawk 3.0.x were buggy, please upgrade to 3.1.x + before attempting to use any gawk port.
    +
    • + +
  • +

    [Optional] zlib library (for mod_deflate)

    + +

    Zlib must be installed into a srclib subdirectory named + zlib. This must be built in-place. Zlib can be obtained + from http://www.zlib.net/ -- the + mod_deflate is confirmed to work correctly with + version 1.2.3.

    + +

    + nmake -f win32\Makefile.msc
    + nmake -f win32\Makefile.msc test +

    +
    • + +
  • +

    [Optional] OpenSSL libraries (for mod_ssl + and ab.exe with ssl support)

    + +
    The OpenSSL library is cryptographic software. The country + in which you currently reside may have restrictions on the import, + possession, use, and/or re-export to another country, of encryption + software. BEFORE using any encryption software, please check your + country's laws, regulations and policies concerning the import, + possession, or use, and re-export of encryption software, to see + if this is permitted. See + http://www.wassenaar.org/ + for more information.
    + +

    Configuring and building OpenSSL requires perl to be installed.

    + +

    OpenSSL must be installed into a srclib subdirectory + named openssl, obtained from + http://www.openssl.org/source/, in order to compile + mod_ssl or the abs.exe project, which + is ab.c with SSL support enabled. To prepare OpenSSL to be linked + to Apache mod_ssl or abs.exe, and disable patent encumbered features + in OpenSSL, you might use the following build commands:

    + +

    + perl Configure no-rc5 no-idea enable-mdc2 enable-zlib VC-WIN32 + -Ipath/to/srclib/zlib -Lpath/to/srclib/zlib
    + ms\do_masm.bat
    + nmake -f ms\ntdll.mak +

    + +
    It is not advisable to use zlib-dynamic, as that transfers + the cost of deflating SSL streams to the first request which must + load the zlib dll. Note the suggested patch enables the -L flag to + work with windows builds, corrects the name of zdll.lib and ensures + .pdb files are generated for troubleshooting. If the assembler is + not installed, you would add no-asm above and use ms\do_ms.bat + instead of the ms\do_masm.bat script.
    +
    • + +
  • +

    [Optional] Database libraries (for mod_dbd + and mod_authn_dbm)

    + +

    The apr-util library exposes dbm (keyed database) and dbd (query + oriented database) client functionality to the httpd server and its + modules, such as authentication and authorization. The sdbm dbm and + odbc dbd providers are compiled unconditionally.

    + +

    The dbd support includes the Oracle instantclient package, MySQL, + PostgreSQL and sqlite. To build these all, for example, set up the + LIB to include the library path, INCLUDE to include the headers path, + and PATH to include the dll bin path of all four SDK's, and set the + DBD_LIST environment variable to inform the build which client driver + SDKs are installed correctly, e.g.;

    + +

    + set DBD_LIST=sqlite3 pgsql oracle mysql +

    + +

    Similarly, the dbm support can be extended with DBM_LIST to + build a Berkeley DB provider (db) and/or gdbm provider, by similarly + configuring LIB, INCLUDE and PATH first to ensure the client library + libs and headers are available.

    + +

    + set DBM_LIST=db gdbm +

    + +
    Depending on the choice of database distributions, it may be + necessary to change the actual link target name (e.g. gdbm.lib vs. + libgdb.lib) that are listed in the corresponding .dsp/.mak files + within the directories srclib\apr-util\dbd or ...\dbm.
    + +

    See the README-win32.txt file for more hints on obtaining the + various database driver SDKs.

    +
    • +
+ + + +

Building from Unix sources

+ + + +

The policy of the Apache HTTP Server project is to only release Unix sources. + Windows source packages made available for download have been supplied by + volunteers and may not be available for every release. You can still build + the server on Windows from the Unix source tarball with just a few additional + steps.

+ +
    +
  1. Download and unpack the Unix source tarball for the latest version.
    2. +
  2. Download and unpack the Unix source tarball for latest version of + APR, AR-Util and APR-Iconv, place these sources in directories httpd-2.x.x\srclib\apr, httpd-2.x.x\srclib\apr-util and httpd-2.x.x\srclib\apr-iconv
    3. +
  3. Open a Command Prompt and CD to the httpd-2.x.x folder
    4. +
  4. Run the line endings conversion utility at the prompt;
    5. +
+ +

+ perl srclib\apr\build\lineends.pl +

+ +

You can now build the server with the Visual Studio development + environment using the IDE. Command-Line builds of the server are not + possible from Unix sources unless you export .mak files as explained + below. +

+ + + +

Command-Line Build

+ + + +

Makefile.win is the top level Apache makefile. + To compile Apache on Windows, simply use one of the following commands + to build the release or debug flavor:

+ +

+ nmake /f Makefile.win _apacher

+ nmake /f Makefile.win _apached +

+ +

Either command will compile Apache. The latter will disable + optimization of the resulting files, making it easier to single + step the code to find bugs and track down problems.

+ +

You can add your apr-util dbd and dbm provider choices with the + additional make (environment) variables DBD_LIST and DBM_LIST, + see the comments about [Optional] Database libraries, above. + Review the initial comments in Makefile.win for additional options + that can be provided when invoking the build.

+ + + +

Developer Studio Workspace IDE Build

+ + + +

Apache can also be compiled using VC++'s Visual Studio + development environment. To simplify this process, a + Visual Studio workspace, Apache.dsw, is provided. + This workspace exposes the entire list of working .dsp + projects that are required for the complete Apache binary release. + It includes dependencies between the projects to assure that they + are built in the appropriate order.

+ +

Open the Apache.dsw workspace, and select + InstallBin (Release or Debug build, + as desired) as the Active Project. InstallBin causes all + related project to be built, and then invokes Makefile.win to + move the compiled executables and dlls. You may personalize the + INSTDIR= choice by changing InstallBin's Settings, + General tab, Build command line entry. INSTDIR defaults to the + /Apache2 directory. If you only want a test compile (without + installing) you may build the BuildBin project instead.

+ +

The .dsp project files are distributed in Visual Studio 6.0 + (98) format. Visual C++ 5.0 (97) will recognize them. Visual Studio + 2002 (.NET) and later users must convert Apache.dsw plus + the .dsp files into an Apache.sln plus + .msproj files. Be sure you reconvert the .msproj + file again if its source .dsp file changes! This is really + trivial, just open Apache.dsw in the VC++ 7.0 IDE once again + and reconvert.

+ +
There is a flaw in the .vcproj conversion of .dsp files. devenv.exe + will mis-parse the /D flag for RC flags containing long quoted /D'efines + which contain spaces. The command: +

+ perl srclib\apr\build\cvtdsp.pl -2005 +

+ will convert the /D flags for RC flags to use an alternate, parseable + syntax; unfortunately this syntax isn't supported by Visual Studio 97 + or its exported .mak files. These /D flags are used to pass the long + description of the mod_apachemodule.so files to the shared .rc resource + version-identifier build.
+ +
Building with OpenSSL 1.1.0 and up + Due to difference in the build structure of OpenSSL begining with version + 1.1.0 you will need to convert the dsp files affected with cvtdsp.pl from + APR 1.6 or greater. The command: +

+ perl srclib\apr\build\cvtdsp.pl -ossl11 +

+
+ +

Visual Studio 2002 (.NET) and later users should also use the Build + menu, Configuration Manager dialog to uncheck both the Debug + and Release Solution modules abs, + mod_deflate and mod_ssl components, as + well as every component starting with apr_db*. These modules + are built by invoking nmake, or the IDE directly with the + BinBuild target, which builds those modules conditionally + if the srclib directories openssl and/or + zlib exist, and based on the setting of DBD_LIST + and DBM_LIST environment variables.

+ + + +

Exporting command-line .mak files

+ + + +

Exported .mak files pose a greater hassle, but they are + required for Visual C++ 5.0 users to build mod_ssl, + abs (ab with SSL support) and/or + mod_deflate. The .mak files also support a broader + range of C++ tool chain distributions, such as Visual Studio Express.

+ +

You must first build all projects in order to create all dynamic + auto-generated targets, so that dependencies can be parsed correctly. + Build the entire project from within the Visual Studio 6.0 (98) IDE, + using the BuildAll target, then use the Project Menu Export + for all makefiles (checking on "with dependencies".) Run the following + command to correct absolute paths into relative paths so they will build + anywhere:

+ +

+ perl srclib\apr\build\fixwin32mak.pl +

+ +

You must type this command from the top level + directory of the httpd source tree. Every + .mak and .dep project file within + the current directory and below will be corrected, and the + timestamps adjusted to reflect the .dsp.

+ +

Always review the generated .mak and .dep + files for Platform SDK or other local, machine specific file paths. + The DevStudio\Common\MSDev98\bin\ (VC6) directory contains + a sysincl.dat file, which lists all exceptions. Update + this file (including both forward and backslashed paths, such as both + sys/time.h and sys\time.h) to ignore such + newer dependencies. Including local-install paths in a distributed + .mak file will cause the build to fail completely.

+ +

If you contribute back a patch that revises project files, we + must commit project files in Visual Studio 6.0 format. Changes + should be simple, with minimal compilation and linkage flags that + can be recognized by all Visual Studio environments.

+ + + +

Installation

+ + + +

Once Apache has been compiled, it needs to be installed in + its server root directory. The default is the + \Apache2 directory, of the same drive.

+ +

To build and install all the files into the desired folder + dir automatically, use one of the following + nmake commands:

+ +

+ nmake /f Makefile.win installr INSTDIR=dir
+ nmake /f Makefile.win installd INSTDIR=dir +

+ +

The dir argument to INSTDIR provides + the installation directory; it can be omitted if Apache is + to be installed into \Apache22 (of the current + drive).

+ + + +

Warning about building Apache from the development tree

+ + + +
Note only the .dsp files are maintained between release + builds. The .mak files are NOT regenerated, due to the tremendous + waste of reviewer's time. Therefore, you cannot rely on the NMAKE + commands above to build revised .dsp project files unless you + then export all .mak files yourself from the project. This is + unnecessary if you build from within the Microsoft + Developer Studio environment.
+ + +
top
+
+

Building httpd with cmake

+ + +

The primary documentation for this build mechanism is in the + README.cmake file in the source distribution. Refer to that file + for detailed instructions.

+ +

Building httpd with cmake requires building APR and APR-util separately. + Refer to their README.cmake files for instructions.

+ +

The primary limitations of the cmake-based build are inherited from the APR-util + project, and are listed below because of their impact on httpd:

+ +
    +
  • No cmake build for the APR-iconv subproject is available, and the + APR-util cmake build cannot consume an existing APR-iconv build. Thus, + mod_charset_lite and possibly some third-party modules + cannot be used.
    • +
  • The cmake build for the APR-util subproject does not support most of the + optional DBM and DBD libraries supported by the included Visual Studio + project files. This limits the database backends supported by a number of + bundled and third-party modules.
    • +
+ +
+
+

Available Languages:  en  | + fr  | + ko 

+
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 diff --git a/docs/manual/platform/win_compiling.html.fr.utf8 b/docs/manual/platform/win_compiling.html.fr.utf8 new file mode 100644 index 0000000..1aa9b7e --- /dev/null +++ b/docs/manual/platform/win_compiling.html.fr.utf8 @@ -0,0 +1,603 @@ + + + + + +Compiler Apache pour Microsoft Windows - Serveur HTTP Apache Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur HTTP Apache Version 2.4

+
+
<-
+

Compiler Apache pour Microsoft Windows

+
+

Langues Disponibles:  en  | + fr  | + ko 

+
+ + +

Il y a de nombreux points importants 횪 conna챤tre avant de + compiler Le serveur HTTP Apache pour Microsoft Windows. Avant de commencer, lisez le + document Utiliser le serveur HTTP Apache avec Microsoft + Windows.

+ +

httpd peut 챗tre compil챕 sous Windows en utilisant une cha챤ne de + compilation bas챕e sur cmake, ou 횪 partir de fichiers projet Visual + Studio maintenus par les d챕veloppeurs de httpd. La cha챤ne de + compilation bas챕e sur cmake supporte directement davantage de + versions de Visual Studio, mais poss챔de actuellement des + fonctionnalit챕s tr챔s limit챕es.

+ +
+ +
top
+
+

Pr챕requis

+ + + +

Pour compiler Apache, l'environnement doit satisfaire aux + conditions suivantes :

+ +
    +
  • +

    Espace disque

    + +

    Assurez-vous de disposer d'un minimum de 200 Mo d'espace + disque disponible. Apr챔s l'installation, Apache occupe environ + 80 Mo d'espace disque, plus l'espace r챕serv챕 aux journaux et au + cache, la taille de ces derniers pouvant augmenter rapidement. + Les besoins r챕els en espace disque d챕pendent 챕troitement de la + configuration choisie et des biblioth챔ques ou modules tiers + install챕s, en particulier lorsqu'OpenSSL est mis en oeuvre. + Comme de nombreux fichiers sont au format texte et donc + facilement compressibles, l'utilisation de la compression du + syst챔me de fichiers NTFS divise ces besoins par deux.

    +
    • + +
  • +

    Correctifs requis

    + +

    Le binaire httpd est compil챕 횪 l'aide de nombreux correctifs + appliqu챕s aux paquets tiers, ce qui permet de s'assurer que le + code fourni est bien compilable et d챕boguable. Ces correctifs + sont disponibles 횪 http://www.apache.org/dist/httpd/binaries/win32/patches_applied/, + et il est recommand챕 de les appliquer afin d'obtenir un + r챕sultat identique aux binaires "officiels" distribu챕s par + l'ASF.

    +
    • + +
  • +

    Microsoft Visual C++ 6.0 (Visual Studio 97) ou sup챕rieur.

    + +

    Apache peut 챗tre compil챕 en utilisant l'outil ligne de + commande, ou depuis l'espace de travail IDE Visual Studio. Pour + la compilation depuis la ligne de commandes, l'environnement + doit comporter les variables the PATH, + INCLUDE, LIB, ainsi que d'autres + variables qui peuvent 챗tre d챕finies via le script + vcvars32.bat :

    + +
    Vous pouvez vous procurer le paquet du Processeur Visual + Studio pour votre ancienne version de Visual Studio, ou une + version compl챔te (et non Express) d'une 챕dition plus r챕cente de + Visual Studio pour l'assembleur ml.exe. Ceci vous permettra, si + vous le souhaitez, de compiler OpenSSL en utilisant une + impl챕mentation du code d'assemblage plus efficace.
    + +
    Seule la cha챤ne d'outils de compilation de Microsoft est + support챕e de mani챔re suivie par les contributeurs actifs 횪 httpd. + Bien que le projet accepte r챕guli챔rement des correctifs pour + s'assurer que MinGW et d'autre outils de compilation + fonctionnent, ou m챗me pour les am챕liorer, ils ne sont pas + maintenus de mani챔re suivie et sont m챗me souvent hors d'챕tat + de fonctionner 횪 certains stades du d챕veloppement normal.
    +
    • + +
  • +

    Le SDK de la plate-forme Windows mis 횪 jour, f챕vrier 2003 ou + plus r챕cent.

    + +

    Un SDK appropri챕 pour la plate-forme Windows est inclus par + d챕faut dans les versions compl챔tes (et non Express/lite) de + Visual C++ 7.1 (Visual Studio 2002) et sup챕rieures ; les + utilisateurs peuvent ignorer ces 챕tapes, 횪 moins qu'ils aient + choisi d'utiliser une version plus r챕cente ou diff챕rente du SDK.

    + +

    Pour pouvoir utiliser Visual C++ 6.0 or 7.0 (Studio 2000 + .NET), l'environnement du SDK de la plate-forme doit 챗tre pr챕par챕 en utilisant le + script setenv.bat (install챕 par le SDK de la plate-forme) avant de + lancer la compilation en ligne de commande ou l'interface GUI + msdev/devenv. L'installation du SDK de la plate-forme pour les + versions Express de Visual Studio (2003 et sup챕rieures) devrait + ajuster l'environnement par d챕faut de mani챔re appropri챕e.

    + +

    + "c:\Program Files\Microsoft Visual Studio\VC98\Bin\VCVARS32"
    + "c:\Program Files\Platform SDK\setenv.bat" +

    + + +
    • + +
  • +

    Perl et awk

    + +

    De nombreuses 챕tapes recommand챕es ici n챕cessitent un + interpr챕teur perl durant le processus de pr챕paration de la + compilation.

    + +

    Pour installer Apache 횪 partir du syst챔me de compilation, de + nombreux fichiers sont modifi챕s via l'utilitaire + awk.exe. awk effectue la modification des fichiers + au moment de l'installation ; il a 챕t챕 choisi car il n챕cessite + un t챕l챕chargement de petite taille (par rapport 횪 Perl ou + WSH/VB). Le site de Brian Kernighan http://www.cs.princeton.edu/~bwk/btl.mirror/ propose un + binaire pr챕compil챕 pour Win32, http://www.cs.princeton.edu/~bwk/btl.mirror/awk95.exe, que + vous devez enregistrer sous le nom awk.exe (plut척t + que awk95.exe).

    + +
    Si awk.exe n'est pas trouv챕, la cible install du fichier + Makefile.win n'effectuera aucune substitution dans les fichiers + .conf install챕s. Vous devez modifier manuellement les fichiers + .conf install챕s afin de permettre au serveur de d챕marrer. + Recherchez et remplacez toutes les balises "@token@" par une + valeur appropri챕e.
    + +
    L'IDE Visual Studio ne trouvera le chemin de + awk.exe que dans la variable PATH, ou dans le + chemin des ex챕cutables sp챕cifi챕 par l'option de menu Tools -> + Options -> (Projects ->) Directories. Assurez-vous + qu'awk.exe est bien dans votre chemin syst챔me.
    + +
    Notez aussi, si vous utilisez les outils Cygwin (http://www.cygwin.com/), que + l'utilitaire awk de nomme gawk.exe et que le + fichier awk.exe est en fait un lien symbolique vers + le fichier gawk.exe. Le shell de commandes Windows + ne reconna챤t pas les liens symboliques, et par cons챕quent la + compilation d'InstallBin 챕chouera. Pour contourner le probl챔me, + vous pouvez supprimer le lien awk.exe de + l'installation de Cygwin, et copier gawk.exe vers + awk.exe. Notez aussi que les portages cygwin/mingw + de gawk 3.0.x 챕taient bogu챕s ; veuillez par cons챕quent effectuer + une mise 횪 jour vers la version 3.1.x avant l'utilisation de + tout portage de gawk.
    +
    • + +
  • +

    [Optionnel] biblioth챔que zlib (pour le module + mod_deflate)

    + +

    Zlib doit 챗tre install챕e dans un sous-r챕pertoire du + r챕pertoire srclib et nomm챕 zlib. Elle + doit 챗tre compil챕e directement 횪 cette place. Zlib est + disponible 횪 l'adresse http://www.zlib.net/ -- le + fonctionnement correct du module mod_deflate a + 챕t챕 v챕rifi챕 avec la version 1.2.3.

    + +

    + nmake -f win32\Makefile.msc
    + nmake -f win32\Makefile.msc test +

    +
    • + +
  • +

    [Optionnel] Biblioth챔ques OpenSSL (pour le module + mod_ssl et ab.exe avec le support + ssl)

    + +
    La biblioth챔que OpenSSL est un logiciel de chiffrement. Le + pays dans lequel vous r챕sidez peut imposer des restrictions 횪 + l'importation, la possession, l'utilisation, et/ou la + r챕exportation vers un autre pays des logiciels de chiffrement. + AVANT d'utiliser tout logiciel de chiffrement, veuillez + consulter la l챕gislation de votre pays, les r챔gles et politiques + d'importation, de possession, ou d'utilisation, et de + r챕exportation des logiciels de chiffrement, afin de d챕terminer + si vous en avez le droit. Voir http://www.wassenaar.org/ + pour plus de d챕tails.
    + +

    La configuration et la compilation d'OpenSSL n챕cessite + l'installation de perl.

    + +

    Pour pouvoir compiler mod_ssl ou le projet + abs.exe, qui devient ab.c avec le support SSL + activ챕, vous devez + t챕l챕charger OpenSSL 횪 l'adresse http://www.openssl.org/source/, + et l'installer dans un sous-r챕pertoire du r챕pertoire + srclib que vous nommerez openssl. Afin + de pr챕parer OpenSSL 횪 la liaison avec le module Apache mod_ssl + ou abs.exe, et d챕sactiver les fonctionnalit챕s d'Openssl gr챕v챕es + de brevets, vous pouvez utiliser la commande de compilation + suivante :

    + +

    + perl Configure no-rc5 no-idea enable-mdc2 enable-zlib VC-WIN32 + -Ipath/to/srclib/zlib -Lpath/to/srclib/zlib
    + ms\do_masm.bat
    + nmake -f ms\ntdll.mak +

    + +
    Il est d챕conseill챕 d'utiliser zlib-dynamic, car la charge + de la d챕compression des flux SSL est alors transf챕r챕e 횪 la + premi챔re requ챗te qui doit charger la dll zlib. Notez que le + correctif propos챕 active le drapeau -L afin de pouvoir + fonctionner avec les compilations Windows, corrige le nom de + zdll.lib et s'assure que les fichiers .pdb sont g챕n챕r챕s afin de + pouvoir r챕soudre les probl챔mes. Si l'assembleur n'est pas + install챕, vous devez ajouter no-asm ci-dessus et utiliser le + script ms\do_ms.bat 횪 la place de ms\do_masm.bat.
    +
    • + +
  • +

    [Optionnel] Biblioth챔ques de bases de donn챕es (pour +mod_dbd et mod_authn_dbm)

    + +

    La biblioth챔que apr-util fournit un acc챔s aux fonctionnalit챕s + clients dbm (base de donn챕es 횪 base de cl챕s) et dbd (base de + donn챕es 횪 base de requ챗tes) au serveur httpd et 횪 certains de + ses modules, comme les modules d'authentification et + d'autorisation. Les fournisseurs sdbm dbm et odbc dbd sont + compil챕s automatiquement.

    + +

    Le support dbd inclut le paquet instantclient Oracle, MySQL, + PostgreSQL et sqlite. Par exemple, pour les compiler tous, + d챕finissez LIB de fa챌on 횪 inclure le chemin des biblioth챔ques, + INCLUDE de fa챌on 횪 inclure le chemin des en-t챗tes, et PATH de + fa챌on 횪 inclure le chemin des dll et bin de chacun des quatre + SDK, et d챕finissez la variable d'environnement DBD_LIST de fa챌on + 횪 indiquer au processus de compilation quels SDKs pilotes + clients du sont correctement install챕s ; par exemple :

    + +

    + set DBD_LIST=sqlite3 pgsql oracle mysql +

    + +

    De mani챔re similaire, le support dbm peut 챗tre 챕tendu avec + DBM_LIST pour compiler un fournisseur Berkeley DB (db) et/ou un + fournisseur gdbm, en configurant tout d'abord de la m챗me mani챔re + LIB, INCLUDE et PATH afin de s'assurer que les biblioth챔ques et + en-t챗tes de la biblioth챔que client sont bien disponibles.

    + +

    + set DBM_LIST=db gdbm +

    + +
    En fonction du choix des distributions de bases de + donn챕es, il peut s'av챕rer n챕cessaire de modifier le nom des + cibles de l'챕dition de liens (par exemple gdbm.lib 횪 la place de + libgdb.lib) list챕es dans les fichiers .dsp/.mak des r챕pertoires + srclib\apr-util\dbd ou ...\dbm correspondants.
    + +

    Voir le fichier README-win32.txt pour plus d'informations 횪 + propos de l'obtention des diff챕rents SDKs pilotes de bases de + donn챕es.

    +
    • + +
+ +
top
+
+

Compilation 횪 partir des sources Unix

+ + + +

Le projet du serveur HTTP Apache 횪 pour politique de ne fournir + que des sources de type Unix. Les paquets source de type Windows + disponibles en t챕l챕chargement ont 챕t챕 챕labor챕s par des + contributeurs, et ne seront pas forc챕ment reconduits pour toutes les + versions. Vous pouvez cependant compiler le serveur sous Windows 횪 + partir des sources Unix en ajoutant quelques 챕tapes suppl챕mentaires.

+ +
    +
  1. T챕l챕chargez et ouvrez le tarball source Unix de la derni챔re + version du serveur HTTP Apache.
    2. +
  2. T챕l챕chargez et ouvrez le tarball source Unix de la derni챔re + version de APR, APR-Util et APR-Iconv, et copier l'arborescence + obtenue dans httpd-2.x.x\srclib\apr, httpd-2.x.x\srclib\apr-util + et httpd-2.x.x\srclib\apr-iconv
    3. +
  3. Ouvrez la console et placez-vous au niveau du r챕pertoire httpd-2.x.x
    4. +
  4. Ex챕cutez l'utilitaire de conversion de fins de ligne
    5. +
+ +

+ perl srclib\apr\build\lineends.pl +

+ +

Vous pouvez maintenant compiler le serveur via l'environnement de + d챕veloppement Visual Studio en utilisant l'IDE. Les compilations + du serveur en ligne de commande ne sont possibles avec des sources + de type Unix que si vous exportez les fichiers .mak comme indiqu챕 + ci-dessous. +

+ +
top
+
+

Compilation 횪 partir de la ligne de commandes

+ + + +

Makefile.win est le makefile principal ou racine + d'Apache. Pour compiler Apache sous Windows, utilisez simplement une + des commandes suivantes pour compiler la version + release ou debug :

+ +

+ nmake /f Makefile.win _apacher

+ nmake /f Makefile.win _apached +

+ + +

Ces deux commandes effectuent la compilation d'Apache. Cependant, + avec la deuxi챔me, les fichiers r챕sultants ne seront pas optimis챕s, + ce qui va faciliter l'examen pas 횪 pas du code pour trouver des + bogues et r챕soudre les probl챔mes.

+ +

Vous pouvez indiquer vos choix en mati챔re de fournisseurs dbd et + dbm 횪 l'aide des variables (d'environnement) additionnelles de make + DBD_LIST et DBM_LIST ; voir les commentaires 횪 propos des + [Optionnel] Biblioth챔ques de bases de donn챕es ci-dessus. Consultez + les commentaires initiaux dans Makefile.win pour plus d'options + pouvant 챗tre fournies lors de la compilation.

+ +
top
+
+

Compilation depuis l'espace de travail IDE de Developer + Studio

+ + + +

Apache peut aussi 챗tre compil챕 depuis l'environnement de + d챕veloppement Visual Studio de VC++. Pour simplifier ce processus, + l'espace de travail Visual Studio Apache.dsw est + fourni. Cet espace de travail expose la liste compl챔te des projets + .dsp actifs n챕cessaires 횪 l'installation binaire + compl챔te d'Apache. Il inclut les d챕pendances entre projets afin que + ces derniers soient compil챕s selon l'ordre appropri챕.

+ +

Ouvrez l'espace de travail Apache.dsw, et + s챕lectionnez InstallBin (compilation + Release ou Debug, selon vos souhaits) + comme Active Project. InstallBin provoque la + compilation de tous les projets concern챕s, puis invoque + Makefile.win pour installer les ex챕cutables et dlls + compil챕s. Vous pouvez modifier la valeur de INSTDIR= + via la configuration de InstallBin, onglet G챕n챕ral, + entr챕e ligne de commandes de compilation. La valeur par d챕faut de + INSTDIR est le r챕pertoire /Apache2. Si + vous d챕sirez effectuer un test de compilation (sans installation), + s챕lectionnez le projet BuildBin.

+ +

Les fichiers projets .dsp sont distribu챕s au format + Visual Studio 6.0 (98). Visual C++ 5.0 (97) les reconna챤t. Les + utilisateurs de Visual Studio 2002 (.NET) et versions sup챕rieures + doivent convertir Apache.dsw et les fichiers + .dsp en un projet Apache.sln, ainsi que + les fichiers .msproj ; assurez-vous de reconvertir le + fichier .msproj si l'un des fichiers source + .dsp est modifi챕 ! Cette op챕ration est vraiment tr챔s + simple, il suffit de r챕ouvrir Apache.dsw dans l'IDE + VC++ 7.0 et de le reconvertir.

+ + +
Il y a une erreur dans la conversion .vcproj des fichiers + .dsp. devenv.exe interpr챔te mal le drapeau + /D pour les drapeaux RC contenant de grandes /D'챕finitions entour챕es + de guillemets, et contenant elles-m챗mes des espaces. Ainsi, la + commande : +

+ perl srclib\apr\build\cvtdsp.pl -2005 +

+ va convertir les drapeaux /D pour les drapeaux RC afin d'utiliser + une syntaxe alternative, interpr챕table ; malheureusement, cette + syntaxe n'est pas support챕e par Visual Studio 97 ou ses fichiers + .mak export챕s. Ces drapeaux /D permettent de transmettre la longue + description des fichiers de mod_apachemodule.so 횪 leurs compilations + d'identificateur de version de ressource .rc partag챕e.
+ + +
Compilation avec OpenSSL versions 1.1.0 et sup챕rieures + Suite 횪 une modification de la structure de compilation d'OpenSSL 횪 partir + de la version 1.1.0, vous devez convertir les fichiers dsp concern챕s via la + commance cvtdsp.pl fournie par APR versions 1.6 et sup챕rieures : +

+ perl srclib\apr\build\cvtdsp.pl -ossl11 +

+
+ + +

Les utilisateurs de Visual Studio 2002 (.NET) et versions + sup챕rieures doivent aussi utiliser + la bo챤te de dialogue Configuration Manager du menu Build pour + d챕cocher les deux versions Debug et + Release des modules mod_ssl + et mod_deflate pour abs. Ces modules + sont compil챕s + en invoquant nmake ou directement l'IDE avec la cible + BinBuild pour compiler ces modules de mani챔re + conditionnelle si les sous-r챕pertoires de srclib + openssl et/ou zlib existent, et en + fonction des d챕finitions des variables d'environnement + DBD_LIST et DBM_LIST.

+ +
top
+
+

Export des fichiers .mak de la ligne de commandes

+ + + + +

Les fichiers .mak export챕s posent plus de probl챔mes, + mais les utilisateurs de Visual C++ 5.0 en ont besoin pour compiler + mod_ssl, abs (ab avec support + SSL) et/ou mod_deflate. Les fichiers .mak + supportent aussi un choix plus large de distributions de cha챤nes + d'outils C++, comme Visual Studio Express.

+ +

Vous devez tout d'abord compiler tous les projets afin de cr챕er + toutes les cibles dynamiques auto-g챕n챕r챕es, de fa챌on 횪 ce que les + d챕pendances puissent 챗tre interpr챕t챕es correctement. Compilez + l'ensemble du projet depuis l'IDE Visual Studio 6.0 (98), en + utilisant la cible BuildAll, puis utilisez le menu de + projet Export pour tous les makefiles (en cochant "with + dependencies"). Utilisez la commande suivante pour transformer les + chemins absolus en chemins relatifs de fa챌on 횪 ce que la compilation + puisse s'effectuer depuis n'importe quelle position dans + l'arborescence :

+ +

+ perl srclib\apr\build\fixwin32mak.pl +

+ +

Vous devez ex챕cuter cette commande depuis la racine de + l'arborescence des sources de httpd. Tout fichier projet + .mak et .dep du r챕pertoire courant et de + ses sous-r챕pertoires sera corrig챕, et les rep챔res de temps ajust챕s + en fonction des .dsp.

+ +

V챕rifiez toujours le SDK de la plate-forme ou autres chemins + fichiers locaux, sp챕cifiques 횪 la machine dans les fichiers + .mak et .dep g챕n챕r챕s. Le r챕pertoire + DevStudio\Common\MSDev98\bin\ (VC6) contient un fichier + sysincl.dat qui 챕num챔re toutes les exceptions. Mettez 횪 + jour ce fichier (en particulier les chemins avec slashes et + anti-slashes, tels que sys/time.h et + sys\time.h) de fa챌on 횪 ignorer ces nouvelles + d챕pendances. Inclure les chemins d'installation locale dans un + fichier .mak distribu챕 fera 챕chouer la + compilation.

+ +

Si vous soumettez un patch qui modifie les fichiers projet, nous + devons valider la modification de ces fichiers projet au format + Visual Studio 6.0. Les modifications doivent 챗tres simples, avec un + minimum de drapeaux de compilation et d'챕dition de liens qui + pourront 챗tre reconnus par tous les environnements Visual + Studio.

+ +
top
+
+

Installation

+ + + + +

Une fois compil챕, Apache doit 챗tre install챕 dans le r챕pertoire + racine du serveur. La valeur par d챕faut est le r챕pertoire + \Apache2, sur le m챗me disque.

+ +

Pour compiler et installer automatiquement tous les fichiers dans + le r챕pertoire rep d챕sir챕, utilisez une des commandes + nmake suivantes :

+ +

+ nmake /f Makefile.win installr INSTDIR=dir
+ nmake /f Makefile.win installd INSTDIR=dir +

+ +

L'argument rep de INSTDIR permet de + sp챕cifier le r챕pertoire d'installation ; il peut 챗tre omis si Apache + doit 챗tre install챕 dans \Apache22 (du lecteur de disque + courant.

+ +
top
+
+

Avertissement 횪 propos de la compilation d'Apache 횪 partir de +l'arborescence de d챕veloppement

+ + + +
Notez que seuls les fichiers .dsp sont + maintenus d'une distribution release 횪 l'autre. Les + fichiers .mak ne sont PAS r챕g챕n챕r챕s, suite 횪 + l'챕norme perte de temps des relecteurs . Vous ne + pouvez donc pas utiliser les commandes NMAKE + ci-dessus pour compiler des fichiers de projet .dsp + r챕vis챕s si vous n'exporter pas ensuite vous-m챗me tous les + fichiers .mak du projet. Ceci n'est pas n챕cessaire + si vous effectuez la compilation depuis l'environnement + Microsoft Developer Studio.
+ +
top
+
+

Compilation de httpd avec cmake

+ + +

La documentation principale pour ce m챕canisme de compilation se trouve + dans le fichier README.cmake situ챕 dans l'arborescence + des sources. Consultez ce fichier pour des instructions d챕taill챕es.

+ +

Pour compiler httpd avec cmake, vous devez compiler APR et APR-util + s챕par챕ment. Consultez les fichiers README.cmake de ces + projets pour obtenir des instructions.

+ +

Les principales limitations de la compilation bas챕e sur cmake sont + h챕rit챕es du projet APR-util et sont 챕num챕r챕es ci-dessous 횪 cause de + leur impact sur httpd :

+ +
    +
  • Il n'est pas possible de compiler le projet APR-iconv avec + cmake, et la compilation de APR-util ne peut pas utiliser de projet + APR-iconv pr챕compil챕. A cause de cela, il n'est pas possible + d'utiliser mod_charset_lite et probablement + d'autres modules tiers.
    • +
  • La compilation du sous-projet APR-util avec cmake ne supporte + pas la plupart des biblioth챔ques optionnelles DBM et DBD utilis챕es + par les fichiers projet Visual Studio inclus. Cela limite les + serveurs de bases de donn챕es d'arri챔re-plan support챕s par de + nombreux modules tiers ou inclus.
    • +
+ +
+
+

Langues Disponibles:  en  | + fr  | + ko 

+
top

Commentaires

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 diff --git a/docs/manual/platform/win_compiling.html.ko.euc-kr b/docs/manual/platform/win_compiling.html.ko.euc-kr new file mode 100644 index 0000000..37a9654 --- /dev/null +++ b/docs/manual/platform/win_compiling.html.ko.euc-kr @@ -0,0 +1,448 @@ + + + + + +Microsoft Windows용 아파치 컴파일 - Apache HTTP Server Version 2.4 + + + + + + +
+

모듈 | 지시어들 | FAQ | 용어 | 사이트맵

+

Apache HTTP Server Version 2.4

+
+
<-
+

Microsoft Windows용 아파치 컴파일

+
+

가능한 언어:  en  | + fr  | + ko 

+
+
이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.
+ + +

아파치를 컴파일하기 전에 주의할 점이 많다. 미리 Microsoft Windows에서 아파치 사용법을 + 참고하라.

+ +
+ +
top
+
+

요구사항

+ + + +

아파치를 컴파일하려면 다음이 정상적으로 설치되야 한다:

+ +
    +
  • +

    디스크 공간

    +

    남은 디스크 공간이 최소한 50 MB는 되야 한다. 아파치 + 설치후에는 빨리 증가하는 로그와 캐쉬파일을 제외하고 + 약 10 MB 정도가 필요하다. 실제 디스크 사용량은 선택한 + 구성과 제삼자가 만든 모듈 혹은 라이브러리에 따라 크게 + 다르다.

    +
    • + +
  • +

    Microsoft Visual C++ 5.0 이상.

    +

    아파치는 명령행 도구를 사용하거나 Visual Studio IDE + Workbench 안에서 컴파일할 수 있다. 명령행에서 컴파일한다면 + vcvars32 배치파일이 설정하는 PATH, + INCLUDE, LIB 등 환경변수가 + 필요하다:

    + +

    + "c:\Program Files\DevStudio\VC\Bin\vcvars32.bat" +

    +
    • + +
  • +

    Windows Platform SDK.

    +

    어떤 아파치 기능을 사용하려면 Visual C++ 5.0에 추가로 + 최신 Microsoft Windows Platform SDK가 필요하다. 명령행에서 + 컴파일한다면 setenv 배치파일이 Platform + SDK 환경을 만든다:

    + +

    + "c:\Program Files\Platform SDK\setenv.bat" +

    + +

    Visual C++ 6.0 이상에 포함된 Platform SDK 파일은 + 충분하다. 이 버전을 사용하는 사용자는 이 과정을 생략해도 + 된다.

    + +
    모든 mod_isapi 기능을 사용하려면 + 최신 Windows Platform SDK가 필요하다. 최신 버전이 아니면 + MSVC++ 5.0은 mod_isapi 기능의 일부를 + 사용할 수 없다고 경고한다. http://msdn.microsoft.com/downloads/sdks/platform/platform.asp에 + 최신 버전이 있다.
    +
    • + +
  • +

    awk 도구 (awk, gawk 등).

    +

    컴파일한 시스템에 아파치를 설치하려면 + awk.exe 도구를 사용하여 여러 파일을 수정해야 + 한다. (Perl이나 WSH/VB과 비교하여) 다운받기에 매우 작고 + 파일 생성 작업이 가능하여 awk를 선택했다. Brian Kernighan의 + http://cm.bell-labs.com/cm/cs/who/bwk/ 사이트에 + 컴파일된 Win32 실행파일 http://cm.bell-labs.com/cm/cs/who/bwk/awk95.exe이 + 있다. 이름을 awk95.exe 대신 + awk.exe로 변경해야 한다.

    + +
    Developer Studio IDE는 Tools 메뉴 Options... + Directories 탭의 (Developer Studio 7.0이라면 Projects + - VC++ Directories pane) Executable files 경로 목록에서만 + awk.exe를 찾는다. 이 목록에 awk.exe + 경로를 추가하고, 필요하다면 PATH 환경변수에도 + 추가한다.
    + +
    Cygwin을 (http://www.cygwin.com/) 사용한다면 + gawk.exe라는 이름으로 awk 도구가 있으며, + awk.exe 파일은 gawk.exe 파일의 + 심볼링크임을 주의하라. Windows 명령 프롬프트가 심볼링크를 + 인식하지 못하기때문에 InstallBin을 컴파일할때 실패한다. + 해결책은 cygwin에서 awk.exe를 삭제하고 + gawk.exe 이름을 awk.exe로 + 바꾼다.
    +
    • + +
  • +

    [선택적인] OpenSSL 라이브러리 (mod_ssl과 + ab.exe의 ssl 지원에 사용)

    +

    주의: 강력한 암호화와 특허가 걸린 지적재산권을 + 전세계에 배포하는데는 상당한 제약이 있다. + OpenSSL은 미국 수출규제법이 규제하며 미국과 기타 지역에서 + 특허로 보호되는 지적재산권인 강력한 암호화를 포함한다. + Apache Software Foundation과 OpenSSL 프로젝트는 OpenSSL + 프로젝트가 제공하는 코드를 소유, 사용, 배포하는데 따른 + 법적 자문을 제공하지 않는다. 직접 법률 상담을 + 받길 바란다. 당신 행동의 책임은 당신에게 있다.

    + +

    mod_ssl이나 (SSL을 지원하는 + ab.exe) abs 프로젝트를 컴파일하려면, OpenSSL을 + http://www.openssl.org/source/에서 다운받아서 + srclib의 openssl이라는 + 하위디렉토리에 설치해야 한다. release와 + debug로 아파치를 컴파일할때 사용하며 0.9.7 + 버전에 있는 특허가 걸린 기능을 사용하지 않는다면, 아래 + 컴파일 명령어를 사용한다:

    + +

    + perl Configure VC-WIN32
    + perl util\mkfiles.pl >MINFO
    + perl util\mk1mf.pl dll no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile
    + perl util\mk1mf.pl dll debug no-asm no-mdc2 no-rc5 no-idea VC-WIN32 >makefile.dbg
    + perl util\mkdef.pl 32 libeay no-asm no-mdc2 no-rc5 no-idea >ms\libeay32.def
    + perl util\mkdef.pl 32 ssleay no-asm no-mdc2 no-rc5 no-idea >ms\ssleay32.def
    + nmake
    + nmake -f makefile.dbg +

    + +
    • + +
  • +

    [선택적인] zlib 소스 (mod_deflate에 + 사용)

    +

    Zlib을 srclib의 zlib라는 + 하위디렉토리에 설치해야 하지만, 소스를 미리 컴파일할 + 필요는 없다. 컴파일 시스템은 이 압축소스를 + mod_deflate 모듈과 같이 컴파일한다. + Zlib은 http://www.gzip.org/zlib/에서 구할 수 있다 -- + mod_deflate는 1.1.4 버전과 정상적으로 + 컴파일되었다.

    +
    • + +
+ +
top
+
+

명령행에서 컴파일하기

+ + + +

먼저 적당한 디렉토리에 아파치 배포본 압축을 푼다. 명령행 + 프롬프트를 열고 그 디렉토리로 cd한다.

+ +

Makefile.win 파일에 아파치 makefile 명령이 + 있다. Windows NT에서 release와 debug + 컴파일하는 명령어는 각각 다음과 같다:

+ + 
nmake /f Makefile.win _apacher
+
+nmake /f Makefile.win _apached
+ +

두 명령어 모두 아파치를 컴파일한다. 후자는 결과파일에 + 디버깅 정보를 포함하여 버그를 찾고 문제를 추적하기 쉽게 + 한다.

+ +
top
+
+

Developer Studio Workspace IDE에서 컴파일하기

+ + + +

VC++의 Visual Studio 개발 환경을 사용하여 아파치를 컴파일할 + 수도 있다. 과정을 쉽게 하려고 Visual Studio workspace + Apache.dsw를 제공한다. 이 workspace는 완전한 + 아파치 바이너리 배포본에 필요한 .dsp 프로젝트 + 목록을 담고있다. 또, 알맞은 순서로 컴파일하기위한 프로젝트간 + 의존성 정보도 포함한다.

+ +

Apache.dsw workspace를 열고 + InstallBin을 (Release나 + Debug 중 원하는 것을) Active Project로 선택한다. + InstallBin은 관련된 모든 프로젝트를 컴파일하고, + 컴파일된 실행파일과 dll을 옮기는 Makefile.win을 + 호출한다. InstallBin의 Settings, General 탭, + Build command line 항목을 수정하여 INSTDIR=을 + 변경할 수 있다. INSTDIR= 기본값은 + /Apache2 디렉토리이다. (설치하지않고) 테스트로 + 컴파일만 해보려면 대신 BuildBin 프로젝트를 + 사용한다.

+ +

.dsp 프로젝트 파일은 Visual C++ 6.0 형식이다. + Visual C++ 5.0 (97)에서도 이 파일을 사용할 수 있다. Visual + C++ 7.0 (.net)은 Apache.dsw와 .dsp + 파일들을 Apache.sln과 .msproj + 파일들로 변환한다. .dsp 소스파일을 수정하면 + 반드시 .msproj 파일로 다시 변환하라! 그냥 VC++ + 7.0 IDE에서 Apache.dsw를 다시 열기만 하면 된다.

+ +

또, Visual C++ 7.0 (.net) 사용자는 Build 메뉴, Configuration + Manager 대화창에서 Debug와 Release의 + abs, mod_ssl, mod_deflate + Solution modules 선택을 해제해야 한다. srclib에 + openssl이나 zlib 디렉토리가 있는 + 경우에만 nmake를 실행하거나 (이 모듈을 명시적으로 + 컴파일하는) IDE BinBuild 대상을 사용하여 모듈을 + 컴파일 할 수 있다.

+ +

Export한 .mak 파일들이 혼란스럽지만, Visual + C++ 5.0 사용자가 mod_ssl, abs (SSL을 지원하는 + ab), mod_deflate를 컴파일할때 필요하다. + VC++ 7.0 (.net) 사용자에게도 binenv 보다 + nmake를 사용하면 컴파일이 더 빠르다. VC++ 5.0이나 + 6.0 IDE에서 전체 프로젝트를 컴파일하고, Project 메뉴의 Export + for all makefiles를 사용하라. 동적으로 자동 생성하는 대상을 + 모두 컴파일하고 올바른 의존성 정보를 얻기위해서는 먼저 + 프로젝트를 컴파일해야 한다. 다음 명령어를 사용하여 경로를 + 수정하면 어떤 경로에서도 컴파일할 수 있다:

+ +

+ perl srclib\apr\build\fixwin32mak.pl +

+ +

httpd 소스 최상위 디렉토리에서 + 명령어를 실행해야 한다. 현재 디렉토리와 하위디렉토리에 있는 + 모든 .mak와 .dep 프로젝트파일을 + 수정하고, .dsp를 고려하여 파일시간을 수정한다.

+ +

프로젝트파일을 다듬어서 패치를 보낸다면, 프로젝트파일을 + Visual Studio 6.0 형식으로 만들어야 한다. 변경은 간단하고, + VC++ 5.0에서 7.0까지 모든 환경에서 인식하는 최소한의 컴파일 + 옵션과 링커 옵션을 사용해야 한다.

+ +
top
+
+

프로젝트 구성요소

+ + + +

Apache.dsw workspace와 makefile.win + nmake 스크립트는 다음 순서대로 아파치 서버 + .dsp 프로젝트를 컴파일한다:

+ +
    +
  1. srclib\apr\apr.dsp
    2. + +
  2. srclib\apr\libapr.dsp
    3. + +
  3. srclib\apr-util\uri\gen_uri_delims.dsp
    4. + +
  4. srclib\apr-util\xml\expat\lib\xml.dsp
    5. + +
  5. srclib\apr-util\aprutil.dsp
    6. + +
  6. srclib\apr-util\libaprutil.dsp
    7. + +
  7. srclib\pcre\dftables.dsp
    8. + +
  8. srclib\pcre\pcre.dsp
    9. + +
  9. srclib\pcre\pcreposix.dsp
    10. + +
  10. server\gen_test_char.dsp
    11. + +
  11. libhttpd.dsp
    12. + +
  12. Apache.dsp
    13. +
+ +

또, modules\ 하위디렉토리 아래 대부분의 + 모듈에는 프로젝트파일이 있다.

+ +

support\ 디렉토리에는 아파치를 실행하는데 + 필요하지는 않지만, 관리자가 아파치를 검사하거나 암호파일과 + 로그파일을 관리하는데 사용할 추가 프로그램들의 프로젝트파일이 + 있다. Windows 전용 지원 프로그램은 support\win32\ + 디렉토리에 따로 있다.

+ +
    +
  1. support\ab.dsp
    2. + +
  2. support\htdigest.dsp
    3. + +
  3. support\htpasswd.dsp
    4. + +
  4. support\logresolve.dsp
    5. + +
  5. support\rotatelogs.dsp
    6. + +
  6. support\win32\ApacheMonitor.dsp
    7. + +
  7. support\win32\wintty.dsp
    8. +
+ +

아파치를 컴파일하면 server root 디렉토리에 설치해야 한다. + 기본값은 같은 디스크의 \Apache2 디렉토리이다.

+ +

컴파일하고 모든 파일을 원하는 폴더 dir에 자동으로 + 설치하려면 다음 nmake 명령어중 하나를 사용한다:

+ + 
nmake /f Makefile.win installr INSTDIR=dir
+
+nmake /f Makefile.win installd INSTDIR=dir
+
+ +

INSTDIR의 dir 아규먼트는 설치디렉토리를 + 뜻한다. 생락하면 \Apache2에 아파치를 설치한다.

+ +

다음과 같이 설치한다:

+ +
    +
  • dir\bin\Apache.exe - 아파치 + 실행파일
    • + +
  • dir\bin\ApacheMonitor.exe - + 서비스 감시용 작업표시줄 아이콘 도구
    • + +
  • dir\bin\htdigest.exe - Digest + auth 암호파일 도구
    • + +
  • dir\bin\htdbm.exe - SDBM auth + 데이터베이스 암호파일 도구
    • + +
  • dir\bin\htpasswd.exe - Basic + auth 암호파일 도구
    • + +
  • dir\bin\logresolve.exe - 로그파일에서 + dns 이름을 찾는 도구
    • + +
  • dir\bin\rotatelogs.exe - 로그파일 + 순환 도구
    • + +
  • dir\bin\wintty.exe - 콘솔창 + 도구
    • + +
  • dir\bin\libapr.dll - Apache + Portable Runtime 공유 라이브러리
    • + +
  • dir\bin\libaprutil.dll - Apache + Utility Runtime 공유 라이브러리
    • + +
  • dir\bin\libhttpd.dll - Apache + Core 라이브러리
    • + +
  • dir\modules\mod_*.so - 읽어들일 + 수 있는 아파치 모듈
    • + +
  • dir\conf - 설정 디렉토리
    • + +
  • dir\logs - 비어있는 로그 + 디렉토리
    • + +
  • dir\include - C 언어 헤더파일
    • + +
  • dir\lib - 링크 라이브러리파일
    • +
+ +

개발중인 아파치 버전을 컴파일할때 경고

+ + + +
.dsp 파일은 release마다 + 새로 만들어진다. 개발자의 시간낭비를 막기위해 + .mak 파일은 새로 만들지 않는다. 그러므로 + NMAKE 명령어를 사용하여 새로운 .dsp + 프로젝트파일을 컴파일할 수 없다. 프로젝트에서 직접 모든 + .mak 파일을 export해야 한다. Microsoft Developer + Studio 환경에서 컴파일한다면 이 작업이 필요없다.
+ +
또, makefile을 export하기 전에 BuildBin + 프로젝트를 (혹은 _apacher나 _apached + 명령행 대상) 컴파일하면 매우 도움이 된다. 컴파일중에 많은 + 파일이 자동으로 만들어진다. 전체를 컴파일해야만 정상적으로 + 컴파일할때 필요한 의존파일을 모두 만든다.
+ +

배포용 .mak 파일을 만드려면 항상 + .mak (혹은 .dep)에서 Platform + SDK 등의 의존성을 점검하라. + DevStudio\SharedIDE\bin\ (VC5)나 + DevStudio\Common\MSDev98\bin\ (VC6) 디렉토리에는 + 모든 예외 목록이 담긴 sysincl.dat 파일이 + 있다. 이 파일에 의존성 정보를 추가한다 + (sys/time.h와 sys\time.h와 같이, + 경로는 슬래쉬를 사용한 것과 백슬래쉬를 사용한 것 모두를 + 추가한다). 배포할 .mak 파일에 현재 컴퓨터에만 + 해당하는 설치경로가 있다면 컴파일이 완전히 실패한다. + 그러므로 srclib/apr/build/fixwin32mak.pl을 + 실행해하여 .mak 파일에 있는 절대경로를 없애야 + 한다.

+ + + +
+
+

가능한 언어:  en  | + fr  | + ko 

+
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 diff --git a/docs/manual/platform/windows.html b/docs/manual/platform/windows.html new file mode 100644 index 0000000..85e68af --- /dev/null +++ b/docs/manual/platform/windows.html @@ -0,0 +1,13 @@ +# GENERATED FROM XML -- DO NOT EDIT + +URI: windows.html.en +Content-Language: en +Content-type: text/html; charset=ISO-8859-1 + +URI: windows.html.fr.utf8 +Content-Language: fr +Content-type: text/html; charset=UTF-8 + +URI: windows.html.ko.euc-kr +Content-Language: ko +Content-type: text/html; charset=EUC-KR diff --git a/docs/manual/platform/windows.html.en b/docs/manual/platform/windows.html.en new file mode 100644 index 0000000..5bb7302 --- /dev/null +++ b/docs/manual/platform/windows.html.en @@ -0,0 +1,664 @@ + + + + + +Using Apache HTTP Server on Microsoft Windows - Apache HTTP Server Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossary | Sitemap

+

Apache HTTP Server Version 2.4

+
+
<-
+

Using Apache HTTP Server on Microsoft Windows

+
+

Available Languages:  en  | + fr  | + ko 

+
+ +

This document explains how to install, configure and run + Apache 2.4 under Microsoft Windows. If you have questions after + reviewing the documentation (and any event and error logs), you + should consult the peer-supported + users' mailing + list.

+ +

This document assumes that you are installing a binary + distribution of Apache. If you want to compile Apache yourself + (possibly to help with development or tracking down bugs), + see Compiling Apache for Microsoft + Windows.

+
+ +
top
+
+

Operating System Requirements

+ + +

The primary Windows platform for running Apache 2.4 is Windows + 2000 or later. Always obtain and + install the current service pack to avoid operating system bugs.

+ +
Apache HTTP Server versions later than 2.2 will not run on any + operating system earlier than Windows 2000.
+
top
+
+

Downloading Apache for Windows

+ + +

The Apache HTTP Server Project itself does not provide binary releases of + software, only source code. Individual committers may provide + binary packages as a convenience, but it is not a release deliverable.

+

If you cannot compile the Apache HTTP Server + yourself, you can obtain a binary package from numerous binary distributions + available on the Internet.

+ +

Popular options for deploying Apache httpd, and, optionally, PHP + and MySQL, on Microsoft Windows, include:

+ +
top
+
+

Customizing Apache for Windows

+ + +

Apache is configured by the files in the conf + subdirectory. These are the same files used to configure the Unix + version, but there are a few different directives for Apache on + Windows. See the directive index + for all the available directives.

+ +

The main differences in Apache for Windows are:

+
    +

  • Because Apache for Windows is multithreaded, it does not + use a separate process for each request, as Apache can on Unix. + Instead there are usually only two Apache processes running: a + parent process, and a child which handles the requests. Within + the child process each request is handled by a separate thread. +

    + +

    The process management directives are also different:

    + +

    MaxConnectionsPerChild: + Like the Unix directive, this controls how many connections a single + child process will serve before exiting. + However, unlike on Unix, a replacement process is not instantly + available. Use the default MaxConnectionsPerChild 0, + unless instructed to change the behavior to overcome a memory leak + in third party modules or in-process applications.

    + +
    Warning: The server configuration + file is reread when a new child process is started. If you have + modified httpd.conf, the new child may not start or + you may receive unexpected results.
    + +

    ThreadsPerChild: + This directive is new. It tells the server how many threads it + should use. This is the maximum number of connections the server + can handle at once, so be sure to set this number high enough for + your site if you get a lot of hits. The recommended default is + ThreadsPerChild 150, but this must be adjusted to + reflect the greatest anticipated number of simultaneous + connections to accept.

    • + +

  • The directives that accept filenames as arguments must use + Windows filenames instead of Unix ones. However, because Apache + may interpret backslashes as an "escape character" sequence, you + should consistently use forward slashes in path names, not + backslashes.

    • + +

  • While filenames are generally case-insensitive on + Windows, URLs are still treated internally as case-sensitive + before they are mapped to the filesystem. For example, the + <Location>, + Alias, and ProxyPass directives all use + case-sensitive arguments. For this reason, it is particularly + important to use the <Directory> directive when attempting + to limit access to content in the filesystem, since this + directive applies to any content in a directory, regardless of + how it is accessed. If you wish to assure that only lowercase + is used in URLs, you can use something like:

    + + 
    RewriteEngine On
+RewriteMap lowercase int:tolower
+RewriteCond "%{REQUEST_URI}" "[A-Z]"
+RewriteRule "(.*)" "${lowercase:$1}" [R,L]
    +
    • + +

  • When running, Apache needs write access only to the logs + directory and any configured cache directory tree. Due to the + issue of case insensitive and short 8.3 format names, Apache must + validate all path names given. This means that each directory + which Apache evaluates, from the drive root up to the directory + leaf, must have read, list and traverse directory permissions. + If Apache2.4 is installed at C:\Program Files, then the root + directory, Program Files and Apache2.4 must all be visible + to Apache.

    • + +

  • Apache for Windows contains the ability to load modules at + runtime, without recompiling the server. If Apache is compiled + normally, it will install a number of optional modules in the + \Apache2.4\modules directory. To activate these or + other modules, the LoadModule + directive must be used. For example, to activate the status + module, use the following (in addition to the status-activating + directives in access.conf):

    + + 
    LoadModule status_module modules/mod_status.so
    + + +

    Information on creating + loadable modules is also available.

    • + +

  • Apache can also load ISAPI (Internet Server Application + Programming Interface) extensions such as those used by Microsoft + IIS and other Windows servers. More + information is available. Note that Apache cannot + load ISAPI Filters, and ISAPI Handlers with some Microsoft feature + extensions will not work.

    • + +

  • When running CGI scripts, the method Apache uses to find + the interpreter for the script is configurable using the + ScriptInterpreterSource + directive.

    • + +

  • Since it is often difficult to manage files with names + like .htaccess in Windows, you may find it useful to + change the name of this per-directory configuration file using + the AccessFilename + directive.

    • + +

  • Any errors during Apache startup are logged into the + Windows event log when running on Windows NT. This mechanism + acts as a backup for those situations where Apache is not yet + prepared to use the error.log file. You can + review the Windows Application Event Log by using the Event Viewer, + e.g. Start - Settings - Control Panel - Administrative Tools + - Event Viewer.

    • +
+ +
top
+
+

Running Apache as a Service

+ + +

Apache comes with a utility called the Apache Service Monitor. + With it you can see and manage the state of all installed Apache + services on any machine on your network. To be able to manage an + Apache service with the monitor, you have to first install the + service (either automatically via the installation or manually). +

+ +

You can install Apache as a Windows NT service as follows from + the command prompt at the Apache bin subdirectory:

+ +

+ httpd.exe -k install +

+ +

If you need to specify the name of the service you want to + install, use the following command. You have to do this if you + have several different service installations of Apache on your + computer. If you specify a name during the install, you have to + also specify it during any other -k operation.

+ +

+ httpd.exe -k install -n "MyServiceName" +

+ +

If you need to have specifically named configuration files for + different services, you must use this:

+ +

+ httpd.exe -k install -n "MyServiceName" -f "c:\files\my.conf" +

+ +

If you use the first command without any special parameters except + -k install, the service will be called Apache2.4 + and the configuration will be assumed to be conf\httpd.conf. +

+ +

Removing an Apache service is easy. Just use:

+ +

+ httpd.exe -k uninstall +

+ +

The specific Apache service to be uninstalled can be specified by using:

+ +

+ httpd.exe -k uninstall -n "MyServiceName" +

+ +

Normal starting, restarting and shutting down of an Apache + service is usually done via the Apache Service Monitor, by using + commands like NET START Apache2.4 and NET STOP + Apache2.4 or via normal Windows service management. Before + starting Apache as a service by any means, you should test the + service's configuration file by using:

+ +

+ httpd.exe -n "MyServiceName" -t +

+ +

You can control an Apache service by its command line switches, + too. To start an installed Apache service you'll use this:

+ +

+ httpd.exe -k start -n "MyServiceName" +

+ +

To stop an Apache service via the command line switches, use + this:

+ +

+ httpd.exe -k stop -n "MyServiceName" +

+ +

or

+ +

+ httpd.exe -k shutdown -n "MyServiceName" +

+ +

You can also restart a running service and force it to reread + its configuration file by using:

+ +

+ httpd.exe -k restart -n "MyServiceName" +

+ +

By default, all Apache services are registered to run as the + system user (the LocalSystem account). The + LocalSystem account has no privileges to your network + via any Windows-secured mechanism, including the file system, named + pipes, DCOM, or secure RPC. It has, however, wide privileges locally. +

+ +
Never grant any network privileges to + the LocalSystem account! If you need Apache to be able + to access network resources, create a separate account for Apache as + noted below.
+ +

It is recommended that users create a separate account for running + Apache service(s). If you have to access network resources via Apache, + this is required.

+ +
    +
  1. Create a normal domain user account, and be sure to + memorize its password.
    2. + +
  2. Grant the newly-created user a privilege of Log on + as a service and Act as part of the operating + system. On Windows NT 4.0 these privileges are granted via + User Manager for Domains, but on Windows 2000 and XP you probably + want to use Group Policy for propagating these settings. You can + also manually set these via the Local Security Policy MMC snap-in. +
    3. + +
  3. Confirm that the created account is a member of the Users + group.
    4. + +
  4. Grant the account read and execute (RX) rights to all document + and script folders (htdocs and cgi-bin + for example).
    5. + +
  5. Grant the account change (RWXD) rights to the + Apache logs directory.
    6. + +
  6. Grant the account read and execute (RX) rights to the + httpd.exe binary executable.
    7. +
+ +
It is usually a good practice to grant the user the Apache + service runs as read and execute (RX) access to the whole Apache2.4 + directory, except the logs subdirectory, where the + user has to have at least change (RWXD) rights.
+ +

If you allow the account to log in as a user and as a service, + then you can log on with that account and test that the account has + the privileges to execute the scripts, read the web pages, and that + you can start Apache in a console window. If this works, and you + have followed the steps above, Apache should execute as a service + with no problems.

+ +
Error code 2186 is a good indication that + you need to review the "Log On As" configuration for the service, + since Apache cannot access a required network resource. Also, pay + close attention to the privileges of the user Apache is + configured to run as.
+ +

When starting Apache as a service you may encounter an error + message from the Windows Service Control Manager. For example, + if you try to start Apache by using the Services applet in the + Windows Control Panel, you may get the following message:

+ +

+ Could not start the Apache2.4 service on \\COMPUTER
+ Error 1067; The process terminated unexpectedly. +

+ +

You will get this generic error if there is any problem with + starting the Apache service. In order to see what is really causing + the problem you should follow the instructions for Running Apache + for Windows from the Command Prompt.

+ +

If you are having problems with the service, it is suggested + you follow the instructions below to try starting httpd.exe from + a console window, and work out the errors before struggling to + start it as a service again.

+
top
+
+

Running Apache as a Console Application

+ + +

Running Apache as a service is usually the recommended way to + use it, but it is sometimes easier to work from the command line, + especially during initial configuration and testing.

+ +

To run Apache from the command line as a console application, + use the following command:

+ +

+ httpd.exe +

+ +

Apache will execute, and will remain running until it is stopped + by pressing Control-C.

+ +

You can also run Apache via the shortcut Start Apache in Console + placed to Start Menu --> Programs --> Apache HTTP Server + 2.4.xx --> Control Apache Server during the installation. + This will open a console window and start Apache inside it. If you + don't have Apache installed as a service, the window will remain + visible until you stop Apache by pressing Control-C in the console + window where Apache is running in. The server will exit in a few + seconds. However, if you do have Apache installed as a service, the + shortcut starts the service. If the Apache service is running + already, the shortcut doesn't do anything.

+ +

If Apache is running as a service, you can tell it to stop by opening another console + window and entering:

+ +

+ httpd.exe -k shutdown +

+ +

Running as a service should be preferred over running in a + console window because this lets Apache end any current operations + and clean up gracefully.

+ +

But if the server is running in a console window, you can + only stop it by pressing Control-C in the same window.

+ +

You can also tell Apache to restart. This forces it to reread + the configuration file. Any operations in progress are allowed to + complete without interruption. To restart Apache, either press + Control-Break in the console window you used for starting Apache, + or enter

+ +

+ httpd.exe -k restart +

+ +

if the server is running as a service.

+ +
Note for people familiar with the Unix version of Apache: + these commands provide a Windows equivalent to kill -TERM + pid and kill -USR1 pid. The + command line option used, -k, was chosen as a reminder + of the kill command used on Unix.
+ +

If the Apache console window closes immediately or unexpectedly + after startup, open the Command Prompt from the Start Menu --> + Programs. Change to the folder to which you installed Apache, type + the command httpd.exe, and read the error message. Then + change to the logs folder, and review the error.log + file for configuration mistakes. Assuming httpd was installed into + C:\Program Files\Apache Software Foundation\Apache2.4\, + you can do the following:

+ +

+ c:
+ cd "\Program Files\Apache Software Foundation\Apache2.4\bin"
+ httpd.exe +

+ +

Then wait for Apache to stop, or press Control-C. Then enter the + following:

+ +

+ cd ..\logs
+ more < error.log +

+ +

When working with Apache it is important to know how it will + find the configuration file. You can specify a configuration file + on the command line in two ways:

+ +
    +

  • -f specifies an absolute or relative path to + a particular configuration file:

    + +

    + httpd.exe -f "c:\my server files\anotherconfig.conf" +

    + +

    or

    + +

    + httpd.exe -f files\anotherconfig.conf +

    • + +

  • -n specifies the installed Apache service + whose configuration file is to be used:

    + +

    + httpd.exe -n "MyServiceName" +

    +
    • +
+ +

In both of these cases, the proper + ServerRoot should be set in + the configuration file.

+ +

If you don't specify a configuration file with -f + or -n, Apache will use the file name compiled into the + server, such as conf\httpd.conf. This built-in path + is relative to the installation directory. You can verify the compiled + file name from a value labelled as SERVER_CONFIG_FILE when + invoking Apache with the -V switch, like this:

+ +

+ httpd.exe -V +

+ +

Apache will then try to determine its ServerRoot by trying the following, in this order:

+ +
    +
  1. A ServerRoot directive + via the -C command line switch.
    2. + +
  2. The -d switch on the command line.
    3. + +
  3. Current working directory.
    4. + +
  4. A registry entry which was created if you did a binary + installation.
    5. + +
  5. The server root compiled into the server. This is + /apache by default, you can verify it by using + httpd.exe -V and looking for a value labelled as + HTTPD_ROOT.
    6. +
+ +

If you did not do a binary install, Apache will in some + scenarios complain about the missing registry key. This warning can + be ignored if the server was otherwise able to find its + configuration file.

+ +

The value of this key is the + ServerRoot directory which + contains the conf subdirectory. When Apache starts it + reads the httpd.conf file from that directory. If + this file contains a ServerRoot + directive which contains a different directory from the one + obtained from the registry key above, Apache will forget the + registry key and use the directory from the configuration file. If + you copy the Apache directory or configuration files to a new + location it is vital that you update the + ServerRoot directive in the + httpd.conf file to reflect the new location.

+
top
+
+

Testing the Installation

+ + +

After starting Apache (either in a console window or as a + service) it will be listening on port 80 (unless you changed the + Listen directive in the + configuration files or installed Apache only for the current user). + To connect to the server and access the default page, launch a + browser and enter this URL:

+ +

+ http://localhost/ +

+ +

Apache should respond with a welcome page and you should see + "It Works!". If nothing happens or you get an error, look in the + error.log file in the logs subdirectory. + If your host is not connected to the net, or if you have serious + problems with your DNS (Domain Name Service) configuration, you + may have to use this URL:

+ +

+ http://127.0.0.1/ +

+ +

If you happen to be running Apache on an alternate port, you + need to explicitly put that in the URL:

+ +

+ http://127.0.0.1:8080/ +

+ +

Once your basic installation is working, you should configure it + properly by editing the files in the conf subdirectory. + Again, if you change the configuration of the Windows NT service + for Apache, first attempt to start it from the command line to + make sure that the service starts with no errors.

+ +

Because Apache cannot share the same port with + another TCP/IP application, you may need to stop, uninstall or reconfigure + certain other services before running Apache. These conflicting + services include other WWW servers, some firewall implementations, + and even some client applications (such as Skype) which will use port + 80 to attempt to bypass firewall issues.

+
top
+
+

Configuring Access to Network Resources

+ + +

Access to files over the network can be specified using two + mechanisms provided by Windows:

+ +
+
Mapped drive letters
+
e.g., Alias "/images/" "Z:/"
+ +
UNC paths
+
e.g., Alias "/images/" "//imagehost/www/images/"
+
+ +

Mapped drive letters allow the administrator to maintain the + mapping to a specific machine and path outside of the Apache httpd + configuration. However, these mappings are associated only with + interactive sessions and are not directly available to Apache httpd + when it is started as a service. Use only UNC paths for + network resources in httpd.conf so that the resources can + be accessed consistently regardless of how Apache httpd is started. + (Arcane and error prone procedures may work around the restriction + on mapped drive letters, but this is not recommended.)

+ +

Example DocumentRoot with UNC path

DocumentRoot "//dochost/www/html/"
+
+ +

Example DocumentRoot with IP address in UNC path

DocumentRoot "//192.168.1.50/docs/"
+
+ +

Example Alias and corresponding Directory with UNC path

Alias "/images/" "//imagehost/www/images/"
+
+<Directory "//imagehost/www/images/">
+#...
+<Directory>
+
+ +

When running Apache httpd as a service, you must create a + separate account in order to access network resources, as described + above.

+
top
+
+

Windows Tuning

+ +
    +

  • If more than a few dozen piped loggers are used on an operating system + instance, scaling up the "desktop heap" is often necessary. For + more detailed information, refer to the piped logging documentation.

    • +
+
+
+

Available Languages:  en  | + fr  | + ko 

+
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 diff --git a/docs/manual/platform/windows.html.fr.utf8 b/docs/manual/platform/windows.html.fr.utf8 new file mode 100644 index 0000000..57ea9aa --- /dev/null +++ b/docs/manual/platform/windows.html.fr.utf8 @@ -0,0 +1,718 @@ + + + + + +Utilisation du serveur HTTP Apache sous Microsoft Windows - Serveur HTTP Apache Version 2.4 + + + + + + +
+

Modules | Directives | FAQ | Glossaire | Plan du site

+

Serveur HTTP Apache Version 2.4

+
+
<-
+

Utilisation du serveur HTTP Apache sous Microsoft Windows

+
+

Langues Disponibles:  en  | + fr  | + ko 

+
+ + +

Ce document d챕crit l'installation, la configuration et + l'ex챕cution d'Apache 2.4 sous Microsoft Windows. Si vous avez des + questions apr챔s avoir lu la documentation, ou si vous avez rencontr챕 + des 챕v챔nements particuliers ou des rapports d'erreur, vous pouvez + consultez la liste + de diffusion de la communaut챕 des utilisateurs.

+ +

Dans ce document, nous supposons que vous installez une + distribution binaire d'Apache. Si vous voulez compiler Apache + vous-m챗me (par exemple pour aider au d챕veloppement ou pour + rechercher des bogues), r챕f챕rez-vous au document Compilation d'Apache pour Microsoft + Windows.

+ +
+ +
top
+
+

Pr챕requis du syst챔me d'exploitation

+ + +

La plate-forme Windows de base pour l'ex챕cution d'Apache 2.4 est + Windows 2000 ou sup챕rieur. Veillez 횪 toujours vous procurer et installer le + dernier service pack afin d'챕viter les bogues du syst챔me + d'exploitation.

+ +
Les versions du serveur HTTP Apache sup챕rieures 횪 2.2 ne + fonctionneront sous aucun syst챔me d'exploitation d'une version + ant챕rieure 횪 Windows 2000.
+ +
top
+
+

T챕l챕chargement d'Apache pour Windows

+ + +

Le projet du serveur HTTP Apache proprement dit ne fournit pas de + distribution binaire mais seulement le code source. Certains membres + du projet peuvent mettre 횪 disposition des paquets binaires + 횪 titre individuel, mais ceux-ci n'ont pas vocation 횪 챗tre + distribu챕s publiquement.

+ +

Si vous n'챗tes + pas en mesure de compiler le serveur HTTP Apache vous-m챗me, vous + pouvez vous procurer un paquet binaire aupr챔s des nombreuses + distributions disponibles sur Internet.

+ +

Quelques solutions populaires pour d챕ployer Apache httpd, et + 챕ventuellement PHP et MySQL sous Microsoft Windows :

+ +
top
+
+

Personnaliser Apache pour Windows

+ + +

La configuration d'Apache est enregistr챕e dans les fichiers du + sous-r챕pertoire conf. Ce sont les m챗me fichiers que + ceux utilis챕s pour configurer la version Unix, mais il y a quelques + directives sp챕cifiques 횪 Apache pour Windows. Voir l'index des directives pour la liste + des directives disponibles.

+ +

Les principales sp챕cificit챕s d'Apache pour Windows sont :

+
    +

  • Comme Apache pour Windows est un programme multithread, il + ne lance pas de processus s챕par챕 pour chaque requ챗te, comme Apache + peut le faire sous Unix. En fait, il n'y a en g챕n챕ral que deux + processus Apache en ex챕cution : un processus parent, et un + processus enfant qui traite les requ챗tes. Chaque requ챗te est + trait챕e par un thread s챕par챕 au sein du processus enfant.

    + +

    Les directives de gestion de processus diff챔rent 챕galement :

    + +

    MaxConnectionsPerChild + : comme dans la version Unix, cette directive contr척le le nombre + de connexions qu'un + processus enfant particulier va traiter avant de s'arr챗ter. + Cependant, 횪 la diff챕rence d'Unix, un processus de remplacement + n'est pas instantan챕ment disponible. Utilisez la d챕finition par + d챕faut MaxConnectionsPerChild 0, sauf si vous + risquez de manquer de m챕moire dans des modules tiers ou dans des + applications in-process.

    + +
    Attention : le fichier de + configuration du serveur est recharg챕 lorsqu'un nouveau processus + enfant est d챕marr챕. En cons챕quence, si vous avez modifi챕 + httpd.conf, le nouveau processus enfant peut ne pas + d챕marrer, ou vous pouvez obtenir des r챕sultats + inattendus.
    + +

    ThreadsPerChild : il + s'agit d'une nouvelle directive. Elle indique au serveur le nombre + de threads qu'il doit utiliser. Elle d챕finit le nombre maximum de + connexions simultan챕es que le serveur peut g챕rer ; vous devez + donc vous assurer que ce nombre soit suffisamment grand pour les + besoins de votre site. La valeur par d챕faut ThreadsPerChild + 150 est recommand챕e, mais doit 챗tre ajust챕e 횪 la valeur + maximale estim챕e de connexions simultan챕es 횪 accepter.

    • + +

  • Les directives qui acceptent des noms de fichiers comme + arguments doivent utiliser des noms de fichiers Windows et non + Unix. Cependant, comme Apache peut interpr챕ter les anti-slashes + comme des s챕quences d'챕chappement de caract챔res, vous devez + absolument utiliser des slashes dans les noms de chemins 횪 la + place des anti-slashes.

    • + +

  • Alors que les noms de fichiers sont en g챕n챕ral insensibles + 횪 la casse sous Windows, les URLs sont encore sensibles 횪 la casse + en interne avant d'챗tre mises en correspondance avec le syst챔me de + fichiers. Par exemple, les directives <Location>, Alias, et ProxyPass utilisent toutes des + arguments sensibles 횪 la casse. Pour cette raison, il est + particuli챔rement recommand챕 d'utiliser la directive <Directory> lorsqu'on + d챕sire limiter l'acc챔s 횪 certains contenus du syst챔me de fichiers, + car cette directive s'applique 횪 tout contenu d'un r챕pertoire, + sans tenir compte de la mani챔re dont on y acc챔de. Pour vous + assurer que seules des minuscules sont utilis챕es dans les URLs, + vous pouvez utiliser ceci :

    + + 
    RewriteEngine On
+RewriteMap lowercase int:tolower
+RewriteCond "%{REQUEST_URI}" "[A-Z]"
+RewriteRule "(.*)" "${lowercase:$1}" [R,L]
    +
    • + +

  • Lors de son ex챕cution, Apache n'a besoin d'un acc챔s en + 챕criture qu'au r챕pertoire des journaux et 횪 toute arborescence de + r챕pertoires de cache configur챕e. Suite au probl챔me d'insensibilit챕 + 횪 la casse et au format de noms courts 8.3, Apache doit valider + tous les noms de chemins fournis. Cela signifie que chaque + r챕pertoire qu'Apache 챕value doit avoir les droits en lecture, + listage et parcours, et ceci depuis la racine jusqu'aux feuilles. + Si Apache2.4 est install챕 dans C:\Program Files, le r챕pertoire + racine, Program Files et Apache2.4 doivent tous 챗tre visibles pour + Apache

    • + +

  • Apache peut charger divers modules sans qu'il soit n챕cessaire + de recompiler le serveur. Si Apache est compil챕 + normalement, il va installer de nombreux modules optionnels dans + le r챕pertoire \Apache2.4\modules. Pour activer ces + modules ou d'autres modules, on doit utiliser la + directive LoadModule. Par + exemple, pour activer le module status, ajoutez la ligne suivante + (en plus des directives d'activation de status dans + access.conf) :

    + + 
    LoadModule status_module modules/mod_status.so
    + + +

    Des informations sont aussi 횪 votre disposition pour cr챕er des modules + chargeables

    • + +

  • Apache peut aussi charger des extensions ISAPI (Internet + Server Application Programming Interface), comme celles qu'utilise + Microsoft IIS et d'autres serveurs Windows. Voir ici pour plus + d'informations. Notez qu'Apache ne peut pas + charger de filtres ISAPI, et que les gestionnaires ISAPI contenant + des extensions de fonctionnalit챕s Microsoft ne fonctionneront + pas.

    • + +

  • Pour les scripts CGI, la m챕thode qu'utilise Apache pour + d챕terminer l'interpr챕teur du script est configurable gr창ce 횪 la + directive ScriptInterpreterSource

    • + +

  • Comme il est souvent difficile de g챕rer des fichiers avec + des noms du style .htaccess sous Windows, vous avez + tout int챕r챗t 횪 changer le nom de ce fichier de configuration par + r챕pertoire 횪 l'aide de la directive AccessFilename.

    • + +

  • Toute erreur survenant au cours du processus de d챕marrage + d'Apache est enregistr챕e dans le journal des 챕v챔nements de + Windows si l'on est sous Windows NT. Ce m챕canisme fonctionne comme + une sauvegarde pour les situations o첫 Apache n'est pas encore pr챗t + 횪 utiliser le fichier error.log. Vous pouvez + consulter le journal des 챕v챔nements applicatifs Windows en + utilisant l'observateur d'챕v챔nements : D챕marrage - Param챔tres - + Panneau de configuration - Outils d'administration - Observateur + d'챕v챔nements.

    • +
+ +
top
+
+

Ex챕cuter Apache en tant que service

+ + +

Apache fournit un utilitaire nomm챕 Apache Service Monitor + (Moniteur du service Apache). Gr창ce 횪 lui, vous pouvez voir et g챕rer + l'챕tat de tous les services Apache install챕s sur toutes les machines + du r챕seau. Pour pouvoir g챕rer un service Apache avec le moniteur, + vous devez d'abord installer le service (soit automatiquement au + cours de l'installation, soit manuellement).

+ +

Vous pouvez installer Apache en tant que service Windows NT 횪 + partir de la ligne de commandes et depuis le sous-r챕pertoire Apache + bin comme suit :

+ +

+ httpd.exe -k install +

+ +

Si vous avez install챕 plusieurs services Apache sur votre + ordinateur, vous devrez sp챕cifier le nom du service que vous voulez + installer en utilisant la commande suivante (notez que si vous + sp챕cifiez un nom durant l'installation, vous devrez aussi le + sp챕cifier pour toute op챕ration comportant l'option -k) :

+ +

+ httpd.exe -k install -n "Nom-service" +

+ +

Si un service doit utiliser un fichier de configuration + sp챕cifique, utilisez ceci :

+ +

+ httpd.exe -k install -n "Nom-service" -f "c:\fichiers\Nom-service.conf" +

+ +

Si vous utilisez la premi챔re commande sans param챔tre particulier, + except챕 -k install, le service aura pour nom + Apache2.4 et le fichier de configuration sera cens챕 + 챗tre conf\httpd.conf.

+ +

Supprimer un service Apache est tr챔s simple. Utilisez + simplement :

+ +

+ httpd.exe -k uninstall +

+ +

On peut sp챕cifier un service Apache particulier en utilisant + :

+ +

+ httpd.exe -k uninstall -n "Nom service" +

+ +

Normalement, le d챕marrage, le red챕marrage et l'arr챗t d'un + service Apache s'effectuent via le Moniteur de Service Apache, ou en + utilisant des commandes telles que NET START Apache2.4 et + NET STOP Apache2.4, ou encore via le gestionnaire de + services standard de Windows. Avant de d챕marrer Apache en tant que + service dans quelque but que ce soit, vous devez tester le fichier + de configuration du service en utilisant :

+ +

+ httpd.exe -n "Nom-service" -t +

+ +

Vous pouvez aussi contr척ler un service Apache 횪 l'aide de ses + options de ligne de commande. Avec cette m챕thode, pour d챕marrer un + service Apache install챕, vous utiliserez :

+ +

+ httpd.exe -k start -n "Nom-Service" +

+ +

Pour arr챗ter un service Apache via les options de lignes de + commande, utilisez ceci :

+ +

+ httpd.exe -k stop -n "Nom-Service" +

+ +

ou

+ +

+ httpd.exe -k shutdown -n "Nom-Service" +

+ +

Vous pouvez aussi red챕marrer un service en ex챕cution et le forcer + 횪 relire son fichier de configuration en utilisant :

+ +

+ httpd.exe -k restart -n "Nom-Service" +

+ +

Par d챕faut, tous les services Apache sont configur챕s pour + s'ex챕cuter sous l'utilisateur system (le compte + LocalSystem). Le compte LocalSystem n'a + pas de privil챔ges sur votre r챕seau, que ce soit via un m챕canisme + s챕curis챕 de Windows, y compris le syst챔me de fichiers, des tubes + nomm챕s, DCOM ou des RPC s챕curis챕s. Il a cependant des privil챔ges + 챕lev챕s en local.

+ +
N'accordez jamais de privil챔ges r챕seau + au compte LocalSystem ! Si Apache doit pouvoir acc챕der + 횪 des ressources r챕seau, cr챕ez un compte s챕par챕 pour Apache comme + indiqu챕 ci-dessous.
+ +

Il est fortement fortement conseill챕 aux utilisateurs de cr챕er un + compte s챕par챕 pour ex챕cuter le(s) service(s) Apache, et m챗me + obligatoire si vous devez acc챕der 횪 des ressources r챕seau via + Apache.

+ +
    +
  1. Cr챕ez un compte d'utilisateur du domaine normal, et + assurez-vous de retenir son mot de passe.
    2. + +
  2. Accordez 횪 l'utilisateur nouvellement cr챕챕 les privil챔ges + Log on as a service et Act as part of the + operating system. Sous Windows NT 4.0, ces privil챔ges sont + accord챕s via le Gestionnaire des utilisateurs du Domaine, mais + sous Windows 2000 et XP, vous aurez plut척t int챕r챗t 횪 utiliser une + GPO pour propager ces configurations. Vous pouvez aussi effectuer + ces r챕glages via la Politique de S챕curit챕 Locale int챕gr챕e 횪 la + MMC.
    3. + +
  3. V챕rifiez que le compte nouvellement cr챕챕 est membre du groupe + Utilisateurs
    4. + +
  4. Accordez 횪 ce compte les droits Lecture et Ex챕cution (RX) sur + tous les documents et r챕pertoires de scripts (htdocs + et cgi-bin par exemple), et aussi sur l'ex챕cutable + binaire httpd.exe.
    5. + +
  5. Accordez aussi 횪 ce compte les droits de modification sur le + r챕pertoire logs.
    6. + +
+ +
Il est en g챕n챕ral de bonne pratique d'accorder 횪 l'utilisateur + sous lequel le service Apache s'ex챕cute les droits en lecture et + ex챕cution (RX) sur l'ensemble du r챕pertoire Apache2.4, sauf pour le + sous-r챕pertoire logs, sur lequel l'utilisateur doit + avoir au moins les droits de modification (RWXD).
+ +

Si vous permettez 횪 ce compte de se connecter en tant + qu'utilisateur et service, vous pouvez ouvrir une session sous ce + compte et v챕rifier s'il a bien le droit d'ex챕cuter les scripts, de + lire les pages web, et si vous pouvez d챕marrer Apache 횪 partir d'une + console Windows. Si tout fonctionne, et si vous avez suivi les + 챕tapes ci-dessus, Apache devrait s'ex챕cuter en tant que service sans + probl챔me.

+ +
Le code d'erreur 2186 indique probablement + qu'Apache ne peut pas acc챕der 횪 une ressource r챕seau n챕cessaire, et + que vous devez revoir la configuration "Log On As" (Se connecter en + tant que ...) du service.
+ +

Lorsqu'Apache d챕marre en tant que service, il se peut que vous + obteniez un message d'erreur du Gestionnaire de Services Windows. + Par exemple, si vous essayez de d챕marrer Apache en utilisant + l'applet Services du Panneau de configuration de Windows, vous + pouvez obtenir le message suivant :

+ +

+ Could not start the Apache2.4 service on \\COMPUTER
+ Error 1067; The process terminated unexpectedly. +

+ +

Vous obtiendrez cette erreur 횪 caract챔re g챕n챕ral pour tout + probl챔me survenant au cours du d챕marrage du service Apache. Afin de + d챕terminer exactement la cause du probl챔me, vous devez suivre les + instructions permettant d'ex챕cuter Apache pour Windows depuis la + ligne de commande.

+ +

Si vous rencontrez des probl챔mes avec le service, il est + conseill챕 de suivre les instructions ci-dessous afin d'essayer de + d챕marrer httpd.exe depuis une console, et d'analyser les erreurs + plut척t que vous d챕mener 횪 essayer de d챕marrer le service.

+ +
top
+
+

Ex챕cuter Apache depuis la console

+ + +

Il est en g챕n챕ral recommand챕 d'ex챕cuter Apache en tant que + service, mais il est parfois plus simple d'utiliser la ligne de + commande, en particulier au cours de la configuration initiale et + les tests.

+ +

Pour ex챕cuter Apache depuis la ligne de commande et en tant + qu'application de console, utilisez la commande suivante :

+ +

+ httpd.exe +

+ +

Apache va d챕marrer, et continuera son ex챕cution jusqu'횪 ce qu'on + l'arr챗te en tapant Ctrl-C.

+ +

Vous pouvez 챕galement d챕marrer Apache via le raccourci "D챕marrer + Apache dans une console" plac챕 dans D챕marrer --> + Programmes --> Apache HTTP Server 2.4.xx --> Control Apache + Server au cours de l'installation. Ceci va + ouvrir une console Windows, et y d챕marrer Apache. + Si vous n'avez pas install챕 Apache en tant que service, la + fen챗tre Windows restera ouverte jusqu'횪 ce que vous arr챗tiez Apache + en tapant Ctrl-C dans cette fen챗tre. Le serveur va alors s'arr챗ter + au bout de quelques secondes. Cependant, si vous avez install챕 + Apache en tant que service, c'est ce dernier que le raccourci + ci-dessus va lancer. Si le service Apache est d챕j횪 en cours + d'ex챕cution, le raccourci va rester sans effet.

+ +

Si Apache s'ex챕cute en tant que service, vous pouvez l'arr챗ter en + ouvrant une autre console et en entrant :

+ +

+ httpd.exe -k shutdown +

+ +

Plut척t que de lancer Apache 횪 partir d'une console, il est + pr챕f챕rable de l'ex챕cuter en tant que service car dans ce cas, il + termine proprement les op챕rations en cours avant de s'챕teindre.

+ +

Si le serveur a 챕t챕 lanc챕 depuis une console, vous ne pouvez + l'arr챗ter qu'en pressant la combinaison de touches Ctrl-C dans la + m챗me fen챗tre.

+ +

Vous pouvez aussi red챕marrer Apache. Ceci le force 횪 recharger + son fichier de configuration. Toute op챕ration en cours peut 챗tre + achev챕e sans interruption. Pour red챕marrer Apache, vous pouvez soit + taper Control-Break dans la fen챗tre de console que vous avez + utilis챕e pour le d챕marrer, soit entrer :

+ +

+ httpd.exe -k restart +

+ +

si le serveur s'ex챕cute en tant que service.

+ +
Note pour les utilisateurs familiers de la version Unix + d'Apache : les commandes ci-dessus repr챕sentent pour Windows + l'챕quivalent des commandes kill -TERM pid et + kill -USR1 pid. L'option de ligne de commande + -k a 챕t챕 choisie 횪 titre de rapprochement avec la + commande kill utilis챕e sous Unix.
+ +

Si la fen챗tre de la console Apache se ferme imm챕diatement ou + inopin챕ment apr챔s le d챕marrage d'Apache, ouvrez une console Windows + depuis le menu D챕marrer --> Programmes. Placez-vous dans le + r챕pertoire d'installation d'Apache, tapez la commande + httpd.exe, et observez le message d'erreur. Allez + ensuite dans le r챕pertoire des journaux, et visualisez le fichier + error.log pour d챕tecter d'챕ventuelles erreurs de + configuration. Si Apache a 챕t챕 install챕 dans C:\Program + Files\Apache Software Foundation\Apache2.4\, vous + pouvez entrer ce qui suit :

+ +

+ c:
+ cd "\Program Files\Apache Software Foundation\Apache2.4\bin"
+ httpd.exe +

+ +

Attendez ensuite qu'Apache s'arr챗te ou tapez Ctrl-C. Entrez alors + la commande suivante :

+ +

+ cd ..\logs
+ more < error.log +

+ +

Lorsqu'on travaille avec Apache, il est important de comprendre + comment ce dernier trouve son fichier de configuration. Vous pouvez + sp챕cifier un fichier de configuration 횪 partir de la ligne de + commande de deux fa챌ons :

+ +
    +

  • L'option -f permet de sp챕cifier un chemin + absolu ou relatif vers un fichier de configuration particulier + :

    (sous Windows 9x, il est recommand챕 d'utiliser la ligne de + commande 횪 cause du manque de fiabilit챕 du support des services + fourni par ce syst챔me). + +

    + httpd.exe -f "c:\fichiers-de-mon-serveur\autre-config.conf" +

    + +

    ou

    + +

    + httpd.exe -f fichiers-de-mon-serveur\autre-config.conf +

    • + +

  • L'option -n permet de sp챕cifier le service + Apache install챕 dont le fichier de configuration doit 챗tre utilis챕 + :

    + +

    + httpd.exe -n "Nom-service" +

    +
    • +
+ +

Dans les deux cas, la directive ServerRoot doit 챗tre correctement d챕finie + dans le fichier de configuration.

+ +

Si vous ne sp챕cifiez aucun fichier de configuration 횪 l'aide des + options -f ou -n, Apache utilisera le nom + du fichier de configuration compil챕 dans le serveur, en g챕n챕ral + conf\httpd.conf. Ce chemin cod챕 en dur est relatif au + r챕pertoire d'installation. Vous pouvez v챕rifier ce chemin 횪 partir + de la valeur de l'챕tiquette SERVER_CONFIG_FILE en + invoquant Apache avec l'option -V, comme ceci :

+ +

+ httpd.exe -V +

+ +

Apache va ensuite essayer de d챕terminer la valeur de son + ServerRoot en effectuant les + recherches suivantes, dans cet ordre :

+ +
    +
  1. Une directive ServerRoot + via l'option de ligne de commande -C.
    2. + +
  2. L'option de ligne de commande -d.
    3. + +
  3. Le r챕pertoire de travail courant.
    4. + +
  4. Une entr챕e de la base de registre cr챕챕e dans le cas d'une + installation binaire.
    5. + +
  5. La racine des documents (DocumentRoot) cod챕e en dur + dans le serveur. Elle + correspond par d챕faut 횪 /apache, et vous pouvez le + v챕rifier en tapant httpd.exe -V et en recherchant + l'챕tiquette HTTPD_ROOT.
    6. +
+ +

Si vous n'avez pas effectu챕 d'installation binaire, dans certains + sc챕narios, Apache va signaler l'absence de cette cl챕 de registre. + On peut passer outre cet avertissement si le serveur a 챕t챕 en mesure + de trouver son fichier de configuration d'une autre mani챔re.

+ +

La valeur de cette cl챕 correspond au r챕pertoire ServerRoot qui contient lui-m챗me le + sous-r챕pertoire conf. Lors de son d챕marrage, Apache lit + le fichier httpd.conf 횪 partir de ce r챕pertoire. Si ce + fichier contient une directive ServerRoot qui sp챕cifie un r챕pertoire + diff챕rent de celui que contient la cl챕 de registre ci-dessus, Apache + oubliera la cl챕 de registre, et utilisera le r챕pertoire sp챕cifi챕 par + le fichier de configuration. Si vous d챕placez le r챕pertoire Apache + ou ses fichiers de configuration, il est vital de mettre 횪 jour la + directive ServerRoot dans + httpd.conf afin de refl챕ter la nouvelle + localisation.

+ +
top
+
+

V챕rification de l'installation

+ + +

Une fois Apache d챕marr챕 (soit 횪 partir d'une console Windows, + soit en tant que service), ce dernier va se mettre 횪 l'챕coute sur + le port 80 (횪 moins que vous ayiez modifi챕 la directive Listen dans les fichiers de + configuration ou que vous ayiez install챕 Apache pour l'utilisateur + courant seulement). Pour vous connecter au serveur et acc챕der 횪 la + page par d챕faut, lancez un navigateur et entrez cette URL :

+ +

+ http://localhost/ +

+ +

Apache devrait renvoyer une page de bienvenue et vous devriez + voir s'afficher "It Works!". Si rien ne se passe ou si vous obtenez + une erreur, consultez le fichier error.log dans le + sous-r챕pertoire logs. Si votre serveur n'est pas + connect챕 au r챕seau, ou si vous avez de s챕rieux probl챔mes avec la + configuration de votre DNS (Domain Name Service), vous devez + utiliser cette URL :

+ +

+ http://127.0.0.1/ +

+ +

Si Apache 챕coute un port non standard, vous devez le pr챕ciser + explicitement dans l'URL :

+ +

+ http://127.0.0.1:8080/ +

+ +

Apr챔s que votre installation de base fonctionne, vous devez la + configurer correctement en 챕ditant les fichiers du sous-r챕pertoire + conf. Encore une fois, si vous modifiez la + configuration du service Apache sous Windows NT, essayez d'abord de + red챕marrer le service depuis la ligne de commande afin de vous + assurer de l'absence d'erreur.

+ +

Comme Apache ne peut pas partager le m챗me port + avec d'autres applications TCP/IP, il se peut que vous soyez amen챕 횪 + arr챗ter, d챕sinstaller ou reconfigurer certains services avant de + d챕marrer Apache. Ces services entrant en conflit avec Apache + comprennent les autres serveurs WWW, certaines impl챕mentations de + pare-feu, et m챗me certaines applications client (comme Skype) qui + utilisent le port 80 afin de contourner les pare-feu.

+ +
top
+
+

Configuration de l'acc챔s aux ressources r챕seau

+ + +

L'acc챔s 횪 des fichiers par le r챕seau peut 챗tre sp챕cifi챕 via deux + m챕canismes fournis par Windows :

+ +
+
Association de lettres de lecteur
+
Par exemple, Alias "/images/" "Z:/"
+ +
chemins UNC
+
Par exemple, Alias "/images/" "//imagehost/www/images/"
+
+ +

L'association de lettres de lecteur permet 횪 l'administrateur de + maintenir une correspondance avec une certaine machine et un certain + chemin en dehors de la configuration d'Apache httpd. Cependant, ces + associations ne sont possibles que dans le cadre des sessions + interactives, et ne sont pas directement disponibles pour Apache httpd + lorsqu'il est d챕marr챕 en tant que service. N'utilisez par + cons챕quent que des + chemins UNC pour les ressources r챕seau dans httpd.conf, de + fa챌on 횪 ce que les ressources soient accessibles quelle que soit la + mani챔re dont Apache httpd a 챕t챕 d챕marr챕 (des proc챕dures exotiques et + probablement sujettes aux erreurs peuvent permettre de contourner la + restriction due aux associations de lettres de lecteur, mais leur + utilisation est d챕conseill챕e).

+ +

Exemple de DocumentRoot avec chemin UNC

DocumentRoot "//dochost/www/html/"
+
+ +

Exemple de DocumentRoot avec adresse IP dans le chemin UNC

DocumentRoot "//192.168.1.50/docs/"
+
+ +

Exemple d'Alias et r챕pertoire correspondant avec + chemin UNC

Alias "/images/" "//imagehost/www/images/"
+
+<Directory "//imagehost/www/images/">
+#...
+<Directory>
+
+ +

Lorsqu'Apache s'ex챕cute en tant que service, vous devez cr챕er un + compte sp챕cifique afin de pouvoir acc챕der aux ressources r챕seau, comme + d챕crit ci-dessus.

+
top
+
+

Personnalisation sous Windows

+ +
    +

  • Si on utilise un grand nombre de redirections de journaux + via des pipes, il est souvent n챕cessaire d'augmenter la + taille de la m챕moire du bureau ("desktop heap"). Pour une information plus + d챕taill챕e, veuillez vous reporter 횪 la documentation sur les redirections de journaux.

    • +
+
+
+

Langues Disponibles:  en  | + fr  | + ko 

+
top

Commentaires

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 diff --git a/docs/manual/platform/windows.html.ko.euc-kr b/docs/manual/platform/windows.html.ko.euc-kr new file mode 100644 index 0000000..f05f298 --- /dev/null +++ b/docs/manual/platform/windows.html.ko.euc-kr @@ -0,0 +1,716 @@ + + + + + +Microsoft Windows에서 아파치 사용법 - Apache HTTP Server Version 2.4 + + + + + + +
+

모듈 | 지시어들 | FAQ | 용어 | 사이트맵

+

Apache HTTP Server Version 2.4

+
+
<-
+

Microsoft Windows에서 아파치 사용법

+
+

가능한 언어:  en  | + fr  | + ko 

+
+
이 문서는 최신판 번역이 아닙니다. + 최근에 변경된 내용은 영어 문서를 참고하세요.
+ + +

이 문서는 Microsoft Windows에서 아파치 2.0을 설치, 설정, + 실행하는 방법을 설명한다. 잘못된 부분이 있거나 다른 방법으로 + 도움을 주려면, 버그 보고 + 페이지를 사용하길 바란다.

+ +

이 문서는 아파치 바이너리 배포본을 설치한다고 가정한다. + (아마도 개발 혹은 버그를 찾기위해) 직접 아파치를 컴파일하려면 + Microsoft Windows용 아파치 + 컴파일을 참고하라.

+ +

현재 Microsoft Windows 운영체제군의 버전 정책상 + 이 문서는 다음과 같이 구분한다:

+
    +
  • Windows NT: Windows NT 커널을 기반으로 + 하는 모든 Windows 버전을 의미한다. Windows NT, Windows + 2000, Windows XP, Windows .Net Server 2003을 지칭한다.
    • +
  • Windows 9x: 소비자 중심의 오래된 + Windows 버전을 뜻한다. Windows 95 (OSR2 포함), Windows + 98, Windows ME를 지칭한다.
    • +
+ +
+ +
top
+
+

운영체제 요구조건

+ + +

아파치 2.0을 실행하기위한 기본 Windows 플래폼은 Windows + NT이다. 바이너리 설치프로그램은 Intel과 AMD와 같은 x86 개열 + 프로세서에서만 동작한다. 아파치는 Windows 9x에서 충분히 + 검사하지 않았기때문에 절대로 실제 서비스에 사용하지 않길 + 바란다. +

+ +

운영체제에 설치한 TCP/IP 네트워크가 동작해야 한다. Windows + 95에서 실행한다면, Winsock 2 업그레이드를 설치해야 한다. + Windows 95용 Winsock 2는 여기에서 + 다운받을 수 있다. +

+ +

Windows NT 4.0을 사용한다면 서비스팩 4의 TCP/IP 문제와 + Winsock 문제가 다음 서비스팩에서 해결되었기때문에, 서비스팩 + 6을 설치하길 적극 권한다.

+
top
+
+

Windows용 아파치 다운로드

+ + +

아파치 웹서버 http://httpd.apache.org/download.cgi에서 + 아파치 최신 버전에 대한 정보를 얻을 수 있다. 여기에는 최신 + 발표판과 알파 혹은 베타 테스트버전과, 아파치 웹서버를 다운로드할 + 수 있는 HTTP 미러와 FTP 미러 목록이 있다. 빠르고 안정하게 + 다운받으려면 가까운 미러를 사용하길 바란다.

+ +

Windows에 설치하려면 확장자가 .msi인 Windows용 + 아파치 버전을 다운받아야 한다. 이 파일은 막바로 실행할 수 + 있는 아파치를 저장한 Microsoft 설치파일이다. 따로 소스코드만 + 묶어둔 .zip 파일이 있다. Microsoft Visual C++ + (Visual Studio)을 사용하여 직접 아파치를 컴파일할 수도 있다.

+
top
+
+

Windows용 아파치 설치하기

+ + +

설치하려면 Microsoft Installer 1.2 이상 버전이 필요하다. + Windows 9x를 사용한다면 여기에서 + Microsoft Installer를 2.0 버전으로 업그레이드할 수 있고, + Windows NT 4.0과 2000을 사용한다면 여기에서 + 2.0 버전 업데이트를 구할 수 있다. Windows XP는 업데이트할 + 필요가 없다.

+ +

바이너리 설치파일로는 같은 컴퓨터에 서로 다른 아파치 + 2.0 버전을 설치할 수 없음을 주의하라. 그러나 1.3 + 버전과 2.0 버전은 같은 컴퓨터에 아무 문제없이 + 설치할 수 있다. 같은 컴퓨터에 두가지 다른 2.0 버전을 설치하려면 + 소스를 컴파일하여 아파치를 + 설치해야 한다.

+ +

위에서 다운받은 아파치 .msi 파일을 실행한다. + 설치할때 다음과 같은 것을 물어본다:

+ +
    +

  1. 네트워크 도메인 (Network Domain). + 등록된 서버의 DNS 도메인을 입력한다. 예를 들어, 서버의 + 전체 DNS 이름이 server.mydomain.net이라면 + 여기에 mydomain.net을 입력한다.

    2. + +

  2. 서버명 (Server Name). 서버의 전체 + DNS 이름. 위의 경우 여기에 server.mydomain.net을 + 입력한다.

    3. + +

  3. 관리자 전자우편 주소 (Administrator's Email + Address). 여기에 서버 관리자나 웹마스터의 전자우편 + 주소를 입력한다. 기본적으로 클라이언트에게 보내는 오류문에 + 이 주소를 기록한다.

    4. + +

  4. 사용자 대상 (For whom to install + Apache) 새로 설치하는 아파치가 80번 포트에서 + 요청을 기다리게 하려면 for All Users, on Port 80, + as a Service - Recommended (모든 사용자, 80번 포트, + service로 - 추천)를 선택한다. 아파치를 service로 실행한다 + (즉, 아파치는 서버에 로그인한 사람이 없어도 실행된다). + 개인적으로 테스트해보거나 이미 80번 포트를 사용하는 다른 + 웹서버가 있다면 only for the Current User, on Port + 8080, when started Manually (현재 사용자만, 8080번 + 포트, 직접 시작)를 선택한다.

    5. + +

  5. 설치 종류 (The installation type). + 모듈 개발에 필요한 소스코드와 라이브러리를 제외한 모든 + 것을 설치하려면 Typical을 선택한다. + Custom을 선택하면 설치할 내용을 지정할 수 + 있다. 전체 설치시 디스크에 빈 공간이 약 13 메가바이트 + 정도 필요하다. 이 수치는 웹사이트 크기를 제외한 + 것이다.

    6. + +

  6. 설치 장소 (Where to install). + 기본 경로는 C:\Program Files\Apache Group이고, + 이곳에 Apache2라는 디렉토리를 만든다.

    7. +
+ +

설치할 동안 아파치는 conf 하위디렉토리에 + 있는 파일들을 선택한 설치 디렉토리에 맞게 구성한다. 그러나 + 이 디렉토리에 설정파일이 이미 있다면 그대로 둔다. 대신, + 해당 파일의 새로운 복사본에 확장자 .default를 + 붙인다. 예를 들어, conf\httpd.conf가 이미 있다면 + conf\httpd.conf.default로 이름을 변경한다. + 설치후 .default 파일의 설정을 직접 살펴보고, + 필요하다면 기존 설정파일을 수정해야 한다.

+ +

또, 이미 htdocs\index.html이라는 파일이 + 있다면 그대로 둔다 (index.html.default라고 + 복사하지도 않는다). 즉, 기존에 아파치가 설치되있더라도 안전하게 + 아파치를 새로 설치할 수 있다. 물론 설치하기 전에 서버를 + 중단하고, 설치후 새로운 서버를 시작해야 한다.

+ +

아파치 설치후 필요하다면 conf 하위디렉토리에 + 있는 설정파일을 수정해야 한다. 파일은 아파치를 설치한 디렉토리의 + htdocs 하위디렉토리에 있는 문서를 서비스하도록 + 설정되있다. 실제로 아파치를 사용하기 전에 설정해야 할 옵션이 + 많다. 그러나 빨리 실행해볼 수 있도록 기본 설정파일로도 동작한다.

+
top
+
+

Windows용 아파치 설정하기

+ + +

아파치는 conf 하위디렉토리에 있는 파일로 + 설정한다. 이 파일은 유닉스용과 같지만, Windows용 아파치 + 특유의 지시어가 몇개 있다. 사용가능한 모든 지시어를 보려면 + 지시어 목록을 참고하라.

+ +

Windows용 아파치의 주된 차이점은:

+
    +

  • Windows용 아파치는 다중쓰레드 방식을 사용하기때문에, + 유닉스와 달리 요청마다 다른 프로세스를 사용하지 않는다. + 대신 아파치 프로세스는 항상, 부모 프로세스와 요청을 처리하는 + 자식 프로세스, 2개이다. 자식 프로세스에 있는 여러 쓰레드들이 + 요청들을 처리한다. +

    + +

    프로세스 관리 지시어도 다르다:

    + +

    MaxRequestsPerChild: 유닉스와 + 같이, 자식 프로세스가 요청을 얼마만큼 처리하고 죽을지를 + 조정한다. 그러나 유닉스와 달리 프로세스가 한번에 한 요청만을 + 처리하지않고 한번에 모든 요청을 서비스하기때문에, 설정한다면 + 매우 큰 값을 설정하길 권한다. 권장하는 기본값 + MaxRequestsPerChild 0을 사용하면 자식 프로세스는 + 죽지않고 영원히 요청을 서비스한다.

    + +
    경고: 자식 프로세스는 새로 + 시작할 때마다 서버설정파일을 새로 읽는다. + httpd.conf를 수정했다면, 자식 프로세스가 + 시작하지 않거나 예기치않은 결과가 발생할 수 있다.
    + +

    ThreadsPerChild: + 이 지시어는 새로 추가되었다. 이 지시어는 서버가 사용할 + 쓰레드 개수를 지정한다. 이 값이 서버가 한번에 처리할 수 + 있는 최대 연결개수이기때문에, 사이트에 접속량이 많다면 + 충분히 큰 값을 설정해야 한다. 권장하는 기본값은 + ThreadsPerChild 50이다.

    • + +

  • 파일명을 아규먼트로 받는 지시어는 유닉스 파일명이 + 아닌 Windows 파일명을 사용해야 한다. 그러나 아파치 내부에서 + 유닉스식 이름을 사용하기때문에 백슬래쉬가 아닌 슬래쉬를 + 사용해야 한다. 드라이브 문자를 사용할 수 있다. 드라이브를 + 지정하지 않으면 아파치 실행파일이 있는 드라이브를 + 사용한다.

    • + +

  • Windows용 아파치는 서버를 다시 컴파일하지 않고 + 실행중에 모듈을 읽어들일 수 있다. 기본값으로 아파치를 + 컴파일하면 \Apache2\modules 디렉토리에 여러 + 선택가능한 모듈을 설치한다. 이 모듈 혹은 다른 모듈을 + 사용하려면 새로 생긴 LoadModule 지시어를 사용한다. + 예를 들어, status 모듈을 사용한다면 + (access.conf에 status관련 지시어와 함께) + 아래와 같이 설정한다:

    + +

    + LoadModule status_module modules/mod_status.so +

    + +

    읽어들일 수 있는 + 모듈 만들기에 대한 정보도 있다.

    • + +

  • 아파치는 Microsoft IIS와 다른 Windows 서버가 사용하는 + ISAPI (Internet Server Application Programming Interface) + 확장을 (즉, 인터넷 서버 프로그램) 읽어들일 수도 있다. + 더 자세한 정보가 있다. + 아파치는 ISAPI 필터를 읽어들일 수 없음을 + 주의하라.

    • + +

  • CGI 스크립트를 사용한다면 ScriptInterpreterSource 지시어를 + 사용하여 아파치가 스크립트의 인터프리터를 찾는 방법을 + 설정할 수 있다.

    • + +

  • Windows에서 .htaccess와 같은 파일명을 + 다루기 힘드므로, AccessFilename 지시어를 사용하여 + 디렉토리별 설정파일 이름을 변경하면 편하다.

    • + +

  • Windows NT라면 아파치 시작시 발생한 오류를 Windows + 이벤트 로그에 기록한다. 그래서 아파치가 보통 사용하는 + error.log 파일을 사용할 수 없는 경우에 대비한다. + Windows 이벤트 로그는 Windows NT 4.0에서는 이벤트 뷰어 + 프로그램으로, 최신 Windows 버전에서는 이벤트 뷰어 MMC + 스냅인에서 볼 수 있다.

    + +
    Windows 9x에는 Windows 이벤트 로그가 없기때문에 + 시작시 발생한 오류를 기록하지 않는다.
    • +
+ +
top
+
+

아파치를 Service로 실행하기

+ + +

Windows NT에서는 아파치를 service로 실행할 수 있다. Windows + 9x에는 매우 실험적인 방법으로 비슷한 기능을 지원한다.

+ +

설치시 자동으로 아파치를 service로 설치할 수 있다. "모든 + 사용자"를 선택하면, 아파치 service가 만들어진다. "현재 + 사용자만"을 선택하더라도 설치후 직접 아파치를 service로 + 등록할 수 있다. service를 설치하려면 Administrators 그룹의 + 구성원이어야 한다.

+ +

아파치에는 Apache Service Monitor라는 도구가 있다. 이 + 도구를 사용하면 네트웍에 있는 다른 컴퓨터에 설치된 아파치 + 상태도 확인하고 관리할 수 있다. monitor로 아파치 service를 + 관리하려면 먼저 service를 (설치시 자동으로 혹은 직접) 설치해야 + 한다. +

+ +

아파치 bin 하위디렉토리에서 명령행 프롬프트에 + 다음과 같이 입력하면 아파치를 Windows NT service로 설치한다:

+ +

+ apache -k install +

+ +

설치할 service 이름을 지정하고 싶다면 다음 명령어를 사용한다. + 컴퓨터에 아파치가 여러개 설치되있다면 이름을 다르게 주어야 + 한다.

+ +

+ apache -k install -n "MyServiceName" +

+ +

service가 사용할 설정파일을 직접 지정하려면 다음과 같이 + 한다:

+ +

+ apache -k install -n "MyServiceName" -f "c:\files\my.conf" +

+ +

-k install 외에 다른 파라미터를 사용하지 + 않으면, service 이름은 Apache2가 되고 설정파일은 + conf\httpd.conf가 된다. +

+ +

아파치 service를 제거하기 쉽다. 간단히:

+ +

+ apache -k uninstall +

+ +

다음과 같이 제거할 아파치 service를 지정할 수 있다:

+ +

+ apache -k uninstall -n "MyServiceName" +

+ +

보통 아파치 service 시작, 재시작, 종료는 Apache Service + Monitor나 NET START Apache2, NET STOP + Apache2 같은 명령어 혹은 Windows 서비스 관리창에서 + 한다. 어떤 방법을 사용하든지 아파치 service를 시작하기 전에 + 설정파일을 검사해봐야 한다:

+ +

+ apache -n "MyServiceName" -t +

+ +

명령행 옵션으로도 아파치 service를 조정할 수 있다. 설치한 + 아파치 serivce를 시작하려면:

+ +

+ apache -k start +

+ +

명령행 옵션으로 아파치 service를 종료하려면:

+ +

+ apache -k stop +

+ +

혹은

+ +

+ apache -k shutdown +

+ +

실행중인 service를 재시작하여 설정파일을 다시 읽도록 + 할 수 있다:

+ +

+ apache -k restart +

+ +

기본적으로 모든 아파치 service는 시스템 사용자 + (LocalSystem 계정) 권한으로 실행하도록 등록된다. + Windows 보안구조상 LocalSystem 계정은 파일시스템, + named pipes, DCOM, secure RPC 등 어떤 방법을 사용하든지 + 네트웍에 접근할 수 없다. 그러나 해당 컴퓨터에서는 많은 권한을 + 가진다. +

+ +
LocalSystem 계정에게 + 네트웍 권한을 절대로 주지 마라! 아파치가 네트웍 자원에 접근해야 + 한다면, 아래에서 설명하는 방법으로 아파치를 위한 별도의 + 계정을 만들어라.
+ +

아파치 service를 실행하기위한 별도의 계정을 만들 수도 + 있다. 특히 아파치가 네트웍 자원에 접근해야 한다면 이 방법을 + 강력히 권한다.

+ +
    +
  1. 일반 도메인 사용자 계정을 만들고 암호를 기억하라.
    2. + +
  2. 새로 만든 계정에 서비스로 로그온와 + 운영 체제의 일부로 활동 권한을 + 부여한다. Windows NT 4.0에서는 User Manager for Domains에서 + 권한을 부여할 수 있고, Windows 2000과 XP에서는 아마도 + "그룹 정책"을 사용해야 한다. "로컬 보안 설정" MMC + 스냅인에서 직접 설정해줄 수도 있다. +
    3. + +
  3. 새로 만든 계정이 Users 그룹에 속하는지 확인한다.
    4. + +
  4. 모든 문서와 스크립트 폴더에 (예를 들어 + htdocs와 cgi-bin) 대해 읽기 및 + 실행 (RX) 권한을 부여한다.
    5. + +
  5. 아파치 logs 디렉토리에 수정 (RWXD) 권한을 + 부여한다.
    6. + +
  6. Apache.exe 실행파일에 읽기 및 실행 (RX) + 권한을 부여한다.
    7. +
+ +
아파치 service를 실행하는 사용자에게 최소한 수정 (RWXD) + 권한이 필요한 logs 하위디렉토리를 제외하고 + Apache2 디렉토리 전체에 읽기 및 실행 (RX) 권한을 부여하는 + 것이 좋다.
+ +

계정에 "로컬 로그온"과 "서비스로 로그온" 권한이 있다면, + 그 계정으로 로그온하여 계정이 스크립트를 실행하고 웹페이지를 + 읽으며 콘솔창에서 아파치를 시작할 수 있는지 검사해볼 수 + 있다. 여기서 문제가 없다면 아파치를 service로 실행해도 문제가 + 없다.

+ +
Error code 2186은 아파치가 필요한 + 네트웍 자원에 접근할 수 없다는 말로 service의 "로그온" + 설정을 확인하라. 또, 아파치를 실행하는 계정의 권한을 + 살펴봐라.
+ +

아파치를 service로 실행하면 Windows Service Control + Manager에서 오류문을 볼 수 있다. 예를 들어, 제어판에서 + "서비스"를 사용하여 아파치를 시작하는 경우 다음과 같은 문구가 + 나올 수 있다:

+ +

+ Could not start the Apache2 service on \\COMPUTER
+ Error 1067; The process terminated unexpectedly. +

+ +

아파치 service를 시작할때 문제가 있으면 일반적인 이런 + 오류가 나온다. 실제 어디가 문제인지 알려면 아파치를 콘솔 + 프로그램으로 실행해보라.

+ +

Windows 9x에서 아파치는 Windows NT의 service와 비슷한 + 방법을 지원한다. 그러나 매우 실험적인 기능이다. + 실제 서비스에 사용할만큼 안정적이지 않고 앞으로 개선될지 + 보장할 수도 없다. 위험하므로 혹시나 사용한다면 주의해서 + 사용해야 한다!

+ +

두가지 service의 중요한 차이점은 다음과 같다:

+ +
    +

  • 아파치가 성공적으로 시작하면 배경에서 실행한다. + 예를 들어, 데스크탑에 바로가기를 만들어서 다음 명령을 + 실행하는 경우,

    + +

    + apache -n "MyServiceName" -k start +

    + +

    service가 성공적으로 시작하면 콘솔창이 생겼다가 금방 + 사라진다. httpd.conf 설정파일에 잘못된 내용이 있는 등 + 아파치 시작시 오류가 발생하면 콘솔창을 계속 보인다. 콘솔창은 + 문제의 원인을 파악하는데 도움을 주는 오류문을 보여준다.

    • + +

  • Windows 9x는 NET START와 NET + STOP 명령어를 지원하지 않는다. 명령프롬프트에서 + -k 옵션을 사용하여 아파치 service를 조정해야 + 한다. +

    • + +

  • + 아파치와 Windows 9x는 네트웍 권한을 가진 특정 사용자로 + 아파치를 실행하지 못한다. 사실 Windows 9x는 보안을 제공하지도 + 않는다. 이것이 바로 Apache Software Foundation이 Windows + 9x 시스템을 공개 웹서버로 사용하길 권하지 않는 이유다. + 사용자가 웹 컨텐츠를 개발하고 아파치 서버 학습을 돕기위해, + 아니면 안전한 사설 네트웍에 위치할 인트라넷 서버를 위해, + Windows 9x를 지원할 뿐이다.

    • + +
+ +

아파치가 콘솔 프로그램으로 동작함을 확인하였다면 Windows + NT에서와 같은 명령어로 가상 service를 설치, 조절, 제거할 + 수 있다. 또, Apache Service Monitor를 사용하여 Windows 9x + 가상 service를 관리할 수 있다.

+ +
top
+
+

아파치를 콘솔 프로그램으로 실행하기

+ + +

일반적으로 아파치를 service로 실행하길 권한다. 그러나 + 명령행에서 실행하는게 편한 경우가 있다 (Windows 9x에서는 + service를 안정적으로 지원하지 않기때문에 명령행에서 아파치를 + 실행하는 방법을 권한다).

+ +

아파치를 콘솔 프로그램으로 실행하려면, 명령행에서 다음 + 명령어를 사용한다:

+ +

+ apache +

+ +

아파치는 Control-C를 눌러서 정지할 때까지 실행된다.

+ +

또, 시작 메뉴 --> 프로그램 --> Apache HTTP + Server 2.0.xx --> Control Apache Server에 설치된 + Start Apache in Console 바로가기로 아파치를 실행할 수 있다. + 바로가기를 실행하면 콘솔창을 열고 그 안에서 아파치를 실행한다. + 아파치를 service로 설치하지 않았다면, 아파치를 실행하는 + 콘솔창에서 Control-C를 눌러 아파치를 중단할때까지 창이 떠있다. + 이 경우 서버는 몇초안에 종료한다. 그러나, 아파치를 service로 + 설치하였다면 바로가기는 service를 시작한다. 아파치 service가 + 이미 실행중이라면 바로가기는 아무일도 하지 않는다.

+ +

다른 콘솔창을 열고 다음과 같이 입력하여 실행중인 아파치를 + 종료할 수 있다:

+ +

+ apache -k shutdown +

+ +

이 방법은 아파치가 현재 작업을 마치고 점잖게 종료할 수 + 있기때문에 Control-C 보다 낫다.

+ +

또, 아파치를 재시작할 수 있다. 이 경우 설정파일을 다시 + 읽는다. 진행중인 작업을 중간에 끊지않고 완료한다. 아파치를 + 재시작하려면:

+ +

+ apache -k restart +

+ +
유닉스용 아파치에 익숙한 사람을 위해: 이 명령어는 + kill -TERM pid나 kill -USR1 + pid의 Windows판이다. 명령행 옵션 + -k는 유닉스 kill 명령어 이름을 + 본따 지었다.
+ +

아파치 콘솔창이 즉시 혹은 시작후 갑자기 닫치면 시작 메뉴 + --> 프로그램의 명령 프롬프트를 실행한다. 아파치를 설치한 + 폴더로 가서 apache 명령어를 실행해보고 발생한 + 오류문을 살펴본다. 그리고 logs 폴더로 가서, 설정파일이 + 잘못되었는지 error.log 파일을 살펴본다. 아파치를 + 설치할때 기본값을 사용했다면 다음과 같다:

+ +

+ c:
+ cd "\Program Files\Apache Group\Apache2\bin"
+ apache +

+ +

아파치가 정지할 때까지 기다리거나 Control-C를 누른다. + 그리고 다음과 같이 입력한다:

+ +

+ cd ..\logs
+ more < error.log +

+ +

아파치를 다룰때 아파치가 어떻게 설정파일을 찾는지 아는 + 것이 중요하다. 두가지 방법으로 명령행에서 설정파일을 지정할 + 수 있다:

+ +
    +

  • -f는 설정파일의 절대경로 혹은 상대경로를 + 지정한다:

    + +

    + apache -f "c:\my server files\anotherconfig.conf" +

    + +

    혹은

    + +

    + apache -f files\anotherconfig.conf +

    • + +

  • -n은 아파치 service를 선택하고, 해당 + service의 설정파일을 사용한다:

    + +

    + apache -n "MyServiceName" +

    +
    • +
+ +

두 경우 모두 설정파일이 적절한 ServerRoot를 지정해야 한다.

+ +

-f나 -n으로 설정파일을 지정하지 + 않으면, 아파치는 conf\httpd.conf와 같이 서버에 + 컴파일된 파일명을 사용한다. 이 기본 경로는 설치 디렉토리에 + 상대적이다. 다음과 같이 -V 옵션으로 아파치를 + 실행하면 SERVER_CONFIG_FILE이란 항목에서 서버가 + 사용할 설정파일을 알 수 있다:

+ +

+ apache -V +

+ +

아파치는 다음 순서대로 ServerRoot를 찾는다:

+ +
    +
  1. -C 명령행 옵션에 사용한 ServerRoot 지시어.
    2. + +
  2. -d 명령행 옵션.
    3. + +
  3. 현재 작업 디렉토리.
    4. + +
  4. 바이너리 설치를 했다면 설치할때 만든 registry 항목.
    5. + +
  5. 서버에 컴파일된 server root. 기본값은 + /apache이고, apache -V를 실행하면 + HTTPD_ROOT라는 항목에서 확인할 수 있다.
    6. +
+ +

설치할때 윈도우즈 레지스트리에 버전 특유의 레지스트리 + 키를 만든다. 키의 위치는 설치 종류에 따라 다르다. install + Apache for all users를 선택하였다면 + HKEY_LOCAL_MACHINE 아래에 다음과 같은 키를 + 만든다 (물론 버전번호는 아파치 버전마다 다르다): +

+ +

+ HKEY_LOCAL_MACHINE\SOFTWARE\Apache Group\Apache\2.0.43 +

+ +

"모든 사용자"를 대상으로 아파치를 설치하였다면 + HKEY_CURRENT_USER 아래 키가 생긴다. 내용은 + 현재 로그온한 사용자에 따라 다르다:

+ +

+ HKEY_CURRENT_USER\SOFTWARE\Apache Group\Apache\2.0.43 +

+ +

키 이름이 서버에 컴파일되기때문에 현재 버전을 건드리지않고 + 새로운 버전을 설치하여 테스트해볼 수 있다. 물론 새 버전을 + 다른 버전과 같은 디렉토리에 설치하지않도록 주의해야 한다.

+ +

바이너리 설치를 하지 않은 경우 아파치는 레지스트리 키가 + 없다고 불평할 수 있다. 서버가 다른 방법으로 설정파일을 찾을 + 수 있다면 이 경고를 무시해도 된다.

+ +

키의 값은 ServerRoot + 디렉토리이며, 이 디렉토리에 conf라는 하위디렉토리가 + 있다. 아파치를 시작하면 이 하위디렉토리에서 + httpd.conf 파일을 읽는다. 이 파일에 나오는 + ServerRoot 지시어가 + 레지스트리 키에 나온 디렉토리와 다르다면, 아파치는 레지스트리에서 + 얻은 값을 무시하고 앞으로 설정파일에 나온 디렉토리를 사용한다. + 아파치 디렉토리나 설정파일을 다른 장소로 복사하면 반드시 + httpd.conf 파일에 있는 ServerRoot 지시어를 그 위치로 + 수정하라.

+ +
top
+
+

정상적으로 설치되었는지 검사하기

+ + +

(콘솔창이나 service를 통해) 아파치를 시작하면 (설정파일의 + Listen 지시어를 + 수정하거나 아파치를 "현재 사용자만" 대상으로 설치하지 않는 + 경우) 80번 포트를 기다린다. 브라우저를 시작하고 URL을 입력하여 + 서버의 기본 페이지에 접근하다:

+ +

+ http://localhost/ +

+ +

아파치는 아파치 설명서 링크가 있는 환영페이지를 보여줘야 + 한다. 아무 일도 일어나지 않거나 오류가 나오면, logs + 하위디렉토리에 있는 error.log 파일을 살펴봐라. + 호스트가 네트웍에 연결되있지 않거나 DNS (Domain Name Service) + 설정에 문제가 있다면 다음 URL을 사용해야 한다:

+ +

+ http://127.0.0.1/ +

+ +

기본 설치가 동작하면 conf 하위디렉토리에 + 있는 파일을 적절히 설정한다. 또, Windows NT 아파치 service + 설정을 수정한 경우 먼저 명령행에서 아파치를 시작하여 오류가 + 발생하지않는지 확인해야 한다.

+ +

아파치가 다른 TCP/IP 프로그램과 같은 포트를 공유할 수 + 없기때문에 아파치를 시작하기 전에 다른 + 서비스를 중단, 제거, 재설정해야 할지도 모른다. 다른 웹서버나 + 특정 방화벽 서버스와 충돌할 수 있다. +

+ +
+
+

가능한 언어:  en  | + fr  | + ko 

+
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 -- cgit v1.2.3