From: Daniel Earl Poirier Date: Wed, 16 Mar 2011 16:58:30 +0000 (+0000) Subject: Update transforms X-Git-Tag: 2.3.12~218 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=b32076c9a520308b5647f05912701f73ae96fcc8;p=thirdparty%2Fapache%2Fhttpd.git Update transforms git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1082207 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/developer/new_api_2_4.html.en b/docs/manual/developer/new_api_2_4.html.en index 087f7164dfa..f272c5fa639 100644 --- a/docs/manual/developer/new_api_2_4.html.en +++ b/docs/manual/developer/new_api_2_4.html.en @@ -288,7 +288,7 @@ code will remain compatible with HTTPD 2.0 and 2.2.

Consider the following changes to take advantage of the new - APLOG_TRACE1..8 log levels: + APLOG_TRACE1..8 log levels:

+

Modules sometimes add process id and/or thread id to their log messages. These ids are now logged by default, so it may not @@ -413,6 +413,7 @@

Does your module...

+
Parse query args
Consider if ap_args_to_table() would be helpful.
@@ -427,6 +428,7 @@
Implement cleanups which clear pointer variables
Use ap_pool_cleanup_set_null().
+
diff --git a/docs/manual/mod/core.html.en b/docs/manual/mod/core.html.en index 0c7ad073c92..7cda3975a66 100644 --- a/docs/manual/mod/core.html.en +++ b/docs/manual/mod/core.html.en @@ -354,26 +354,35 @@ content-type is text/plain or text/html - + - +
Description:Determines whether encoded path separators in URLs are allowed to be passed through
Syntax:AllowEncodedSlashes On|Off
Syntax:AllowEncodedSlashes On|Off|NoDecode
Default:AllowEncodedSlashes Off
Context:server config, virtual host
Status:Core
Module:core
Compatibility:Available in Apache httpd 2.0.46 and later
Compatibility:Available in Apache httpd 2.0.46 and later. +NoDecode option available in 2.3.12 and later.

The AllowEncodedSlashes directive allows URLs which contain encoded path separators (%2F for / and additionally %5C for \ on according systems) - to be used. Normally such URLs are refused with a 404 (Not found) error.

+ to be used in the path info.

+ +

With the default value, Off, such URLs are refused + with a 404 (Not found) error.

+ +

With the value On, such URLs are accepted, and encoded + slashes are decoded like all other encoded characters.

+ +

With the value NoDecode, such URLs are accepted, but + encoded slashes are not decoded but left in their encoded state.

Turning AllowEncodedSlashes On is mostly useful when used in conjunction with PATH_INFO.

Note

-

Allowing encoded slashes does not imply decoding. - Occurrences of %2F or %5C (only on - according systems) will be left as such in the otherwise decoded URL - string.

+

If encoded slashes are needed in path info, use of NoDecode is + strongly recommended as a security measure. Allowing slashes + to be decoded could potentially allow unsafe paths.

See also

diff --git a/docs/manual/mod/core.xml.de b/docs/manual/mod/core.xml.de index 914fd657670..afa7f2973fd 100644 --- a/docs/manual/mod/core.xml.de +++ b/docs/manual/mod/core.xml.de @@ -1,7 +1,7 @@ - + + +