From: Stefan Fritsch In addition to string-valued functions, there are also list-valued functions which
diff --git a/docs/manual/mod/index.html.de b/docs/manual/mod/index.html.de
index a0242e044f4..d9fbfec21ac 100644
--- a/docs/manual/mod/index.html.de
+++ b/docs/manual/mod/index.html.de
@@ -165,7 +165,7 @@ request processing
-CONTENT_TYPE
+REMOTE_ADDR
-HANDLER
+HTTPS
-REMOTE_ADDR
+IPV6
+
+ HTTPS
@@ -250,9 +252,9 @@ listfunction ::= listfuncname "(" word ")"
IPV6
@@ -269,11 +271,16 @@ listfunction ::= listfuncname "(" word ")"
Name Description
+
- -n
String is not empty (XXX: not yet implemented) String is not empty
+
- -z
String is empty (XXX: not yet implemented) String is empty
Get HTTP request header
-resp
Get HTTP response header
+osenv
+
+ reqenv
Lookup request environment variable
+osenv
Lookup operating system environment variable
+ note
Lookup request environment variable
-
- env
Lookup request environment variable (XXX: will need to be changed for better ssl_expr compat)
+
+ lolower
Reqturn first match of note
, reqenv
,
+ osenv
tolower
Convert string to lower case
@@ -281,6 +288,8 @@ listfunction ::= listfuncname "(" word ")"
toupper
Convert string to uppser case Escape special characters in %hex encoding
+unescape
Unescape %hex encoded string, leaving URL-special characters encoded (XXX: describe better)
+ file
Read contents from a file mod_proxy
mod_proxy
extension for load balancing mod_proxy
mod_proxy
extension for load balancing ls
, ou à la commande
shell Win32 dir
mod_proxy
mod_proxy
extension for load balancing mod_proxy
mod_proxy
extension for load balancing
"dispatch = match"
"dispatch = 'match'"
The Request headers, Response headers and Environment variables - are now interpreted from syntax $req{foo}, - $resp{foo} and $env{foo} respectively. - The variables $handler and $Content-Type + are now interpreted from syntax %{req:foo}, + %{resp:foo} and %{env:foo} respectively. + The variables %{HANDLER} and %{CONTENT_TYPE} are also supported.
-Note that the match no longer supports integer comparisons - or substring matches. The latter can be replaced by regular - expression matches.
+Note that the match no longer support substring matches. They can be + replaced by regular expression matches.
AddOutputFilterByType
FilterDeclare SSI
- FilterProvider SSI INCLUDES "$resp{Content-Type} = /^text\/html/"
+ FilterProvider SSI INCLUDES "%{CONTENT_TYPE} =~ m|^text/html|"
FilterChain SSI
- FilterProvider SSI INCLUDES "Handler = server-parsed"
+ FilterProvider SSI INCLUDES "%{HANDLER} = 'server-parsed'"
FilterChain SSI
FilterDeclare gzip CONTENT_SET
- FilterProvider gzip inflate "$req{Accept-Encoding} != /gzip/"
+ FilterProvider gzip inflate "%{req:Accept-Encoding} !~ /gzip/"
FilterChain gzip
- FilterProvider unpack jpeg_unpack "$resp{Content-Type} = image/jpeg"
- FilterProvider unpack gif_unpack "$resp{Content-Type} = image/gif"
- FilterProvider unpack png_unpack "$resp{Content-Type} = image/png"
+ FilterProvider unpack jpeg_unpack "%{CONTENT_TYPE} = 'image/jpeg'"
+ FilterProvider unpack gif_unpack "%{CONTENT_TYPE} = 'image/gif'"
+ FilterProvider unpack png_unpack "%{CONTENT_TYPE} = 'image/png'"
- FilterProvider downsample downsample_filter "$resp{Content-Type} = /image\/(jpeg|gif|png)/"
+ FilterProvider downsample downsample_filter "%{CONTENT_TYPE} = m|^image/(jpeg|gif|png)|"
FilterProtocol downsample "change=yes"
- FilterProvider repack jpeg_pack "$resp{Content-Type} = image/jpeg"
- FilterProvider repack gif_pack "$resp{Content-Type} = image/gif"
- FilterProvider repack png_pack "$resp{Content-Type} = image/png"
+ FilterProvider repack jpeg_pack "%{CONTENT_TYPE} = 'image/jpeg'"
+ FilterProvider repack gif_pack "%{CONTENT_TYPE} = 'image/gif'"
+ FilterProvider repack png_pack "%{CONTENT_TYPE} = 'image/png'"
<Location /image-filter>
FilterChain unpack downsample repack
@@ -460,50 +460,8 @@
ap_register_output_filter
.
expression can be any of the following:
-string
string1 = string2
- string1 == string2
- string1 != string2
Compare string1 with string2. If
- string2 has the form /string2/
- then it is treated as a regular expression. Regular expressions are
- implemented by the PCRE engine and
- have the same syntax as those in perl
- 5. Note that ==
is just an alias for =
- and behaves exactly the same way.
string1 < string2
- string1 <= string2
- string1 > string2
- string1 >= string2
strcmp(3)
). Therefore the string "100" is less than
- "20".( expression )
! expression
expression1 &&
- expression2
expression1 ||
- expression2
expression is described in the + ap_expr documentation.
La fonctionnalité suEXEC permet l'exécution des programmes CGI et @@ -400,7 +398,7 @@ de suEXEC
--with-suexec-userdir=DIR
mod_filter
: FilterProvider
syntax has changed and
+ now uses a boolean expression to determine if a filter is applied.
+ Afin d'assister les utilisateurs lors de leurs opérations de mise à jour, nous maintenons un document diff --git a/docs/manual/upgrading.xml.fr b/docs/manual/upgrading.xml.fr index b7492a9c608..463da64e644 100644 --- a/docs/manual/upgrading.xml.fr +++ b/docs/manual/upgrading.xml.fr @@ -3,7 +3,7 @@ - +