From cb35beef2a938b80c9e4b5d6a408eca437aa74db Mon Sep 17 00:00:00 2001
From: Arno Töll Apache HTTP Server Version 2.4 Available Languages: en This module provides HTTP/2 (RFC 7540) support for the Apache
+ HTTP Server. This module relies on libnghttp2
+ to provide the core http/2 engine. This module is experimental. Its behaviors, directives, and
+ defaults are subject to more change from release to
+ release relative to other standard modules. Users are encouraged to
+ consult the "CHANGES" file for potential updates.
+ This directive toggles the usage of the HTTP/2 Direct Mode. This
+ should be used inside a
+
+ This directive sets the maximum number of active streams per HTTP/2 session (e.g. connection)
+ that the server allows. A stream is active if it is not
+ This directive sets the maximum number of seconds a h2 worker may
+ idle until it shuts itself down. This only happens while the number of
+ h2 workers exceeds
+ This directive sets the maximum number of worker threads to spawn
+ per child process for HTTP/2 processing. If this directive is not used,
+
+ This directive sets the minimum number of worker threads to spawn
+ per child process for HTTP/2 processing. If this directive is not used,
+
+ This directive toggles if HTTP/2 requests shall be serialized in
+ HTTP/1.1 format for processing by
+ Serialization will lower performance, but gives more backward
+ compatibility in case custom filters/hooks need it.
+
+ This directive sets maximum number of extra file handles
+ a HTTP/2 session is allowed to use. A file handle is counted as
+ extra when it is transfered from a h2 worker thread to
+ the main HTTP/2 connection handling. This commonly happens when
+ serving static files.
+
+ Depending on the processing model configured on the server, the
+ number of connections times number of active streams may exceed
+ the number of file handles for the process. On the other hand,
+ converting every file into memory bytes early results in too
+ many buffer writes. This option helps to mitigate that.
+
+ The number of file handles used by a server process is then in
+ the order of:
+
+ This directive sets the maximum number of outgoing data bytes buffered in memory
+ for an active streams. This memory is not allocated per stream as such. Allocations
+ are counted against this limit when they are about to be done. Stream processing
+ freezes when the limit has been reached and will only continue when buffered data
+ has been sent out to the client.
+
+ This directive sets the size of the window that is used for flow control
+ from client to server and limits the amount of data the server has to buffer.
+ The client will stop sending on a stream once the limit has been reached until
+ the server announces more available space (as it has processed some of the data).
+
+ This limit affects only request bodies, not its meta data such as headers. Also,
+ it has no effect on response bodies as the window size for those are managed
+ by the clients.
+ Available Languages: en
+
+
+
+ Det inntraff en intern feil hos serveren, og det var ikke mulig å
+ gjennomføre din forespørsel. Serveren er enten overbelastet, eller
+ CGI-skriptet inneholder feil.
+
+
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_LENGTH_REQUIRED.html.var b/docs/error/HTTP_LENGTH_REQUIRED.html.var
index d13c359c..f542b9d4 100644
--- a/docs/error/HTTP_LENGTH_REQUIRED.html.var
+++ b/docs/error/HTTP_LENGTH_REQUIRED.html.var
@@ -41,13 +41,12 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- Una solicitud con el método
- requiere que el contenido de la variable de los encabezados
- Content-Length
sea válida.
+ Una petición con el método requiere que el encabezado
+ Content-Length
sea válido.
----------es--
@@ -136,6 +135,19 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ En forespørsel med
+ metoden krever en korrekt Content-Length
header.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_METHOD_NOT_ALLOWED.html.var b/docs/error/HTTP_METHOD_NOT_ALLOWED.html.var
index 124cd589..1eefb9d7 100644
--- a/docs/error/HTTP_METHOD_NOT_ALLOWED.html.var
+++ b/docs/error/HTTP_METHOD_NOT_ALLOWED.html.var
@@ -39,11 +39,11 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- El método
- no está permitido para el URL solicitado.
+ No se permite el método
+ para la URL solicitada.
----------es--
@@ -126,6 +126,19 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ metoden er ikke
+ tillatt for den forespurte adressen.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_NOT_FOUND.html.var b/docs/error/HTTP_NOT_FOUND.html.var
index 90fdcf7e..442f4968 100644
--- a/docs/error/HTTP_NOT_FOUND.html.var
+++ b/docs/error/HTTP_NOT_FOUND.html.var
@@ -82,23 +82,23 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- El URL solicitado no ha sido localizado en este servidor.
+ No se ha localizado la URL solicitada en este servidor.
- El URL de la ">página que lo refirió
- parece ser equivocado u obsoleto. Por favor comunique al autor
- de ">esa
- página acerca del error.
+ La URL de la ">página que le ha remitido
+ parece ser errónea o estar obsoleta. Por favor, informe del error
+ al autor de ">esa
+ página.
- Si usted tecleó el URL manualmente, por favor revise su
- ortografía y vuélvalo a intentar.
+ Si usted ha introducido la URL manualmente, por favor revise su
+ ortografía e inténtelo de nuevo.
@@ -267,6 +267,33 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ Den etterspurte adressen finnes ikke på denne serveren.
+
+
+
+ Lenken på den
+ ">forrige siden
+ser ut til å være feil eller utdatert. Venligst informer forfatteren av
+ ">siden
+ om feilen.
+
+
+
+ Om du skrev inn adressen manuelt, vennligst kontroller stavingen og
+ forsøk igjen.
+
+
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_NOT_IMPLEMENTED.html.var b/docs/error/HTTP_NOT_IMPLEMENTED.html.var
index 99f19f6a..8dc2f7d9 100644
--- a/docs/error/HTTP_NOT_IMPLEMENTED.html.var
+++ b/docs/error/HTTP_NOT_IMPLEMENTED.html.var
@@ -37,11 +37,11 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- El servidor no tiene implementada la acción
- solicitada por el buscador.
+ El servidor no soporta la acción
+ solicitada por el navegador.
----------es--
@@ -119,6 +119,19 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ Serveren støtter ikke den handlingen som ønskes utført av
+ nettleseren.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
@@ -184,7 +197,7 @@ Content-language: sv
Content-type: text/html; charset=UTF-8
Body:----------sv--
Servern stödjer inte den handling som önskades
diff --git a/docs/error/HTTP_PRECONDITION_FAILED.html.var b/docs/error/HTTP_PRECONDITION_FAILED.html.var
index ef93e6e1..da69e2b6 100644
--- a/docs/error/HTTP_PRECONDITION_FAILED.html.var
+++ b/docs/error/HTTP_PRECONDITION_FAILED.html.var
@@ -38,11 +38,11 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- La pre-condición de la solicitud para el
- URL no se evaluó positivamente.
+ No se ha evaluado positivamente la pre-condición
+ de la petición para la URL.
----------es--
@@ -121,6 +121,19 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ Den nødvendige forutsetningen for forespørselen passerte ikke
+ vurderingen med positivt resultat.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var b/docs/error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
index f3e0f661..20bceff6 100644
--- a/docs/error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
+++ b/docs/error/HTTP_REQUEST_ENTITY_TOO_LARGE.html.var
@@ -42,10 +42,10 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- El método
+ El método
no permite transmitir la información, o el
volumen de la información excede los límites
de capacidad del mismo.
@@ -135,6 +135,20 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ metoden tillater ikke
+ de sendte data eller så overskrider datamengenden
+ kapasitetsbegrensningen.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_REQUEST_TIME_OUT.html.var b/docs/error/HTTP_REQUEST_TIME_OUT.html.var
index 3f395657..85004a0e 100644
--- a/docs/error/HTTP_REQUEST_TIME_OUT.html.var
+++ b/docs/error/HTTP_REQUEST_TIME_OUT.html.var
@@ -40,11 +40,11 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- El servidor cerró la conección de red
- debido a que el buscador no termino la solicitud
+ El servidor ha cerrado la conexión de red
+ debido a que el navegador no ha finalizado la solicitud
dentro del tiempo permitido.
@@ -129,6 +129,19 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ Serveren stengte forbindelsen fordi nettleseren ikke avsluttet
+ forespørselen innen tidsgrensen.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_REQUEST_URI_TOO_LARGE.html.var b/docs/error/HTTP_REQUEST_URI_TOO_LARGE.html.var
index ba5b409a..4831c472 100644
--- a/docs/error/HTTP_REQUEST_URI_TOO_LARGE.html.var
+++ b/docs/error/HTTP_REQUEST_URI_TOO_LARGE.html.var
@@ -40,11 +40,11 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- La longitud del URL solicitado excede el límite de
- capacidad para este servidor. La solicitud no puede ser procesada.
+ La longitud de la URL solicitada excede el límite de
+ capacidad para este servidor. No se puede procesar la solicitud.
----------es--
@@ -128,6 +128,20 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ Lengden på adressen som etterspurtes overskrider
+ kapasitetsgrensen for denne serveren. Forespørselen kan
+ ikke prosesseres.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_SERVICE_UNAVAILABLE.html.var b/docs/error/HTTP_SERVICE_UNAVAILABLE.html.var
index ec021344..e5905ebb 100644
--- a/docs/error/HTTP_SERVICE_UNAVAILABLE.html.var
+++ b/docs/error/HTTP_SERVICE_UNAVAILABLE.html.var
@@ -43,13 +43,12 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- Por el momento el servidor no puede atender su solicitud
- debido a que está en mantenimiento o a que tiene
- problemas de capacidad. Por favor intente nuevamente
- más tarde.
+ El servidor no puede procesar su solicitud en este momento
+ debido a tareas de mantenimiento o a problemas de capacidad.
+ Por favor, inténtelo de nuevo más tarde.
----------es--
@@ -138,6 +137,19 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ Serveren er midlertidig ikke i stand til å utføre din
+ forespørsel. Vennligst prøv igjen senere.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_UNAUTHORIZED.html.var b/docs/error/HTTP_UNAUTHORIZED.html.var
index bd799579..2a8994f0 100644
--- a/docs/error/HTTP_UNAUTHORIZED.html.var
+++ b/docs/error/HTTP_UNAUTHORIZED.html.var
@@ -62,20 +62,20 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
El servidor no puede certificar que usted esté autorizado
- para accesar el URL "".
- Pudo haber suministrado información incorrecta (ej.
- contraseña inválida) o, el buscador no sabe
- como suministrar la información requerida.
+ para acceder a la URL "".
+ Ha podido suministrar información incorrecta (ej.
+ contraseña no válida) o el navegador no sabe
+ cómo suministrar la información requerida.
- En caso de que a usted le este permitido accesar el documento,
- verifique su nombre de usuario y contraseña y vuélvalo
- a intentar.
+ En caso de que usted tenga permiso para acceder al documento,
+ por favor verifique su nombre de usuario y contraseña y
+ vuélvalo a intentar.
----------es--
@@ -209,6 +209,27 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ Serveren kunne ikke verifisere at du har tillatelse til å besøke
+ adressen "". Enten
+ oppga du feil opplysninger (f.eks. feil passord) eller så støtter
+ ikke din nettleser dette autentiseringsystemet.
+
+
+
+ Om du har tillatelse til å besøke siden, vennligst kontroler ditt
+ brukernavn og passord og forsøk igjen.
+
+
+----------nb--
+
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var b/docs/error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
index a5a74872..44094cde 100644
--- a/docs/error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
+++ b/docs/error/HTTP_UNSUPPORTED_MEDIA_TYPE.html.var
@@ -37,10 +37,10 @@ Body:----------en--
Content-language: es
Content-type: text/html
Body:----------es--
-
+
- El servidor no tiene implementado el tipo
+ El servidor no soporta el tipo
de medio transmitido en la solicitud.
@@ -120,6 +120,18 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ Serveren støtter ikke den mediatypen som ble forespurt.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/HTTP_VARIANT_ALSO_VARIES.html.var b/docs/error/HTTP_VARIANT_ALSO_VARIES.html.var
index c38afd47..ba9609c6 100644
--- a/docs/error/HTTP_VARIANT_ALSO_VARIES.html.var
+++ b/docs/error/HTTP_VARIANT_ALSO_VARIES.html.var
@@ -133,6 +133,19 @@ Body:----------nl--
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+
+
+ En variant av den forespurte enheten er i seg selv en forhandelbar
+ ressurs. Tilgang ikke mulig.
+
+
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/error/README b/docs/error/README
index b369187f..b660d07e 100644
--- a/docs/error/README
+++ b/docs/error/README
@@ -24,6 +24,7 @@
| Italian (it) | Luigi Rosa |
| Japanese (ja) | TAKAHASHI Makoto |
| Korean (ko) | Jaeho Shin |
+ | Norwegian Bokmål (nb) | Tom Fredrik Klaussen |
| Polish (pl) | Tomasz Kepczynski |
| Romanian (ro) | Andrei Besleaga |
| Serbian (sr) | Nikola Smolenski |
diff --git a/docs/error/contact.html.var b/docs/error/contact.html.var
index 4dea0126..62044cf0 100644
--- a/docs/error/contact.html.var
+++ b/docs/error/contact.html.var
@@ -74,6 +74,13 @@ Indien u van oordeel bent dat deze server in fout is, gelieve
de ">webmaster te contacteren.
----------nl--
+Content-language: nb
+Content-type: text/html; charset=UTF-8
+Body:----------nb--
+Om du tror dette skyldes en serverfeil, venligst kontakt
+">webansvarlig.
+----------nb--
+
Content-language: pl
Content-type: text/html; charset=UTF-8
Body:----------pl--
diff --git a/docs/man/ab.1 b/docs/man/ab.1
index f9df604f..cbca2f80 100644
--- a/docs/man/ab.1
+++ b/docs/man/ab.1
@@ -19,7 +19,7 @@
.el .ne 3
.IP "\\$1" \\$2
..
-.TH "AB" 1 "2014-06-24" "Apache HTTP Server" "ab"
+.TH "AB" 1 "2015-05-01" "Apache HTTP Server" "ab"
.SH NAME
ab \- Apache HTTP server benchmarking tool
@@ -80,7 +80,7 @@ Do HEAD requests instead of GET\&.
Enable the HTTP KeepAlive feature, \fIi\&.e\&.\fR, perform multiple requests within one HTTP session\&. Default is no KeepAlive\&.
.TP
-l
-Do not report errors if the length of the responses is not constant\&. This can be usefull for dynamic pages\&. Available in 2\&.4\&.7 and later\&.
+Do not report errors if the length of the responses is not constant\&. This can be useful for dynamic pages\&. Available in 2\&.4\&.7 and later\&.
.TP
-m \fIHTTP-method\fR
Custom HTTP method for the requests\&. Available in 2\&.4\&.10 and later\&.
diff --git a/docs/manual/bind.html.de b/docs/manual/bind.html.de
index cdaba989..02af1105 100644
--- a/docs/manual/bind.html.de
+++ b/docs/manual/bind.html.de
@@ -1,6 +1,8 @@
-
+Apache Module mod_http2
+
+
+Description: Support for the HTTP/2 transport layer
+Status: Extension
+ModuleIdentifier: h2_module SourceFile: mod_http2.c Summary
+
+ Warning
+ Directives
+
+H2Direct Directive
+
+
+
+Description: H2 Direct Protocol Switch
+Syntax: H2Direct on|off
+Default: H2Direct on (for non TLS)
+Context: server config, virtual host
+Status: Extension
+Module: mod_http2 <VirtualHost>
+ section to enable direct HTTP/2 communication for that virtual host.
+ Direct communication means that if the first bytes received by the
+ server on a connection match the HTTP/2 preamble, the HTTP/2
+ protocol is switched to immediately without further negotiation.
+ This mode falls outside the RFC 7540 but has become widely implemented
+ as it is very convenient for development and testing.
+ By default the direct HTTP/2 mode is enabled.
+ Example
H2Direct on
+H2MaxSessionStreams Directive
+
+
+
+Description: Maximum number of active streams per HTTP/2 session.
+Syntax: H2MaxSessionStreams n
+Default: H2MaxSessionStreams 100
+Context: server config, virtual host
+Status: Extension
+Module: mod_http2 idle
or
+ closed
according to RFC 7540.
+ Example
H2MaxSessionStreams 20
+H2MaxWorkerIdleSeconds Directive
+
+
+
+Description: Maximum number of seconds h2 workers remain idle until shut down.
+Syntax: H2MaxWorkerIdleSeconds n
+Default: H2MaxWorkerIdleSeconds 600
+Context: server config
+Status: Extension
+Module: mod_http2 H2MinWorkers
.
+ Example
H2MaxWorkerIdleSeconds 20
+H2MaxWorkers Directive
+
+
+
+Description: Maximum number of worker threads to use per child process.
+Syntax: H2MaxWorkers n
+Context: server config
+Status: Extension
+Module: mod_http2 mod_http2
will chose a value suitable for the mpm
+ module loaded.
+ Example
H2MaxWorkers 20
+H2MinWorkers Directive
+
+
+
+Description: Minimal number of worker threads to use per child process.
+Syntax: H2MinWorkers n
+Context: server config
+Status: Extension
+Module: mod_http2 mod_http2
will chose a value suitable for the mpm
+ module loaded.
+ Example
H2MinWorkers 10
+H2SerializeHeaders Directive
+
+
+
+Description: Serialize Request/Resoonse Processing Switch
+Syntax: H2SerializeHeaders on|off
+Default: H2SerializeHeaders off
+Context: server config, virtual host
+Status: Extension
+Module: mod_http2 httpd
core or if
+ received binary data shall be passed into the request_rec
s
+ directly.
+ Example
H2SerializeHeaders on
+H2SessionExtraFiles Directive
+
+
+
+Description: Number of Extra File Handles
+Syntax: H2SessionExtraFiles n
+Default: H2SessionExtraFiles 5
+Context: server config, virtual host
+Status: Extension
+Module: mod_http2 (h2_connections * extra_files) + (h2_max_worker)
+ Example
H2SessionExtraFiles 10
+H2StreamMaxMemSize Directive
+
+
+
+Description: Maximum amount of output data buffered per stream.
+Syntax: H2StreamMaxMemSize bytes
+Default: H2StreamMaxMemSize 65536
+Context: server config, virtual host
+Status: Extension
+Module: mod_http2 Example
H2StreamMaxMemSize 128000
+H2WindowSize Directive
+
+
+
+Description: Size of Stream Window for upstream data.
+Syntax: H2WindowSize bytes
+Default: H2WindowSize 65536
+Context: server config, virtual host
+Status: Extension
+Module: mod_http2 Example
H2WindowSize 128000
+Comments
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.Access control
<Location "/server-info">
SetHandler server-info
- Order allow,deny
# Allow access from server itself
- Allow from 127.0.0.1
+ Require ip 127.0.0.1
+
# Additionally, allow access from local workstation
- Allow from 192.168.1.17
+ Require ip 192.168.1.17
</Location>
Contrle d'accs
<Location "/server-info">
SetHandler server-info
- Order allow,deny
# Autorisation d'accs depuis le serveur lui-mme
- Allow from 127.0.0.1
+ Require ip 127.0.0.1
+
# Autorisation d'accs depuis une station de travail du rseau
# local
- Allow from 192.168.1.17
+ Require ip 192.168.1.17
</Location>
Açıklama: | Sunucuya yapılan isteklerin günlük kayıtlarının tutulması | ||
---|---|---|---|
Durum: | Temel | ||
%T |
Saniye cinsinden, isteği sunmak için harcanan zaman. | ||
%u |
+|||
%{BİRİM}T |
+ BİRİM ile belirtilen zaman birimi cinsinden, isteği
+ sunmak için harcanan zaman. Geçerli birimler: milisaniye için
+ ms , mikrosaniye için us , saniye için
+ s . s kullanımı birimsiz %T ile
+ aynı sonucu verir; us kullanımı %D ile aynı
+ sonucu verir. Birimli %T kullanımı 2.4.13 ve sonrasında
+ geçerlidir. | ||
%u |
Uzak kullanıcı (kimlik doğrulaması istenmişse vardır; durum kodu
(%s ) 401 ise yanlış olabilir). | ||
%U |
+|||
%U |
Herhangi bir sorgu dizgesi içermeksizin istenen URL yolu. | ||
%v |
+|||
%v |
İsteği sunan sunucunun meşru sunucu ismi (ServerName ). | ||
%V |
+|||
%V |
UseCanonicalName ayarı ile
ilgili sunucu ismi. | ||
%X |
+|||
%X |
Yanıt tamamlandığında bağlantı durumu:
| ||
%I |
+|||
%I |
İstek ve başlıklar dahil alınan bayt sayısı. Sıfır olamaz. Bunu
kullanmak için mod_logio etkin olmalıdır. | ||
%O |
- Başlıklar dahil gönderilen bayt sayısı. Sıfır olamaz. Bunu
- kullanmak için mod_logio etkin olmalıdır. | ||
%S |
+|||
%O |
+ Başlıklar dahil gönderilen bayt sayısı. Bir yanıtın
+ gönderilmesinden önce istekten vazgeçilmesi gibi nadir durumlarda
+ sıfır olabilir. Bunu kullanmak için mod_logio etkin
+ olmalıdır. | ||
%S |
Aktarılan bayt sayısı (alınan ve gönderilen), istekler ve başlıklar
dahil; sıfır olamaz. %I ve %O'nun birleşimidir. Bunu kullanmak için
mod_logio etkinleştirilmelidir. | ||
%{ALANADI}^ti |
+|||
%{ALANADI}^ti |
Sunucuya gönderilen istekteki ALANADI:
Trailer satır(lar)ının içeriği. | ||
%{VARNAME}^to |
+|||
%{VARNAME}^to |
Sunucudan gönderilen yanıttaki ALANADI:
Trailer satır(lar)ının içeriği. |
# Biçem dizgesi yerine takma ad içeren CustomLog LogFormat "%h %l %u %t \"%r\" %>s %b" common -CustomLog logs/access_log common +CustomLog "logs/access_log" common # Biçem dizgesinin kendisini içeren CustomLog -CustomLog logs/access_log "%h %l %u %t \"%r\" %>s %b"+CustomLog "logs/access_log" "%h %l %u %t \"%r\" %>s %b"
Üçüncü argüman isteğe bağlı olup,belli bir isteğin günlüğe kaydedilip @@ -438,15 +447,15 @@ CustomLog logs/access_log "%h %l %u %t \"%r\" %>s %b" isterseniz:
SetEnvIf Request_URI \.gif$ gif-image -CustomLog gif-requests.log common env=gif-image -CustomLog nongif-requests.log common env=!gif-image+CustomLog "gif-requests.log" common env=gif-image +CustomLog "nongif-requests.log" common env=!gif-image
Veya eski RefererIgnore
yönergesinin davranışını taklit
etmek isterseniz:
SetEnvIf Referer example\.com localreferer -CustomLog referer.log referer env=!localreferer+CustomLog "referer.log" referer env=!localreferer @@ -506,7 +515,7 @@ CustomLog referer.log referer env=!localreferer belirtilmedikçe Ortak Günlük Biçemi öntanımlıdır.
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-agent}i\"" -TransferLog logs/access_log+TransferLog "logs/access_log" diff --git a/docs/manual/mod/mod_logio.html.tr.utf8 b/docs/manual/mod/mod_logio.html.tr.utf8 index e3f43b03..3706245f 100644 --- a/docs/manual/mod/mod_logio.html.tr.utf8 +++ b/docs/manual/mod/mod_logio.html.tr.utf8 @@ -32,7 +32,6 @@ ko | tr -
Açıklama: | Her isteğin girdi ve çıktı uzunluklarının günlüklenmesi. |
---|---|
Durum: | Eklenti | Aktarılan bayt sayısı (alınan ve gönderilen), istekler ve başlıklar
dahil; sıfır olamaz. %I ve %O'nun birleşimidir. Apache 2.4.7 ve sonrasında kullanılabilmektedir. |
+
%^FB |
+ İstek gelip yanıt başlıklarının ilk baytı yazılana kadar mikrosaniye cinsinden geçen zaman. Sadece LogIOTrackTTFB yönergesine ON atanmışsa kullanılabilir.+ Apache 2.4.13 ve sonrasında kullanılabilir. |
Genel olarak, işlevsellik şöyle kullanılır:
@@ -101,16 +103,20 @@Açıklama: | Enable tracking of time to first byte (TTFB) |
---|---|
Açıklama: | İlk baytın yazılmasına kadar geçen süreyi izler |
Sözdizimi: | LogIOTrackTTFB ON|OFF |
Öntanımlı: | LogIOTrackTTFB OFF |
Bağlam: | sunucu geneli, sanal konak, dizin, .htaccess |
Geçersizleştirme: | none |
Durum: | Eklenti |
Modül: | mod_logio |
Uyumluluk: | Apache HTTP Server 2.4.13 and later |
Bu yönergenin belgesi henüz Türkçeye çevrilmedi. - Lütfen İngilizce sürümüne bakınız.
Bu yönerge isteğin okunmasından yanıt başlığının ilk baytının
+ yazılmasına kadar geçen sürenin izlenmesini yapılandırır. Sonuçlanan
+ değeri %^FB
biçemi ile günlüğe kaydettirebilirsiniz.
Mevcut Diller: en | diff --git a/docs/manual/mod/mod_lua.html.en b/docs/manual/mod/mod_lua.html.en index f5f6989e..f695985e 100644 --- a/docs/manual/mod/mod_lua.html.en +++ b/docs/manual/mod/mod_lua.html.en @@ -165,7 +165,7 @@ function handle(r) -- use our own Error contents r:puts("Unsupported HTTP method " .. r.method) r.status = 405 - return apache2.ok + return apache2.OK else -- use the ErrorDocument return 501 diff --git a/docs/manual/mod/mod_lua.html.fr b/docs/manual/mod/mod_lua.html.fr index a9581f7c..67f37bba 100644 --- a/docs/manual/mod/mod_lua.html.fr +++ b/docs/manual/mod/mod_lua.html.fr @@ -173,7 +173,7 @@ function handle(r) -- message d'erreur personnalis r:puts("Unsupported HTTP method " .. r.method) r.status = 405 - return apache2.ok + return apache2.OK else -- message d'erreur ErrorDocument return 501 diff --git a/docs/manual/mod/mod_proxy.html.en b/docs/manual/mod/mod_proxy.html.en index 81b70bfb..5ce4af60 100644 --- a/docs/manual/mod/mod_proxy.html.en +++ b/docs/manual/mod/mod_proxy.html.en @@ -58,7 +58,7 @@ capabilities
mod_proxy_balancer
and one or more
- balancer modules, if load balancing is required. (See
+ balancer modules if load balancing is required. (See
mod_proxy_balancer
for more information.)A reverse proxy (or gateway), by contrast, appears to the client just like an ordinary web server. No special configuration on the client is necessary. - The client makes ordinary requests for content in the name-space + The client makes ordinary requests for content in the namespace of the reverse proxy. The reverse proxy then decides where to - send those requests, and returns the content as if it was itself + send those requests and returns the content as if it were itself the origin.
A typical usage of a reverse proxy is to provide Internet users access to a server that is behind a firewall. Reverse proxies can also be used to balance load among several back-end - servers, or to provide caching for a slower back-end server. + servers or to provide caching for a slower back-end server. In addition, reverse proxies can be used simply to bring several servers into the same URL space.
@@ -238,7 +238,7 @@ ProxyVia OnThe proxy manages the configuration of origin servers and their communication parameters in objects called workers. - There are two built-in workers, the default forward proxy worker and the + There are two built-in workers: the default forward proxy worker and the default reverse proxy worker. Additional workers can be configured explicitly.
@@ -258,7 +258,7 @@ ProxyVia OnThis will create a worker associated with the origin server URL
- http://backend.example.com
and using the given timeout
+ http://backend.example.com
that will use the given timeout
values. When used in a forward proxy, workers are usually defined
via the ProxySet
directive:
Using explicitly configured workers in the forward mode is
not very common, because forward proxies usually communicate with many
different origin servers. Creating explicit workers for some of the
- origin servers can still be useful, if they are used very often.
+ origin servers can still be useful if they are used very often.
Explicitly configured workers have no concept of forward or reverse
proxying by themselves. They encapsulate a common concept of
communication with origin servers. A worker created by
ProxyPass
for use in a
- reverse proxy will be also used for forward proxy requests whenever
- the URL to the origin server matches the worker URL and vice versa.
The URL identifying a direct worker is the URL of its origin server including any path components given:
@@ -307,13 +307,13 @@ ProxyPass "/examples" "http://backend.example.com/examples" timeout=10 worker is used. The benefit is, that there is only one connection pool, so connections are more often reused. Note that all configuration attributes given explicitly for the later worker will be ignored. This will be logged - as a warning. In the above example the resulting timeout value + as a warning. In the above example, the resulting timeout value for the URL/examples
will be 60
instead
of 10
!
If you want to avoid worker sharing, sort your worker definitions
by URL length, starting with the longest worker URLs. If you want to maximize
- worker sharing use the reverse sort order. See also the related warning about
+ worker sharing, use the reverse sort order. See also the related warning about
ordering ProxyPass
directives.
ProxySet
.
The set of options available for a direct worker
- depends on the protocol, which is specified in the origin server URL.
+ depends on the protocol which is specified in the origin server URL.
Available protocols include ajp
, fcgi
,
ftp
, http
and scgi
.
You can control who can access your proxy via the <Proxy>
control block as in
the following example:
This directive allows for growth potential in the number of Balancers available for a virtualhost in addition to the number pre-configured. It only takes effect if there is at - least 1 pre-configured Balancer.
+ least one pre-configured Balancer.This directive adds a member to a load balancing group. It could be used +
This directive adds a member to a load balancing group. It can be used
within a <Proxy balancer://...>
container
- directive, and can take any of the key value pair parameters available to
+ directive and can take any of the key value pair parameters available to
ProxyPass
directives.
One additional parameter is available only to BalancerMember
directives:
loadfactor. This is the member load factor - a number between 1
(default) and 100, which defines the weighted load to be applied to the
member in question.
The balancerurl is only needed when not in +
The balancerurl is only needed when not within a
<Proxy balancer://...>
container directive. It corresponds to the url of a balancer defined in
ProxyPass
directive.
Domain name comparisons are done without regard to the case, and
Domains are always assumed to be anchored in the root of the
- DNS tree, therefore two domains .ExAmple.com
and
+ DNS tree; therefore, the two domains .ExAmple.com
and
.example.com.
(note the trailing period) are considered
equal. Since a domain comparison does not involve a DNS lookup, it is much
more efficient than subnet comparison.
Hostname comparisons are done without regard to the case,
and Hostnames are always assumed to be anchored in the root
- of the DNS tree, therefore two hosts WWW.ExAmple.com
+ of the DNS tree; therefore, the two hosts WWW.ExAmple.com
and www.example.com.
(note the trailing period) are
considered equal.
The ProxyBadHeader
directive determines the
- behaviour of mod_proxy
if it receives syntactically invalid
+ behavior of mod_proxy
if it receives syntactically invalid
response header lines (i.e. containing no colon) from the origin
server. The following arguments are possible:
IsError
Ignore
This directive is useful for reverse-proxy setups, where you want to +
This directive is useful for reverse-proxy setups where you want to
have a common look and feel on the error pages seen by the end user.
This also allows for included files (via
mod_include
's SSI) to get
- the error code and act accordingly (default behavior would display
- the error page of the proxied server, turning this on shows the SSI
- Error message).
This directive does not affect the processing of informational (1xx), normal success (2xx), or redirect (3xx) responses.
@@ -876,12 +876,12 @@ proxiedThe ProxyIOBufferSize
directive adjusts the size
- of the internal buffer, which is used as a scratchpad for the data between
+ of the internal buffer which is used as a scratchpad for the data between
input and output. The size must be at least 512
.
In almost every case there's no reason to change that value.
+In almost every case, there's no reason to change that value.
-If used with AJP this directive sets the maximum AJP packet size in +
If used with AJP, this directive sets the maximum AJP packet size in
bytes. Values larger than 65536 are set to 65536. If you change it from
the default, you must also change the packetSize
attribute of
your AJP connector on the Tomcat side! The attribute
@@ -905,7 +905,7 @@ proxied resources
The <ProxyMatch>
directive is
- identical to the <Proxy>
directive, except it matches URLs
+ identical to the <Proxy>
directive, except that it matches URLs
using regular expressions.
From 2.4.8 onwards, named groups and backreferences are captured and @@ -938,9 +938,9 @@ through
The ProxyMaxForwards
directive specifies the
- maximum number of proxies through which a request may pass, if there's no
+ maximum number of proxies through which a request may pass if there's no
Max-Forwards
header supplied with the request. This may
- be set to prevent infinite proxy loops, or a DoS attack.
ProxyMaxForwards 15
Max-Forwards
if the Client didn't set it.
Earlier Apache httpd versions would always set it. A negative
ProxyMaxForwards
value, including the
- default -1, gives you protocol-compliant behaviour, but may
+ default -1, gives you protocol-compliant behavior but may
leave you open to loops.
@@ -966,8 +966,8 @@ through
This directive allows remote servers to be mapped into the - space of the local server; the local server does not act as a - proxy in the conventional sense, but appears to be a mirror of the + space of the local server. The local server does not act as a + proxy in the conventional sense but appears to be a mirror of the remote server. The local server is often called a reverse proxy or gateway. The path is the name of a local virtual path; url is a partial URL for the @@ -982,12 +982,18 @@ through
In 2.4.7 and later, support for using a Unix Domain Socket is available by using a target
which prepends unix:/path/lis.sock|
. For example, to proxy
- HTTP and target the UDS at /home/www/socket you would use
+ HTTP and target the UDS at /home/www/socket, you would use
unix:/home/www.socket|http://localhost/whatever/
.
unix:
URL is DefaultRuntimeDir
aware.When used inside a <Location>
section, the first argument is omitted and the local
+ directory is obtained from the <Location>
. The same will occur inside a
+ <LocationMatch>
section;
+ however, ProxyPass does not interpret the regexp as such, so it is necessary
+ to use ProxyPassMatch
in this situation instead.
Suppose the local server has address http://example.com/
;
then
http://example.com/mirror/foo/bar
to be internally converted
into a proxy request to http://backend.example.com/bar
.
- The following alternative syntax is possible, however it can carry a +
The ProxyPass directive is not supported in <Directory>
or <Files>
sections.
If you require a more flexible reverse-proxy configuration, see the
+ RewriteRule
directive with the
+ [P]
flag.
The following alternative syntax is possible; however, it can carry a performance penalty when present in very large numbers. The advantage of the below syntax is that it allows for dynamic control via the Balancer Manager interface:
@@ -1010,8 +1022,8 @@ throughIf the first argument ends with a trailing /, the second - argument should also end with a trailing / and vice - versa. Otherwise the resulting requests to the backend may miss some + argument should also end with a trailing /, and vice + versa. Otherwise, the resulting requests to the backend may miss some needed slashes and do not deliver the expected results.
ProxyPass
rules starting with the
- longest URLs first. Otherwise later rules for longer URLS will be hidden
+ longest URLs first. Otherwise, later rules for longer URLS will be hidden
by any earlier rule which uses a leading substring of the URL. Note that
there is some relation with worker sharing. In contrast, only one
ProxyPass
directive can be placed
in a Location
block, and the most
specific location will take precedence.
- For the same reasons exclusions must come before the +
For the same reasons, exclusions must come before the
general ProxyPass
directives.
ProxyPass key=value
Parameters
In Apache HTTP Server 2.1 and later, mod_proxy supports pooled
connections to a backend server. Connections created on demand
can be retained in a pool for future use. Limits on the pool size
and other settings can be coded on
the ProxyPass
directive
- using key=value
parameters, described in the table
+ using key=value
parameters, described in the tables
below.
By default, mod_proxy will allow and retain the maximum number of @@ -1094,7 +1108,7 @@ ProxyPass "/mirror/foo" "http://backend.example.com"
ThreadsPerChild
directive.SERVER_BUSY
+ connections in the pool, the Apache httpd will return SERVER_BUSY
status to the client.
This parameter should be used when you have a firewall between your
- Apache httpd and the backend server, who tend to drop inactive connections.
+ Apache httpd and the backend server, which tends to drop inactive connections.
This flag will tell the Operating System to send KEEP_ALIVE
- messages on inactive connections and thus prevent the firewall to drop the connection.
- To enable keepalive set this property value to On
.
On
.
The frequency of initial and subsequent TCP keepalive probes depends on global OS settings, and may be as high as 2 hours. To be useful, the frequency configured in the OS must be smaller than the threshold used @@ -1180,19 +1195,19 @@ ProxyPass "/mirror/foo" "http://backend.example.com"
mod_proxy_ajp
to send a CPING
+ mod_proxy_ajp
to send a CPING
request on the ajp13 connection (implemented on Tomcat 3.3.2+, 4.1.28+
and 5.0.13+). For HTTP, it causes mod_proxy_http
to send a 100-Continue
to the backend (only valid for
HTTP/1.1 - for non HTTP/1.1 backends, this property has no
- effect). In both cases the parameter is the delay in seconds to wait
+ effect). In both cases, the parameter is the delay in seconds to wait
for the reply.
This feature has been added to avoid problems with hung and
busy backends.
This will increase the network traffic during the normal operation
which could be an issue, but it will lower the
traffic in case some of the cluster nodes are down or busy.
- By adding a postfix of ms the delay can be also set in
+ By adding a postfix of ms, the delay can be also set in
milliseconds.
D: Worker is disabled and will not accept any requests. |
S: Worker is administratively stopped. |
I: Worker is in ignore-errors mode, and will always be considered available. |
I: Worker is in ignore-errors mode and will always be considered available. |
H: Worker is in hot-standby mode and will only be used if no other viable workers are available. |
E: Worker is in an error state. |
N: Worker is in drain mode, and will only accept existing sticky sessions + |
N: Worker is in drain mode and will only accept existing sticky sessions destined for itself and ignore all other requests. |
If the Proxy directive scheme starts with the
balancer://
(eg: balancer://cluster
,
- any path information is ignored) then a virtual worker that does not really
- communicate with the backend server will be created. Instead it is responsible
- for the management of several "real" workers. In that case the special set of
- parameters can be add to this virtual worker. See mod_proxy_balancer
- for more information about how the balancer works.
+ any path information is ignored), then a virtual worker that does not really
+ communicate with the backend server will be created. Instead, it is responsible
+ for the management of several "real" workers. In that case, the special set of
+ parameters can be added to this virtual worker.
+ See mod_proxy_balancer
for more information about how
+ the balancer works.
Balancer parameters |
---|
byrequests | Balancer load-balance method. Select the load-balancing scheduler
method to use. Either byrequests , to perform weighted
- request counting, bytraffic , to perform weighted
- traffic byte count balancing, or bybusyness , to perform
- pending request balancing. Default is byrequests .
+ request counting; bytraffic , to perform weighted
+ traffic byte count balancing; or bybusyness , to perform
+ pending request balancing. The default is byrequests .
|
||
maxattempts | One less than the number of workers, or 1 with a single worker. | @@ -1285,7 +1301,7 @@ ProxyPass "/mirror/foo" "http://backend.example.com"||
nofailover | Off | -If set to On the session will break if the worker is in
+ | If set to On , the session will break if the worker is in
error state or disabled. Set this value to On if backend
servers do not support session replication.
|
stickysessionsep | "." | Sets the separation symbol in the session cookie. Some backend application servers - do not use the '.' as the symbol. For example the Oracle Weblogic server uses + do not use the '.' as the symbol. For example, the Oracle Weblogic server uses '!'. The correct symbol can be set using this option. The setting of 'Off' signifies that no symbol is used. | |
scolonpathdelim | Off | -If set to On the semi-colon character ';' will be
+ | If set to On , the semi-colon character ';' will be
used as an additional sticky session path delimiter/separator. This
is mainly used to emulate mod_jk's behavior when dealing with paths such
as JSESSIONID=6736bcf34;foo=aabfa
|
timeout | 0 | -Balancer timeout in seconds. If set this will be the maximum time - to wait for a free worker. Default is not to wait. + | Balancer timeout in seconds. If set, this will be the maximum time + to wait for a free worker. The default is to not wait. |
failonstatus | - | -A single or comma-separated list of HTTP status codes. If set this will + | A single or comma-separated list of HTTP status codes. If set, this will force the worker into error state when the backend returns any status code in the list. Worker recovery behaves the same as other worker errors. |
A sample balancer setup
+A sample balancer setup:
ProxyPass "/special-area" "http://special.example.com" smax=5 max=10 ProxyPass "/" "balancer://mycluster/" stickysession=JSESSIONID|jsessionid nofailover=On <Proxy "balancer://mycluster"> @@ -1371,8 +1387,8 @@ ProxyPass "/" "balancer://mycluster/" stickysession=JSESSIONID|jsessionid nofail </Proxy>-
Setting up a hot-standby, that will only be used if no other - members are available
+Setting up a hot-standby that will only be used if no other + members are available:
ProxyPass "/" "balancer://hotcluster/" <Proxy "balancer://hotcluster"> BalancerMember "ajp://1.2.3.4:8009" loadfactor=1 @@ -1383,12 +1399,14 @@ ProxyPass "/" "balancer://mycluster/" stickysession=JSESSIONID|jsessionid nofail </Proxy>+
Additional ProxyPass Keywords
+Normally, mod_proxy will canonicalise ProxyPassed URLs. But this may be incompatible with some backends, particularly those that make use of PATH_INFO. The optional nocanon - keyword suppresses this, and passes the URL path "raw" to the - backend. Note that may affect the security of your backend, as it - removes the normal limited protection against URL-based attacks + keyword suppresses this and passes the URL path "raw" to the + backend. Note that this keyword may affect the security of your backend, + as it removes the normal limited protection against URL-based attacks provided by the proxy.
Normally, mod_proxy will include the query string when @@ -1396,20 +1414,8 @@ ProxyPass "/" "balancer://mycluster/" stickysession=JSESSIONID|jsessionid nofail The optional noquery keyword (available in httpd 2.4.1 and later) prevents this.
-When used inside a <Location>
section, the first argument is omitted and the local
- directory is obtained from the <Location>
. The same will occur inside a
- <LocationMatch>
section,
- however ProxyPass does not interpret the regexp as such, so it is necessary
- to use ProxyPassMatch
in this situation instead.
This directive is not supported in <Directory>
or <Files>
sections.
If you require a more flexible reverse-proxy configuration, see the
- RewriteRule
directive with the
- [P]
flag.
The optional interpolate keyword, in combination with
- ProxyPassInterpolateEnv
causes the ProxyPass
+ ProxyPassInterpolateEnv
, causes the ProxyPass
to interpolate environment variables, using the syntax
${VARNAME}. Note that many of the standard CGI-derived
environment variables will not exist when this interpolation happens,
@@ -1442,7 +1448,7 @@ ProxyPassReverse "/mirror/foo/" "https://backend.example.com/"
This directive will cause the current server/vhost to "inherit"
ProxyPass
@@ -1466,18 +1472,18 @@ ProxyPassReverse "/mirror/foo/" "https://backend.example.com/"
This directive, together with the interpolate argument to
ProxyPass
, ProxyPassReverse
,
- ProxyPassReverseCookieDomain
and
- ProxyPassReverseCookiePath
+ ProxyPassReverseCookieDomain
, and
+ ProxyPassReverseCookiePath
,
enables reverse proxies to be dynamically
- configured using environment variables, which may be set by
+ configured using environment variables which may be set by
another module such as mod_rewrite
.
It affects the ProxyPass
,
ProxyPassReverse
,
ProxyPassReverseCookieDomain
, and
- ProxyPassReverseCookiePath
directives,
+ ProxyPassReverseCookiePath
directives
and causes them to substitute the value of an environment
variable varname
for the string ${varname}
- in configuration directives (if the interpolate option is set).
Keep this turned off (for server performance) unless you need it!
@@ -1491,8 +1497,8 @@ ProxyPassReverse "/mirror/foo/" "https://backend.example.com/"This directive is equivalent to ProxyPass
,
- but makes use of regular expressions, instead of simple prefix matching. The
+
This directive is equivalent to ProxyPass
+ but makes use of regular expressions instead of simple prefix matching. The
supplied regular expression is matched against the url, and if it
matches, the server will substitute any parenthesized matches into the given
string and use it as a new url.
Take care when constructing the target URL of the rule, considering the security impact from allowing the client influence over the set of URLs to which your server will act as a proxy. Ensure that the scheme - and hostname part of the URL is either fixed, or does not allow the + and hostname part of the URL is either fixed or does not allow the client undue influence.
@@ -1562,7 +1568,7 @@ proxied serverThis directive lets Apache httpd adjust the URL in the Location
,
Content-Location
and URI
headers on HTTP
redirect responses. This is essential when Apache httpd is used as a
- reverse proxy (or gateway) to avoid by-passing the reverse proxy
+ reverse proxy (or gateway) to avoid bypassing the reverse proxy
because of HTTP redirects on the backend servers which stay behind
the reverse proxy.
mod_proxy_html
.
- path is the name of a local virtual path. url is a - partial URL for the remote server - the same way they are used for the +
path is the name of a local virtual path; url is a
+ partial URL for the remote server.
+ These parameters are used the same way as for the
ProxyPass
directive.
For example, suppose the local server has address @@ -1590,16 +1597,16 @@ ProxyPassReverseCookiePath "/" "/mirror/foo/"
will not only cause a local request for the
http://example.com/mirror/foo/bar
to be internally converted
into a proxy request to http://backend.example.com/bar
- (the functionality ProxyPass
provides here). It also takes care
- of redirects the server backend.example.com
sends: when
- http://backend.example.com/bar
is redirected by him to
- http://backend.example.com/quux
Apache httpd adjusts this to
+ (the functionality which ProxyPass
provides here).
+ It also takes care of redirects which the server backend.example.com
+ sends when redirecting http://backend.example.com/bar
to
+ http://backend.example.com/quux
. Apache httpd adjusts this to
http://example.com/mirror/foo/quux
before forwarding the HTTP
redirect response to the client. Note that the hostname used for
constructing the URL is chosen in respect to the setting of the UseCanonicalName
directive.
Note that this ProxyPassReverse
directive can
- also be used in conjunction with the proxy pass-through feature
+ also be used in conjunction with the proxy feature
(RewriteRule ... [P]
) from mod_rewrite
because it doesn't depend on a corresponding ProxyPass
directive.
<Location>
. The same occurs inside a <LocationMatch>
section, but will probably not work as
intended, as ProxyPassReverse will interpret the regexp literally as a
path; if needed in this situation, specify the ProxyPassReverse outside
- the section, or in a separate <Location>
section.
+ the section or in a separate <Location>
section.
This directive is not supported in <Directory>
or <Files>
sections.
When enabled, this option will pass the Host: line from the incoming
request to the proxied host, instead of the hostname specified in the
- ProxyPass
line.
ProxyPass
line.
This option should normally be turned Off
. It is mostly
useful in special configurations like proxied mass name-based virtual
@@ -1744,7 +1751,7 @@ ProxyRemote "ftp" "http://ftpproxy.mydomain:8080"
as yet another HTTP proxy request, to another proxy which can handle
them.
This option also supports reverse proxy configuration - a backend +
This option also supports reverse proxy configuration; a backend webserver can be embedded within a virtualhost URL space even if that server is hidden by another forward proxy.
@@ -1760,7 +1767,7 @@ expressionsThe ProxyRemoteMatch
is identical to the
- ProxyRemote
directive, except the
+ ProxyRemote
directive, except that the
first argument is a regular expression
match against the requested URL.
Keep in mind that the same parameter key can have a different meaning - depending whether it is applied to a balancer or a worker as shown by the two + depending whether it is applied to a balancer or a worker, as shown by the two examples above regarding timeout.
Description: | Serveur mandataire/passerelle multi-protocole |
---|---|
Statut: | Extension |
IdentificateurdeModule: | proxy_module |
Cette directive permet de rfrencer des serveurs distants depuis
- l'espace d'URLs du serveur local ; le serveur
+ l'espace d'URLs du serveur local. Le serveur
local n'agit pas en tant que mandataire au sens conventionnel, mais
plutt comme miroir du serveur distant. Le serveur local est
souvent nomm mandataire inverse ou
@@ -1113,6 +1111,15 @@ sont support
unix:
tient compte de la directive
DefaultRuntimeDir
.
+
Lorsque cette directive est utilise dans une section <Location>
, le premier
+ argument est omis et le rpertoire local est obtenu partir de
+ l'argument de la directive <Location>
. Il en est de mme l'intrieur
+ d'une section <LocationMatch>
, mais le rsultat ne sera
+ probablement pas celui attendu car ProxyPassReverse va interprter
+ l'expression rationnelle littralement comme un chemin ; si besoin
+ est dans ce cas, dfinissez la directive ProxyPassReverse en dehors
+ de la section, ou dans une section <Location>
spare.
Supposons que le serveur local a pour adresse
http://example.com/
; alors la ligne
http://example.com/miroir/foo/bar
en une requte
mandate pour http://backend.example.com/bar
.
+ La directive ProxyPass ne peut pas tre place dans une section
+ <Directory>
ou
+ <Files>
.
Si vous avez besoin d'un configuration de mandataire inverse plus
+ souple, reportez-vous la documentaion de la directive RewriteRule
et son drapeau
+ [P]
.
La syntaxe alternative suivante est valide, bien qu'elle puisse induire une dgradation des performances lorsqu'elle est prsente en trs grand nombre. Elle possde l'avantage de @@ -1180,14 +1195,16 @@ ProxyPass "/mirror/foo" "http://backend.example.com" +
ProxyPass cl=valeur
Paramtres
Depuis la version 2.1 du serveur HTTP Apache, mod_proxy supporte
les groupements de connexions vers un serveur d'arrire-plan. Les
connexions cres la demande peuvent tre enregistres dans un
groupement pour une utilisation ultrieure. La taille du groupe
ainsi que d'autres caractristiques peuvent tre dfinies via la
directive ProxyPass
au moyen de paramtres
- cl=valeur
dont la description fait l'objet du tableau
- ci-dessous.
cl=valeur
dont la description fait l'objet des
+ tableaux ci-dessous.
Par dfaut, mod_proxy permet et met en rserve le nombre maximum de connexions pouvant tre utilises simultanment par le processus @@ -1281,8 +1298,9 @@ ProxyPass "/mirror/foo" "http://backend.example.com"
On
, la session va
s'interrompre si le serveur cible est dans un tat d'erreur ou
- dsactiv. Dfinissez ce paramtre On si le serveur
+ dsactiv. Dfinissez ce paramtre On
si le serveur
d'arrire-plan ne supporte pas la rplication de session.
JSESSIONID
ou
PHPSESSIONID
, et dpend du serveur d'application
d'arrire-plan qui supporte les sessions. Si le serveur
- d'application d'arrire-plan utilise des noms diffrents pour
+ d'application d'arrire-plan utilise un nom diffrent pour
les cookies et les identifiants cods d'URL (comme les
conteneurs de servlet), sparez-les par le caractre '|'. La
premire partie contient le cookie et la seconde le chemin.Mots-cls additionnels de ProxyPass
+Normalement, mod_proxy va mettre sous leur forme canonique les URLs traites par ProxyPass. Mais ceci peut tre incompatible avec certains serveurs d'arrire-plan, et en particulier avec ceux qui @@ -1793,8 +1813,9 @@ par un serveur mandat
chemin est le nom d'un chemin virtuel local.
- url est une URL partielle pour le serveur distant - ils
- sont utiliss de la mme faon qu'avec la directive ProxyPass
.
ProxyPass
.
Supposons par exemple que le serveur local a pour adresse
http://example.com/
; alors
http://backend.example.com/bar
(la fonctionnalit fournie par ProxyPass
). Il va
aussi s'occuper des redirections que le serveur
- backend.example.com
envoie : lorsque
- http://backend.example.com/bar
est redirig par
- celui-ci vers http://backend.example.com/quux
, Apache
+ backend.example.com
envoie lorsqu'il redirige
+ http://backend.example.com/bar
vers
+ http://backend.example.com/quux
. Apache
httpd corrige ceci en http://example.com/miroir/foo/quux
avant de faire suivre la redirection HTTP au client. Notez que le
nom d'hte utilis pour construire l'URL est choisi en respectant la
dfinition de la directive UseCanonicalName
.
Notez que la directive ProxyPassReverse
- peut aussi tre utilise en conjonction avec la fonctionnalit
- pass-through (RewriteRule ... [P]
) du module
+ peut aussi tre utilise en conjonction avec la
+ fonctionnalit de mandataire
+ (RewriteRule ... [P]
) du module
mod_rewrite
, car elle ne dpend pas d'une directive
ProxyPass
correspondante.
Lorsqu'elle est active, cette directive va transmettre l'en-tte
Host: de la requte entrante vers le serveur mandat, au lieu du nom
- d'hte spcifi par la directive ProxyPass
.
ProxyPass
.
Cette directive est habituellement dfinie Off
.
Elle est principalement utile dans les configurations particulires
@@ -1983,7 +2005,7 @@ ProxyRemote "ftp" "http://ftpproxy.mydomain:8080"
HTTP, vers un autre mandataire capable de les traiter.
Cette directive supporte aussi les configurations de mandataire - inverse - un serveur web d'arrire-plan peut tre intgr dans + inverse ; un serveur web d'arrire-plan peut tre intgr dans l'espace d'URL d'un serveur virtuel, mme si ce serveur est cach par un autre mandataire direct.
diff --git a/docs/manual/mod/mod_proxy.html.ja.utf8 b/docs/manual/mod/mod_proxy.html.ja.utf8 index 2519a3b2..fd6a41b7 100644 --- a/docs/manual/mod/mod_proxy.html.ja.utf8 +++ b/docs/manual/mod/mod_proxy.html.ja.utf8 @@ -925,7 +925,7 @@このディレクティブの解説文書は まだ翻訳されていません。英語版をご覧ください。
diff --git a/docs/manual/mod/mod_rewrite.html.en b/docs/manual/mod/mod_rewrite.html.en index ecacc71c..a5a44289 100644 --- a/docs/manual/mod/mod_rewrite.html.en +++ b/docs/manual/mod/mod_rewrite.html.en @@ -361,7 +361,7 @@ AliasMatch "^/myapp" "/opt/myapp-1.2.3"QUERY_STRING
.THE_REQUEST
mod_ssl
is loaded, but will always expand to
the empty string if it is not. Example:
%{SSL:SSL_CIPHER_USEKEYSIZE}
may expand to
- 128
.
+ 128
. These variables are available even without
+ setting the StdEnvVars
option of the
+ SSLOptions
directive.
%{HTTP:header}
, where header can be
diff --git a/docs/manual/mod/mod_rewrite.html.fr b/docs/manual/mod/mod_rewrite.html.fr
index 67a9981f..c7401c43 100644
--- a/docs/manual/mod/mod_rewrite.html.fr
+++ b/docs/manual/mod/mod_rewrite.html.fr
@@ -29,6 +29,8 @@
+Description: | Ce module fournit un moteur de rcriture base de rgles permettant de rcrire les URLs des requtes la vole |
---|
Description: | Keepalive time for idle connections |
---|---|
Syntax: | MemcacheConnTTL num[units] |
Default: | MemcacheConnTTL 15s |
Context: | server config, virtual host |
Status: | Extension |
Module: | mod_socache_memcache |
Compatibility: | Available in Apache 2.4.17 and later |
Set the time to keep idle connections with the memcache server(s) + alive (threaded platforms only).
+ +Valid values for MemcacheConnTTL
are times
+ up to one hour. 0 means no timeout.
This timeout defaults to units of seconds, but accepts + suffixes for milliseconds (ms), seconds (s), minutes (min), and hours (h). +
Before Apache 2.4.17, this timeout was hardcoded and its value was 600 usec.
+ So, the closest configuration to match the legacy behaviour is to set
+ MemcacheConnTTL
to 1ms.
# Set a timeout of 10 minutes +MemcacheConnTTL 10min +# Set a timeout of 60 seconds +MemcacheConnTTL 60+
Available Languages: en | diff --git a/docs/manual/mod/mod_socache_memcache.html.fr b/docs/manual/mod/mod_socache_memcache.html.fr index 184c7e93..95af8778 100644 --- a/docs/manual/mod/mod_socache_memcache.html.fr +++ b/docs/manual/mod/mod_socache_memcache.html.fr @@ -58,9 +58,50 @@
Description: | Dure de conservation des connexions inactives |
---|---|
Syntaxe: | MemcacheConnTTL num[units] |
Dfaut: | MemcacheConnTTL 15s |
Contexte: | configuration du serveur, serveur virtuel |
Statut: | Extension |
Module: | mod_socache_memcache |
Compatibilit: | Disponible partir de la version 2.4.17 du serveur HTTP +Apache. |
Dfinit la dure pendant laquelle les connexions + inactives avec le(s) serveur(s) memcache seront conserves + (plateformes threades seulement).
+ +Les valeurs valides de la directive
+ MemcacheConnTTL
sont des dures d'une heure
+ maximum. La valeur 0 signifie une absence de premption
L'unit par dfaut pour ce dlai est la seconde, mais vous + pouvez ajouter un suffixe pour spcifier une unit diffrente ; ms + pour milliseconde, s pour seconde, min pour minute et h pour heure.. +
Dans les versions antrieures 2.4.17, ce dlai tait cod en
+ dur et sa valeur tait 600 microsecondes. La valeur la plus proche
+ de cette ancienne valeur pour la directive
+ MemcacheConnTTL
est donc 1ms.
# Dfinition d'un dlai de 10 minutes +MemcacheConnTTL 10min +# Dfinition d'un dlai de 60 secondes +MemcacheConnTTL 60+
Langues Disponibles: en | diff --git a/docs/manual/mod/mod_ssl.html.en b/docs/manual/mod/mod_ssl.html.en index 206537f0..6a0c4614 100644 --- a/docs/manual/mod/mod_ssl.html.en +++ b/docs/manual/mod/mod_ssl.html.en @@ -160,6 +160,7 @@ compatibility variables.
SSL_CLIENT_S_DN_
x509SSL_CLIENT_SAN_Email_
nSSL_CLIENT_SAN_DNS_
nSSL_CLIENT_SAN_OTHER_msUPN_
nSSL_CLIENT_I_DN
SSL_CLIENT_I_DN_
x509SSL_CLIENT_V_START
SSL_SERVER_S_DN
SSL_SERVER_SAN_Email_
nSSL_SERVER_SAN_DNS_
nSSL_SERVER_SAN_OTHER_dnsSRV_
nSSL_SERVER_S_DN_
x509SSL_SERVER_I_DN
SSL_SERVER_I_DN_
x509CustomLog "logs/ssl_request_log" "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b"
These formats even work without setting the StdEnvVars
+option of the SSLOptions
+directive.
-Finally the the end-entity certificate's private key can also be
+Finally the end-entity certificate's private key can also be
added to the certificate file instead of using a separate
SSLCertificateKeyFile
directive. This practice is highly discouraged. If it is used,
@@ -769,8 +774,8 @@ prefixes are:
aNULL
, eNULL
and EXP
ciphers are always disabledBeginning with version 2.4.7, null and export-grade
-ciphers are always disabled, as mod_ssl unconditionally prepends any supplied
-cipher suite string with !aNULL:!eNULL:!EXP:
at initialization.
!aNULL:!eNULL:!EXP
to any cipher string at initialization.
A simpler way to look at all of this is to use the ``openssl ciphers
@@ -1118,7 +1123,7 @@ features are added to OpenSSL.
mod_ssl
(at least version 1.0.2 is required). For a list of supported command
names, see the section Supported configuration file commands in the
-SSL_CONF_cmd(3) manual page for OpenSSL.
+SSL_CONF_cmd(3) manual page for OpenSSL.
Some of the SSLOpenSSLConfCmd
commands can be used
as an alternative to existing directives (such as
@@ -1333,7 +1338,7 @@ query can be done in two ways which can be configured by
Description: | Configure usable SSL/TLS protocol versions | |
---|---|---|
Syntax: | SSLProtocol [+|-]protocol ... | |
Default: | SSLProtocol all | |
Default: | SSLProtocol all -SSLv3 (up to 2.4.16: all) | |
Context: | server config, virtual host | |
Status: | Extension | |
Module: | mod_ssl |
Description: | Configure usable SSL protocol flavors for proxy usage | |
---|---|---|
Syntax: | SSLProxyProtocol [+|-]protocol ... | |
Default: | SSLProxyProtocol all | |
Default: | SSLProxyProtocol all -SSLv3 (up to 2.4.16: all) | |
Context: | server config, virtual host | |
Override: | Options | |
Status: | Extension |
Description: | Chiffrement de haut niveau bas sur les protocoles Secure Sockets Layer (SSL) et Transport Layer Security (TLS) | |
---|---|---|
Statut: | Extension | Les entres d'extension subjectAltName du certificat client de type rfc822Name |
SSL_CLIENT_SAN_DNS_ n | chane | Les entres d'extension subjectAltName du certificat client de type dNSName |
SSL_CLIENT_SAN_OTHER_msUPN_ n |
+chane | Extensions subjectAltName de type otherName du +certificat client, forme Microsoft du nom principal de l'utilisateur (OID 1.3.6.1.4.1.311.20.2.3) |
SSL_CLIENT_I_DN | chane | DN de l'metteur du certificat du client |
SSL_CLIENT_I_DN_ x509 | chane | @@ -226,6 +231,9 @@ certificat de serveur de type rfc822Name|
SSL_SERVER_SAN_DNS_ n | chane | Les entres d'extension subjectAltName du certificat de serveur de type dNSName |
SSL_SERVER_SAN_OTHER_dnsSRV_ n |
+chane | Extensions subjectAltName de type otherName du +certificat serveur, sous la forme SRVName (OID 1.3.6.1.5.5.7.8.7, RFC 4985) |
SSL_SERVER_I_DN | chane | DN de l'metteur du certificat du serveur |
SSL_SERVER_I_DN_ x509 | chane | @@ -892,9 +900,9 @@ peut plus y|
Description: | Indique les versions du protocole SSL/TLS disponibles | |
Syntaxe: | SSLProtocol [+|-]protocole ... | |
Dfaut: | SSLProtocol all | |
Dfaut: | SSLProtocol all -SSLv3 (jusqu' la version 2.4.16 : all) | |
Contexte: | configuration du serveur, serveur virtuel | |
Statut: | Extension | |
Module: | mod_ssl | |
Description: | Dfinit les protocoles SSL disponibles pour la fonction de mandataire | |
Syntaxe: | SSLProxyProtocol [+|-]protocole ... | |
Dfaut: | SSLProxyProtocol all | |
Dfaut: | SSLProxyProtocol all -SSLv3 (jusqu' la version 2.4.16: all) | |
Contexte: | configuration du serveur, serveur virtuel | |
AllowOverride: | Options | |
Statut: | Extension |
Açıklama: | Sunucu etkinliği ve başarımı hakkında bilgi sağlar. |
---|---|
Durum: | Temel |
Modül Betimleyici: | status_module |
Description: | Change the merge order of inherited patterns |
---|---|
Syntax: | SubstituteInheritBefore on|off |
Default: | SubstituteInheritBefore off |
Context: | directory, .htaccess |
Override: | FileInfo |
Status: | Extension |
Module: | mod_substitute |
Compatibility: | Available in httpd 2.4.17 and later |
Whether to apply the inherited Substitute
+ patterns first (on
), or after the ones of the current
+ context (off
).
+ SubstituteInheritBefore
is itself inherited,
+ hence contexts that inherit it (those that don't specify their own
+ SubstituteInheritBefore
value) will apply the
+ closest defined merge order.
Description: | Effectue des oprations de recherche/remplacement sur les corps de rponses |
---|---|
Statut: | Extension |
Description: | Change the merge order of inherited patterns |
---|---|
Syntaxe: | SubstituteInheritBefore on|off |
Dfaut: | SubstituteInheritBefore off |
Contexte: | rpertoire, .htaccess |
AllowOverride: | FileInfo |
Statut: | Extension |
Module: | mod_substitute |
Compatibilit: | Available in httpd 2.4.17 and later |
La documentation de cette directive + n'a pas encore t traduite. Veuillez vous reporter la version + en langue anglaise.
Description: | Dfinit la longueur de ligne maximale |
---|
Açıklama: | Kitlesel sanal konakların devingen olarak yapılandırılmasını sağlar |
---|---|
Durum: | Eklenti |
Modül Betimleyici: | vhost_alias_module |
Voreinstellung: | GracefulShutdownTimeout 0 |
Kontext: | Serverkonfiguration |
Status: | MPM |
Modul: | prefork , worker , event |
Modul: | event , worker , prefork |
Kompatibilitt: | Available in version 2.2 and later |
Die Dokumentation zu dieser Direktive wurde noch nicht bersetzt. Bitte schauen Sie in die englische @@ -224,6 +225,24 @@ will exit.
+Beschreibung: | Ratio between the number of CPU cores (online) and the number of +listeners' buckets |
---|---|
Syntax: | ListenCoresBucketsRatio ratio |
Voreinstellung: | ListenCoresBucketsRatio 0 (disabled) |
Kontext: | Serverkonfiguration |
Status: | MPM |
Modul: | event , worker , prefork |
Kompatibilitt: | Available in Apache HTTP Server 2.4.17, with a kernel supporting
+the socket option SO_REUSEPORT and distributing new connections
+evenly accross listening processes' (or threads') sockets using it (eg. Linux
+3.9 and later, but not the current implementations of SO_REUSEPORT
+in *BSDs. |
Die Dokumentation zu dieser Direktive wurde + noch nicht bersetzt. Bitte schauen Sie in die englische + Version.
Beschreibung: | Limit on the number of connections that an individual child server @@ -232,7 +251,7 @@ will handle during its life |
---|---|
Voreinstellung: | MaxConnectionsPerChild 0 |
Kontext: | Serverkonfiguration |
Status: | MPM |
Modul: | event , mpm_netware , mpm_winnt , mpmt_os2 , prefork , worker |
Modul: | event , worker , prefork , mpm_winnt , mpm_netware , mpmt_os2 |
Kompatibilitt: | Available Apache HTTP Server 2.3.9 and later. The old name
MaxRequestsPerChild is still supported. |
Die Dokumentation zu dieser Direktive wurde @@ -265,7 +284,7 @@ simultaneously
See usage for details
event
, prefork
, worker
event
, worker
, prefork
Die Dokumentation zu dieser Direktive wurde noch nicht bersetzt. Bitte schauen Sie in die englische Version.
ReceiveBufferSize 0
event
, mpm_netware
, mpm_winnt
, mpmt_os2
, prefork
, worker
event
, worker
, prefork
, mpm_winnt
, mpm_netware
, mpmt_os2
Die Dokumentation zu dieser Direktive wurde noch nicht bersetzt. Bitte schauen Sie in die englische Version.
diff --git a/docs/manual/mod/mpm_common.html.en b/docs/manual/mod/mpm_common.html.en index 4e53e370..61ef48ec 100644 --- a/docs/manual/mod/mpm_common.html.en +++ b/docs/manual/mod/mpm_common.html.en @@ -43,6 +43,7 @@ more than one multi-processing module (MPM)See usage for the default setting
event
, prefork
, worker
event
, worker
, prefork
This controls the directory to which Apache httpd attempts to switch before dumping core. If your operating system is configured to @@ -119,7 +120,7 @@ after a crash
EnableExceptionHook Off
event
, prefork
, worker
event
, worker
, prefork
For safety reasons this directive is only available if the server was
configured with the --enable-exception-hook
option. It
@@ -140,7 +141,7 @@ will exit.
GracefulShutdownTimeout 0
prefork
, worker
, event
event
, worker
, prefork
The GracefulShutdownTimeout
specifies
@@ -159,7 +160,7 @@ listens to
Listen [IP-address:]portnumber [protocol]
mpm_netware
, mpm_winnt
, mpmt_os2
, prefork
, worker
, event
event
, worker
, prefork
, mpm_winnt
, mpm_netware
, mpmt_os2
The Listen
directive instructs Apache httpd to
@@ -238,7 +239,7 @@ including other causes.
ListenBacklog 511
event
, mpm_netware
, mpm_winnt
, mpmt_os2
, prefork
, worker
event
, worker
, prefork
, mpm_winnt
, mpm_netware
, mpmt_os2
The maximum length of the queue of pending connections. Generally no tuning is needed or desired, however on some @@ -252,6 +253,41 @@ including other causes. but use a number based on (but normally larger than) what is set.
+ + +Description: | Ratio between the number of CPU cores (online) and the number of +listeners' buckets |
---|---|
Syntax: | ListenCoresBucketsRatio ratio |
Default: | ListenCoresBucketsRatio 0 (disabled) |
Context: | server config |
Status: | MPM |
Module: | event , worker , prefork |
Compatibility: | Available in Apache HTTP Server 2.4.17, with a kernel supporting
+the socket option SO_REUSEPORT and distributing new connections
+evenly accross listening processes' (or threads') sockets using it (eg. Linux
+3.9 and later, but not the current implementations of SO_REUSEPORT
+in *BSDs. |
A ratio between the number of (online) CPU cores and the
+ number of listeners' buckets can be used to make Apache HTTP Server create
+ num_cpu_cores / ratio
listening buckets, each containing its
+ own Listen
-ing socket(s) on the same port(s), and
+ then make each child handle a single bucket (with round-robin distribution
+ of the buckets at children creation time).
ListenCoresBucketsRatio
can improve the
+ scalability when accepting new connections is/becomes the bottleneck.
+ On systems with a large number of CPU cores, enabling this feature has
+ been tested to show significant performances improvement and shorter
+ responses time.
There must be at least twice the number of CPU cores than the
+ configured ratio for this to be active. The recommended
+ ratio is 8
, hence at least 16
+ cores should be available at runtime when this value is used.
MaxConnectionsPerChild 0
event
, mpm_netware
, mpm_winnt
, mpmt_os2
, prefork
, worker
event
, worker
, prefork
, mpm_winnt
, mpm_netware
, mpmt_os2
MaxRequestsPerChild
is still supported.free()
MaxMemFree 2048
event
, mpm_netware
, prefork
, worker
, mpm_winnt
event
, worker
, prefork
, mpm_winnt
, mpm_netware
The MaxMemFree
directive sets the
maximum number of free Kbytes that every allocator is allowed
@@ -305,7 +341,7 @@ simultaneously
See usage for details
event
, prefork
, worker
event
, worker
, prefork
The MaxRequestWorkers
directive sets the limit
on the number of simultaneous requests that will be served. Any
@@ -341,13 +377,13 @@ simultaneously
See usage for details
event
, mpm_netware
, mpmt_os2
, worker
event
, worker
, mpm_netware
, mpmt_os2
Maximum number of idle threads. Different MPMs deal with this directive differently.
-For worker
, the default is
- MaxSpareThreads 250
. This MPM deals with idle threads
+
For worker
and event
, the default is
+ MaxSpareThreads 250
. These MPMs deal with idle threads
on a server-wide basis. If there are too many idle threads in the
server then child processes are killed until the number of idle
threads is less than this number.
mpm_netware
wants the value to be greater than
MinSpareThreads
.worker
, the value must be greater or equal
- to the sum of MinSpareThreads
- and ThreadsPerChild
.worker
and event
, the value
+ must be greater or equal to the sum of
+ MinSpareThreads
and
+ ThreadsPerChild
.See usage for details
event
, mpm_netware
, mpmt_os2
, worker
event
, worker
, mpm_netware
, mpmt_os2
Minimum number of idle threads to handle request spikes. - Different MPMs deal with this directive - differently.
+ Different MPMs deal with this directive differently. -worker
uses a default of MinSpareThreads
- 75
and deals with idle threads on a server-wide basis. If
- there aren't enough idle threads in the server then child
+
worker
and event
use a default of
+ MinSpareThreads 75
and deal with idle threads on a server-wide
+ basis. If there aren't enough idle threads in the server then child
processes are created until the number of idle threads is greater
than number.
PidFile logs/httpd.pid
event
, mpm_winnt
, mpmt_os2
, prefork
, worker
event
, worker
, prefork
, mpm_winnt
, mpmt_os2
The PidFile
directive sets the file to
which the server records the process id of the daemon. If the
@@ -459,7 +495,7 @@ of the daemon
ReceiveBufferSize 0
event
, mpm_netware
, mpm_winnt
, mpmt_os2
, prefork
, worker
event
, worker
, prefork
, mpm_winnt
, mpm_netware
, mpmt_os2
The server will set the TCP receive buffer size to the number of bytes specified.
@@ -477,7 +513,7 @@ the child processesScoreBoardFile logs/apache_runtime_status
event
, mpm_winnt
, prefork
, worker
event
, worker
, prefork
, mpm_winnt
Apache HTTP Server uses a scoreboard to communicate between its parent and child processes. Some architectures require a file to facilitate @@ -512,7 +548,7 @@ Apache HTTP Server
SendBufferSize 0
event
, mpm_netware
, mpm_winnt
, mpmt_os2
, prefork
, worker
event
, worker
, prefork
, mpm_winnt
, mpm_netware
, mpmt_os2
Sets the server's TCP send buffer size to the number of bytes specified. It is often useful to set this past the OS's standard @@ -540,14 +576,14 @@ Apache HTTP Server
See usage for details
event
, prefork
, worker
event
, worker
, prefork
For the prefork
MPM, this directive sets the
maximum configured value for MaxRequestWorkers
for the lifetime of the
- Apache httpd process. For the worker
MPM, this directive
- in combination with ThreadLimit
sets
+ Apache httpd process. For the worker
and event
+
MPMs, this directive in combination with ThreadLimit
sets
the maximum configured value for MaxRequestWorkers
for the lifetime of the
- Apache httpd process. Any attempts to change this directive during a
+ Apache httpd process. Any attempts to change this directive during a
restart will be ignored, but MaxRequestWorkers
can be modified during
a restart.
MaxRequestWorkers
to.
- With worker
, use this directive only
- if your MaxRequestWorkers
and
- ThreadsPerChild
+
With worker
and event
, use this
+ directive only if your MaxRequestWorkers
+
and ThreadsPerChild
settings require more than 16 server processes (default). Do not set
the value of this directive any higher than the number of server
processes required by what you may want for MaxRequestWorkers
and ThreadsPerChild
.
See usage for details
event
, mpmt_os2
, prefork
, worker
event
, worker
, prefork
, mpmt_os2
The StartServers
directive sets the
number of child server processes created on startup. As the number
@@ -601,10 +637,10 @@ Apache HTTP Server
MinSpareServers
, MaxSpareServers
)
there is usually little reason to adjust this parameter.
The default value differs from MPM to MPM. worker
- defaults to StartServers 3
; prefork
- defaults to 5
; mpmt_os2
defaults to
- 2
.
The default value differs from MPM to MPM. worker
and
+ event
default to StartServers 3
;
+ prefork
defaults to 5
; mpmt_os2
+ defaults to 2
.
See usage for details
event
, mpm_winnt
, worker
event
, worker
, mpm_winnt
This directive sets the maximum configured value for ThreadsPerChild
for the lifetime
of the Apache httpd process. Any attempts to change this directive
@@ -681,7 +717,7 @@ per child process
See usage for details
event
, mpm_winnt
, worker
event
, worker
, mpm_winnt
This directive sets the number of threads created by each child process. The child creates these threads at startup and @@ -706,7 +742,7 @@ client connections
65536 on NetWare; varies on other operating systems
event
, mpm_netware
, mpmt_os2
, mpm_winnt
, worker
, event
event
, worker
, mpm_winnt
, mpm_netware
, mpmt_os2
The ThreadStackSize
directive sets the
diff --git a/docs/manual/mod/mpm_common.html.fr b/docs/manual/mod/mpm_common.html.fr
index 7c6d6d18..921b440a 100644
--- a/docs/manual/mod/mpm_common.html.fr
+++ b/docs/manual/mod/mpm_common.html.fr
@@ -32,6 +32,8 @@
ja |
tr
Description: | Une srie de directives implmentes par plusieurs modules multi-processus (MPM) |
---|---|
Statut: | MPM |
Description: | Rapport entre le nombre de coeurs de processeur activs et +le nombre de segments d'coute |
---|---|
Syntaxe: | ListenCoresBucketsRatio ratio |
Dfaut: | ListenCoresBucketsRatio 0 (disabled) |
Contexte: | configuration du serveur |
Statut: | MPM |
Module: | event , prefork , worker |
Compatibilit: | Disponible partir de la version 2.4.13 du serveur HTTP
+Apache, avec un noyau supportant l'option de socket
+SO_REUSEPORT , et distribuant uniformment les nouvelles
+connexions aux sockets d'coute des processus (ou threads) qui
+l'utilisent (par exemple Linux versions 3.9 et ultrieures, mais pas
+l'implmentation courante de SO_REUSEPORT par les
+plateformes de type BSD. |
Vous pouvez utiliser la directive
+ ListenCoresBucketsRatio
pour spcifier un
+ ratio entre le nombre de coeurs de CPU activs et le
+ nombre de segments d'coute (listeners' buckets) souhaits ; le
+ serveur HTTP Apache va alors crernum_cpu_cores / ratio
+ segments d'coute, chacun contenant son propre socket d'coute
+ Listen
sur le ou les mmes ports ; chaque
+ processus enfant sera associ un seul segment d'coute (avec une
+ distribution de type round-robin des segments la cration des
+ processus enfants).
La directive ListenCoresBucketsRatio
peut
+ amliorer le support de la monte en charge lorsque l'arrive de
+ nouvelles connexions est/devient un goulot d'tranglement. Le test
+ de cette fonctionnalit avec des machines possdant un nombre de
+ coeurs de CPU important a permit de constater une amlioration des
+ performances significative et des temps de rponse plus courts.
Pour que cette fonctionnalit soit active, le nombre de coeurs
+ de CPU doit tre gal au moins au double du ratio
+ spcifi. Si vous spcifiez la valeur recommande pour
+ ratio, savoir 8
, le nombre minimum de
+ coeurs de processeurs disponibles sera alors de 16
.
説明: | Ratio between the number of CPU cores (online) and the number of +listeners' buckets |
---|---|
構文: | ListenCoresBucketsRatio ratio |
デフォルト: | ListenCoresBucketsRatio 0 (disabled) |
コンテキスト: | サーバ設定ファイル |
ステータス: | MPM |
モジュール: | event , worker , prefork |
互換性: | Available in Apache HTTP Server 2.4.17, with a kernel supporting
+the socket option SO_REUSEPORT and distributing new connections
+evenly accross listening processes' (or threads') sockets using it (eg. Linux
+3.9 and later, but not the current implementations of SO_REUSEPORT
+in *BSDs. |
このディレクティブの解説文書は + まだ翻訳されていません。英語版をご覧ください。 +
説明: | Limit on the number of connections that an individual child server @@ -251,7 +270,7 @@ will handle during its life |
---|---|
デフォルト: | MaxConnectionsPerChild 0 |
コンテキスト: | サーバ設定ファイル |
ステータス: | MPM |
モジュール: | event , mpm_netware , mpm_winnt , mpmt_os2 , prefork , worker |
モジュール: | event , worker , prefork , mpm_winnt , mpm_netware , mpmt_os2 |
互換性: | Available Apache HTTP Server 2.3.9 and later. The old name
MaxRequestsPerChild is still supported. |
このディレクティブの解説文書は @@ -283,7 +302,7 @@ simultaneously
See usage for details
event
, prefork
, worker
event
, worker
, prefork
このディレクティブの解説文書は まだ翻訳されていません。英語版をご覧ください。
Açıklama: | Birden fazla Çok Süreçlilik Modülü (MPM) tarafından gerçeklenmiş yönergeler bütünü. |
---|---|
Durum: | MPM |
Açıklama: | İşlemci çekirdek sayısının dinleyenlerin buket sayısına oranı |
---|---|
Sözdizimi: | ListenCoresBucketsRatio oran |
Öntanımlı: | ListenCoresBucketsRatio 0 (iptal) |
Bağlam: | sunucu geneli |
Durum: | MPM |
Modül: | event , prefork , worker |
Uyumluluk: | Apache HTTP Server 2.4.17 ve sonrasında,
+ SO_REUSEPORT soket seçeneğini destekleyen bir Linux çekirdeğinin
+ varlığında ve yeni bağlantıların bunu kullanan dinleme süreçlerinin (veya
+ evrelerinin) soketleri arasında eşit paylaştırılıyor olması halinde
+ kullanılır. Örneğin Linux 3.9 ve sonrasında kullanılabilirken *BSD'lerin şu
+ anki SO_REUSEPORT gerçeklenimi ile kullanılamaz. |
(çevrimiçi) İşlemci çekirdek sayısının dinleyenlerin buket sayısına
+ oranı, Apache HTTP Sunucusunun işlemci_çekirdek_sayısı /
+ oran
sayıda dinleme buketi oluşturması için kullanılabilir ve bu
+ buketlerin herbiri aynı portlar üzerinde kendi
+ Listen
soketlerini içeriyor olurlar. Bu durumda,
+ her çocuk süreç tek bir buketle çalışır (çocukların oluşturulması
+ sırasında buketler döner dağılımla eşleştirilir).
ListenCoresBucketsRatio
yeni bağlantılar kabul
+ edilirken/darboğazlar oluşurken ölçeklenebilirliği arttırabilir. Çok
+ sayıda işlemci çekirdekli sistemlerde bu özelliğin etkinleştirilmesinin
+ önemli başarım artışları ve daha kısa yanıt süreleri oluşturduğu
+ gözlenmiştir.
Bu oranın etkin olabilmesi için işlemci çekirdeği çift sayıda
+ olmalıdır. oran için önerilen değer 8
olup bu
+ durumda çalışma anında en azından 16
çekirdek
+ kullanılabiliyor olmalıdır.
StartServers
processes
accepting connections.
- Each child process consists of a a pool of worker threads and a +
Each child process consists of a pool of worker threads and a main thread that accepts connections and passes them to the workers via a work queue. The worker thread pool is dynamic, managed by a maintenance thread so that the number of idle threads is kept between diff --git a/docs/manual/mod/quickreference.html.de b/docs/manual/mod/quickreference.html.de index b0a58bb7..bf4fed3d 100644 --- a/docs/manual/mod/quickreference.html.de +++ b/docs/manual/mod/quickreference.html.de @@ -472,118 +472,129 @@ angegebenen MIME-Content-Type will exit.
base
for imagemap filesbase
for imagemap filesPOST
data)HSE_APPEND_LOG_PARAMETER
requests from
+POST
data)HSE_APPEND_LOG_PARAMETER
requests from
ISAPI extensions to the error logHSE_APPEND_LOG_PARAMETER
requests from
+HSE_APPEND_LOG_PARAMETER
requests from
ISAPI extensions to the query fieldmod_mime
to treat path_info
+mod_mime
to treat path_info
components as part of the filenameAllow
and Deny
are
evaluated.ProxyHTMLURLMap
rules.<head>
sections.Via
HTTP response
+Via
HTTP response
header for proxied requestsServer
Last-Modified
headers are generated by the
+Last-Modified
headers are generated by the
server.base
for imagemap filesbase
for imagemap filesPOST
data)HSE_APPEND_LOG_PARAMETER
requests from
+POST
data)HSE_APPEND_LOG_PARAMETER
requests from
ISAPI extensions to the error logHSE_APPEND_LOG_PARAMETER
requests from
+HSE_APPEND_LOG_PARAMETER
requests from
ISAPI extensions to the query fieldmod_mime
to treat path_info
+mod_mime
to treat path_info
components as part of the filenameAllow
and Deny
are
evaluated.ProxyHTMLURLMap
rules.<head>
sections.Via
HTTP response
+Via
HTTP response
header for proxied requestsServer
HTTP response
+Server
HTTP response
headerLast-Modified
headers are generated by the
+Last-Modified
headers are generated by the
server.base
for imagemap filesbase
for imagemap filesPOST
data)HSE_APPEND_LOG_PARAMETER
requests from
+POST
data)HSE_APPEND_LOG_PARAMETER
requests from
ISAPI extensions to the error logHSE_APPEND_LOG_PARAMETER
requests from
+HSE_APPEND_LOG_PARAMETER
requests from
ISAPI extensions to the query fieldmod_mime
to treat path_info
+mod_mime
to treat path_info
components as part of the filenameAllow
and Deny
are
evaluated.ProxyHTMLURLMap
rules.<head>
sections.Via
HTTP response
+Via
HTTP response
header for proxied requestsServer
HTTP response
+Server
HTTP response
headerLast-Modified
headers are generated by the
+Last-Modified
headers are generated by the
server.Les troisime et quatrime colonnes numrent les contextes dans - lesquels la directive est applicable ainsi que son statut en accord avec le +
La troisime colonne numre les contextes dans + lesquels la directive est applicable, et la quatrime indique son statut en accord avec le tableau des lgendes ci-dessous.