From: Daniel Gruno The most essential part of any request is the request record
. In a call to a handler function, this is represented by the Some key elements of the
-This version in its entirity can be found here:
+This version in its entirety can be found here:
mod_example_2.c.
-Now that we've told the server to expect some directives for our module, it's
+Now that we have told the server to expect some directives for our module, it's
time to make a few functions for handling these. What the server reads in the
configuration file(s) is text, and so naturally, what it passes along to
our directive handler is one or more strings, that we ourselves need to
@@ -1217,8 +1217,19 @@ AP_INIT_TAKE1("exampleEnabled", example_set_enabled, NULL, RSRC_CONF, "Enable or
this directive in a global server context, but since we are now trying out
a context aware version of our module, we should set this to something
more lenient, namely the value
request_rec*
structure passed along with every call that is made.
-This struct, typically just refered to as r
in modules,
+This struct, typically just referred to as r
in modules,
contains all the information you need for your module to fully process any
HTTP request and respond accordingly.
request_rec
structure are:
@@ -728,7 +728,7 @@ static int example_handler(request_rec *r)
The directive handler function
ACCESS_CONF
, which lets us use
-the directive inside <Directory> and <Location> blocks.
+the directive inside <Directory> and <Location> blocks. For more
+control over the placement of your directives, you can combine the following
+restrictions together to form a specific rule:
+
RSRC_CONF
: Allow in .conf files (not .htaccess) outside <Directory> or <Location>ACCESS_CONF
: Allow in .conf files (not .htaccess) inside <Directory> or <Location>OR_OPTIONS
: Allow in .conf files and .htaccess when AllowOverride Options
is setOR_FILEINFO
: Allow in .conf files and .htaccess when AllowOverride FileInfo
is setOR_AUTHCFG
: Allow in .conf files and .htaccess when AllowOverride AuthConfig
is setOR_INDEXES
: Allow in .conf files and .htaccess when AllowOverride Indexes
is setOR_ALL
: Allow anywhere in .conf files and .htaccessUsing the server to allocate configuration slots
@@ -1658,7 +1669,7 @@ static int example_handler(request_rec *r)
keyValuePair* formData;
/*~~~~~~~~~~~~~~~~~~~~~~*/
- formData = readPost();
+ formData = readPost(r);
if (formData) {
int i;
for (i = 0; formData[i]; i++) {
diff --git a/docs/manual/mod/mod_authnz_ldap.html.en b/docs/manual/mod/mod_authnz_ldap.html.en
index 4fa230c9f7..71990521d9 100644
--- a/docs/manual/mod/mod_authnz_ldap.html.en
+++ b/docs/manual/mod/mod_authnz_ldap.html.en
@@ -865,6 +865,21 @@ authorization
properly protected. You should only use the AuthLDAPBindDN
and AuthLDAPBindPassword
if you
absolutely need them to search the directory.
If the value begins with exec: the resulting command will be + executed and the first line returned to standard output by the + program will be used as the password.
++#Password used as-is +AuthLDAPBindPassword secret + +#Run /path/to/program to get my password +AuthLDAPBindPassword exec:/path/to/program + +#Run /path/to/otherProgram and provide arguments +AuthLDAPBindPassword "exec:/path/to/otherProgram argument1" +
Si la valeur spécifiée débute par "exec:", la commande qui suit sera + exécutée, et la première ligne renvoyée par la commande sur la + sortie standard sera utilisée comme mot de passe.
++# Mot de passe spécifié directement +AuthLDAPBindPassword secret + +# Exécution de /path/to/program pour obtenir le mot de passe +AuthLDAPBindPassword exec:/path/to/program + +# Exécution de /path/to/otherProgram avec un argument pour obtenir le mot de passe +AuthLDAPBindPassword "exec:/path/to/otherProgram argument1" +
512
.
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
- bytes. If you change it from the default, you must also change the
- packetSize
attribute of your AJP connector on the
- Tomcat side! The attribute packetSize
is only available
- in Tomcat 5.5.20+
and 6.0.2+
packetSize
attribute of
+ your AJP connector on the Tomcat side! The attribute
+ packetSize
is only available in Tomcat 5.5.20+
+ and 6.0.2+
+
Normally it is not necessary to change the maximum packet size. Problems with the default value have been reported when sending certificates or certificate chains.
@@ -1270,6 +1273,13 @@ ProxyPass /mirror/foo http://backend.example.com 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. +balancer-manager
application page.
diff --git a/docs/manual/mod/mod_proxy.html.fr b/docs/manual/mod/mod_proxy.html.fr
index e8bc4a8d02..70d472ea3b 100644
--- a/docs/manual/mod/mod_proxy.html.fr
+++ b/docs/manual/mod/mod_proxy.html.fr
@@ -942,8 +942,11 @@ donn
Dans la plupart des cas, il n'y a aucune raison de modifier cette valeur.
+Si elle est utilisée avec AJP, cette directive permet de définir
- la taille maximale du paquet AJP en octets. Si vous ne conservez pas
+ la taille maximale du paquet AJP en octets. Si la valeur spécifiée
+ est supérieure à 65536, elle est corrigée et prend la valeur 65536.
+ Si vous ne conservez pas
la valeur par défaut, vous devez aussi modifier l'attribut
packetSize
de votre connecteur AJP du côté de Tomcat !
L'attribut packetSize
n'est disponible que dans Tomcat
@@ -1429,7 +1432,15 @@ ProxyPass /mirror/foo http://backend.example.com
dans la liste. La récupération du worker s'effectue comme dans
le cas des autres erreurs de worker.