From: Jim Jagielski
Konfiguration der vom Apache HTTP Server verwendeten Adressen und Ports.
diff --git a/docs/manual/convenience.map b/docs/manual/convenience.map index dce68daaeab..e86f47601b5 100644 --- a/docs/manual/convenience.map +++ b/docs/manual/convenience.map @@ -474,6 +474,7 @@ redirectmatch mod/mod_alias.html#redirectmatch redirectpermanent mod/mod_alias.html#redirectpermanent redirecttemp mod/mod_alias.html#redirecttemp reflectorheader mod/mod_reflector.html#reflectorheader +regexdefaultoptions mod/core.html#regexdefaultoptions registerhttpmethod mod/core.html#registerhttpmethod remoteipheader mod/mod_remoteip.html#remoteipheader remoteipinternalproxy mod/mod_remoteip.html#remoteipinternalproxy diff --git a/docs/manual/howto/reverse_proxy.html.en b/docs/manual/howto/reverse_proxy.html.en index 1bdfdd80674..f79899b7bb3 100644 --- a/docs/manual/howto/reverse_proxy.html.en +++ b/docs/manual/howto/reverse_proxy.html.en @@ -176,19 +176,40 @@ ProxyPassReverse "/images" "balancer://myset/"
- You can also fine-tune various failover scenarios, detailing which
- workers and even which balancers should accessed in such cases. For
- example, the below setup implements 2 failover cases: In the first,
- http://hstandby.example.com:8080 is only sent traffic
- if all other workers in the myset balancer are not available.
- If that worker itself is not available, only then will the
- http://bkup1.example.com:8080 and http://bkup2.example.com:8080
- workers be brought into rotation:
+ You can also fine-tune various failover scenarios, detailing which workers
+ and even which balancers should be accessed in such cases. For example, the
+ below setup implements three failover cases:
+
http://spare1.example.com:8080 and
+ http://spare2.example.com:8080 are only sent traffic if one
+ or both of http://www2.example.com:8080 or
+ http://www3.example.com:8080 is unavailable. (One spare
+ will be used to replace one unusable member of the same balancer set.)
+ http://hstandby.example.com:8080 is only sent traffic if
+ all other workers in balancer set 0 are not available.
+ 0 workers, spares, and the standby
+ are unavailable, only then will the
+ http://bkup1.example.com:8080 and
+ http://bkup2.example.com:8080 workers from balancer set
+ 1 be brought into rotation.
+ + Thus, it is possible to have one or more hot spares and hot standbys for + each load balancer set.
<Proxy balancer://myset>
BalancerMember http://www2.example.com:8080
BalancerMember http://www3.example.com:8080 loadfactor=3 timeout=1
+ BalancerMember http://spare1.example.com:8080 status=+R
+ BalancerMember http://spare2.example.com:8080 status=+R
BalancerMember http://hstandby.example.com:8080 status=+H
BalancerMember http://bkup1.example.com:8080 lbset=1
BalancerMember http://bkup2.example.com:8080 lbset=1
@@ -200,11 +221,12 @@ ProxyPassReverse "/images/" "balancer://myset/"
- The magic of this failover setup is setting http://hstandby.example.com:8080
- with the +H status flag, which puts it in hot standby mode,
- and making the 2 bkup# servers part of the #1 load balancer set (the
- default set is 0); for failover, hot standbys (if they exist) are used 1st, when all regular
- workers are unavailable; load balancer sets are always tried lowest number first.
+ For failover, hot spares are used as replacements for unusable workers in
+ the same load balancer set. A worker is considered unusable if it is
+ draining, stopped, or otherwise in an error/failed state. Hot standbys are
+ used if all workers and spares in the load balancer set are
+ unavailable. Load balancer sets (with their respective hot spares and
+ standbys) are always tried in order from lowest to highest.
SIRHEretry setting of the worker.
Protocols
ProtocolsHonorOrder
QualifyRedirectURL
RegexDefaultOptions
RegisterHttpMethod
RLimitCPU
RLimitMEM| Beschreibung: | Allow to configure global/default options for regexes |
|---|---|
| Syntax: | RegexDefaultOptions [none] [+|-]option [[+|-]option] ... |
| Voreinstellung: | RegexDefaultOptions DOLLAR_ENDONLY |
| Kontext: | Serverkonfiguration |
| Status: | Core |
| Modul: | core |
| Kompatibilität: | Only available from Apache 2.4.30 and later. |
Die Dokumentation zu dieser Direktive wurde + noch nicht übersetzt. Bitte schauen Sie in die englische + Version.
| Beschreibung: | Register non-standard HTTP methods |
|---|---|
| Kontext: | Serverkonfiguration |
| Status: | Core |
| Modul: | core |
| Kompatibilität: | Available in Apache HTTP Server 2.4.24 and later |
Die Dokumentation zu dieser Direktive wurde noch nicht übersetzt. Bitte schauen Sie in die englische Version.
Protocols
ProtocolsHonorOrder
QualifyRedirectURL
RegexDefaultOptions
RegisterHttpMethod
RLimitCPU
RLimitMEM| Descripción: | Allow to configure global/default options for regexes |
|---|---|
| Sintaxis: | RegexDefaultOptions [none] [+|-]option [[+|-]option] ... |
| Valor por defecto: | RegexDefaultOptions DOLLAR_ENDONLY |
| Contexto: | server config |
| Estado: | Core |
| Módulo: | core |
| Compatibilidad: | Only available from Apache 2.4.30 and later. |
La Documentación para esta directiva + no ha sido traducida aún. Por favor use la versión en inglés + mientras tanto. +
| Descripción: | Register non-standard HTTP methods |
|---|---|
| Contexto: | server config |
| Estado: | Core |
| Módulo: | core |
| Compatibilidad: | Available in Apache HTTP Server 2.4.24 and later |
La Documentación para esta directiva no ha sido traducida aún. Por favor use la versión en inglés mientras tanto. diff --git a/docs/manual/mod/core.html.ja.utf8 b/docs/manual/mod/core.html.ja.utf8 index 5c2a41dde0c..bb1a48dc708 100644 --- a/docs/manual/mod/core.html.ja.utf8 +++ b/docs/manual/mod/core.html.ja.utf8 @@ -105,6 +105,7 @@
Protocols
ProtocolsHonorOrder
QualifyRedirectURL
RegexDefaultOptions
RegisterHttpMethod
RLimitCPU
RLimitMEM| 説æ: | Allow to configure global/default options for regexes |
|---|---|
| æ§æ: | RegexDefaultOptions [none] [+|-]option [[+|-]option] ... |
| ããã©ã«ã: | RegexDefaultOptions DOLLAR_ENDONLY |
| ã³ã³ããã¹ã: | ãµã¼ãè¨å®ãã¡ã¤ã« |
| ã¹ãã¼ã¿ã¹: | Core |
| ã¢ã¸ã¥ã¼ã«: | core |
| äºææ§: | Only available from Apache 2.4.30 and later. |
ãã®ãã£ã¬ã¯ãã£ãã®è§£èª¬ææ¸ã¯ + ã¾ã 翻訳ããã¦ãã¾ãããè±èªçãã覧ãã ããã +
| 説æ: | Register non-standard HTTP methods |
|---|---|
| ã³ã³ããã¹ã: | ãµã¼ãè¨å®ãã¡ã¤ã« |
| ã¹ãã¼ã¿ã¹: | Core |
| ã¢ã¸ã¥ã¼ã«: | core |
| äºææ§: | Available in Apache HTTP Server 2.4.24 and later |
ãã®ãã£ã¬ã¯ãã£ãã®è§£èª¬ææ¸ã¯ ã¾ã 翻訳ããã¦ãã¾ãããè±èªçãã覧ãã ããã
Configuring hot spares can help ensure that a certain number of + workers are always available for use per load balancer set:
+ProxyPass "/" "balancer://sparecluster/" +<Proxy balancer://sparecluster> + BalancerMember ajp://1.2.3.4:8009 + BalancerMember ajp://1.2.3.5:8009 + # The servers below are hot spares. For each server above that is unusable + # (draining, stopped, unreachable, in error state, etc.), one of these spares + # will be used in its place. Two servers will always be available for a request + # unless one or more of the spares is also unusable. + BalancerMember ajp://1.2.3.6:8009 status=+R + BalancerMember ajp://1.2.3.7:8009 status=+R +</Proxy>+ +
Setting up a hot-standby that will only be used if no other - members are available:
+ members (or spares) are available in the load balancer set:ProxyPass "/" "balancer://hotcluster/"
<Proxy "balancer://hotcluster">
BalancerMember "ajp://1.2.3.4:8009" loadfactor=1
diff --git a/docs/manual/mod/mod_proxy.html.fr b/docs/manual/mod/mod_proxy.html.fr
index 491664c0bd8..203134d6451 100644
--- a/docs/manual/mod/mod_proxy.html.fr
+++ b/docs/manual/mod/mod_proxy.html.fr
@@ -30,6 +30,8 @@
fr |
ja
Verfügbare Sprachen: de | diff --git a/docs/manual/mod/quickreference.html.en b/docs/manual/mod/quickreference.html.en index 7227967cc0d..e1ab258dc1d 100644 --- a/docs/manual/mod/quickreference.html.en +++ b/docs/manual/mod/quickreference.html.en @@ -753,9 +753,9 @@ proxied
Server HTTP response
+Server HTTP response
headerLast-Modified headers are generated by the
+Last-Modified headers are generated by the
server.TRACE requestsmime.types fileTRACE requestsmime.types fileIdiomas disponibles: de | diff --git a/docs/manual/mod/quickreference.html.ja.utf8 b/docs/manual/mod/quickreference.html.ja.utf8 index a4b55544983..3bae8eec9ee 100644 --- a/docs/manual/mod/quickreference.html.ja.utf8 +++ b/docs/manual/mod/quickreference.html.ja.utf8 @@ -337,7 +337,7 @@ variables
Server HTTP å¿çããããè¨å®ããServer HTTP å¿çããããè¨å®ããLast-Modified headers are generated by the
+ [[!]env-variable[=value]] ...Last-Modified headers are generated by the
server.TRACE ã¡ã½ããã®ãªã¯ã¨ã¹ãã«å¯¾ããå¿çæ¹æ³ã決ãã
+TRACE ã¡ã½ããã®ãªã¯ã¨ã¹ãã«å¯¾ããå¿çæ¹æ³ã決ãã
mime.types ãã¡ã¤ã«ã®ä½ç½®mime.types ãã¡ã¤ã«ã®ä½ç½®ç¿»è¨³æ¸ã¿è¨èª: de | diff --git a/docs/manual/mod/quickreference.html.ko.euc-kr b/docs/manual/mod/quickreference.html.ko.euc-kr index fc41ab71b85..3e17a078da4 100644 --- a/docs/manual/mod/quickreference.html.ko.euc-kr +++ b/docs/manual/mod/quickreference.html.ko.euc-kr @@ -334,7 +334,7 @@ headers
Server HTTP response
+Server HTTP response
headerLast-Modified headers are generated by the
+Last-Modified headers are generated by the
server.TRACE requestsmime.types fileTRACE requestsmime.types file°¡´ÉÇÑ ¾ð¾î: de | diff --git a/docs/manual/mod/quickreference.html.tr.utf8 b/docs/manual/mod/quickreference.html.tr.utf8 index 20df1960949..49fc77c6371 100644 --- a/docs/manual/mod/quickreference.html.tr.utf8 +++ b/docs/manual/mod/quickreference.html.tr.utf8 @@ -751,9 +751,9 @@ proxied
Server HTTP response
+Server HTTP response
headerLast-Modified headers are generated by the
+Last-Modified headers are generated by the
server.TRACE requestsmime.types fileTRACE requestsmime.types fileå¯ç¨è¯è¨: de |
diff --git a/docs/manual/suexec.html.en b/docs/manual/suexec.html.en
index 63f7bad5dc2..526e79301c0 100644
--- a/docs/manual/suexec.html.en
+++ b/docs/manual/suexec.html.en
@@ -374,21 +374,6 @@
together with the --enable-suexec option to let
APACI accept your request for using the suEXEC feature.
-
--enable-suexec-capabilitiessuexec binary is installed "setuid/setgid
- root", which allows it to run with the full privileges of the
- root user. If this option is used, the suexec
- binary will instead be installed with only the setuid/setgid
- "capability" bits set, which is the subset of full root
- priviliges required for suexec operation. Note that
- the suexec binary may not be able to write to a log
- file in this mode; it is recommended that the
- --with-suexec-syslog --without-suexec-logfile
- options are used in conjunction with this mode, so that syslog
- logging is used instead.--with-suexec-bin=PATHsuexec binary must be hard-coded
@@ -450,12 +435,6 @@
"suexec_log" and located in your standard logfile
directory (--logfiledir).--with-suexec-syslog--without-suexec-logfile.--with-suexec-safepath=PATHThe suEXEC wrapper will write log information
to the file defined with the --with-suexec-logfile
- option as indicated above, or to syslog if --with-suexec-syslog
- is used. If you feel you have configured and
- installed the wrapper properly, have a look at the log and the
- error_log for the server to see where you may have gone astray.
- The output of "suexec -V" will show the options
- used to compile suexec, if using a binary distribution.