From: Rich Bowen Date: Tue, 12 May 2026 11:58:17 +0000 (+0000) Subject: Tweaks the language around LogLevel - it's not "new" any more. X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=b0308b12378e90c73f7be0ec6a8be8b15cc75013;p=thirdparty%2Fapache%2Fhttpd.git Tweaks the language around LogLevel - it's not "new" any more. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1934137 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_rewrite.xml b/docs/manual/mod/mod_rewrite.xml index bac1d6e3e5..7ea73809be 100644 --- a/docs/manual/mod/mod_rewrite.xml +++ b/docs/manual/mod/mod_rewrite.xml @@ -46,7 +46,7 @@ URLs on the fly

mod_rewrite can operate on the full URL-path, or any portion of it, including the PATH_INFO or QUERY_STRING. It can also inspect - other values, such as headers, cookies, environment variables.

+ other values, such as headers, cookies, or environment variables.

A rewrite rule can be invoked in the server configuration files, or in throughput.

Further details, discussion, and examples, are provided in the - detailed mod_rewrite documentation.

+ detailed Guide to mod_rewrite.

Logging @@ -74,25 +74,29 @@ URLs on the fly level higher than trace2 only for debugging! - Example - + Example + LogLevel alert rewrite:trace3 - - + + RewriteLog

Those familiar with earlier versions of mod_rewrite will no doubt be looking for the RewriteLog and RewriteLogLevel - directives. This functionality has been completely replaced by the - new per-module logging configuration mentioned above. + directives. Since the release of httpd 2.4, these directives + have been replaced with the per-module logging configuration + provided by LogLevel.

To get just the mod_rewrite-specific log messages, pipe the log file through grep:

- - tail -f error_log|fgrep '[rewrite:' - + + + +tail -f error_log|fgrep '[rewrite:' + +