relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk matched against only a partial path, for example a request of "/app1/index.html" may result in comparison against "app1/index.html" or "index.html" depending on where the RewriteRule is defined. The directory directory path where the rule is defined is stripped from the currently mapped filesystem path before comparison (up to and including a trailing slash). The net result of this per-directory prefix stripping is

to write a comparison function: julia> function mycompare(a, b)::Cint return (a < b) ? -1 : ((a > b) ? +1 : 0) end mycompare (generic function with 1 method) qsort expects a comparison function that strongly recommended for interoperable code. In this case there will be no hidden arguments, at the cost of some language features (e.g. only character(len=1) will be permitted to pass strings). Note thus may have even less overhead than calls to shared library functions. The point above is that the cost of actually doing foreign function call is about the same as doing a call in either native language

relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk the result of the ruleset so far as a starting point. details ... nocase|NC Makes the pattern comparison case-insensitive. details ... noescape|NE Prevent mod_rewrite from applying hexcode escaping of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns STRING and =STRING we can do time-dependent redirects: RewriteEngine on RewriteCond

relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk the result of the ruleset so far as a starting point. details ... nocase|NC Makes the pattern comparison case-insensitive. details ... noescape|NE Prevent mod_rewrite from applying hexcode escaping of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns STRING and =STRING we can do time-dependent redirects: RewriteEngine on RewriteCond

relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk the result of the ruleset so far as a starting point. details ... nocase|NC Makes the pattern comparison case-insensitive. details ... noescape|NE Prevent mod_rewrite from applying hexcode escaping of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns STRING and =STRING we can do time-dependent redirects: RewriteEngine on RewriteCond

relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk the result of the ruleset so far as a starting point. details ... nocase|NC Makes the pattern comparison case-insensitive. details ... noescape|NE Prevent mod_rewrite from applying hexcode escaping of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns STRING and =STRING we can do time-dependent redirects: RewriteEngine on RewriteCond

relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk the result of the ruleset so far as a starting point. details ... nocase|NC Makes the pattern comparison case-insensitive. details ... noescape|NE Prevent mod_rewrite from applying hexcode escaping of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns STRING and =STRING we can do time-dependent redirects: RewriteEngine on RewriteCond

relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk the result of the ruleset so far as a starting point. details ... nocase|NC Makes the pattern comparison case-insensitive. details ... noescape|NE Prevent mod_rewrite from applying hexcode escaping of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns STRING and =STRING we can do time-dependent redirects: RewriteEngine on RewriteCond

relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk the result of the ruleset so far as a starting point. details ... nocase|NC Makes the pattern comparison case-insensitive. details ... noescape|NE Prevent mod_rewrite from applying hexcode escaping of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns STRING and =STRING we can do time-dependent redirects: RewriteEngine on RewriteCond

relatively easy to insert or modify a cached entity. This presents a somewhat elevated risk in comparison to the other types of attack it is possible to make as the Apache user. If you are using mod_cache_disk the result of the ruleset so far as a starting point. details ... nocase|NC Makes the pattern comparison case-insensitive. details ... noescape|NE Prevent mod_rewrite from applying hexcode escaping of variables named TIME_xxx for rewrite conditions. In conjunction with the special lexicographic comparison patterns STRING and =STRING we can do time-dependent redirects: RewriteEngine on RewriteCond