<p><module>mod_rewrite</module> 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.</p>
+ other values, such as headers, cookies, or environment variables.</p>
<p>A rewrite rule
can be invoked in the server configuration files, or in <glossary
throughput.</p>
<p>Further details, discussion, and examples, are provided in the
- <a href="../rewrite/">detailed mod_rewrite documentation</a>.</p>
+ detailed <a href="../rewrite/">Guide to mod_rewrite</a>.</p>
</summary>
<section id="logging"><title>Logging</title>
level higher than <code>trace2</code> only for debugging!
</note>
- <example><title>Example</title>
- <highlight language="config">
+ <example><title>Example</title>
+ <highlight language="config">
LogLevel alert rewrite:trace3
- </highlight>
- </example>
+ </highlight>
+ </example>
<note><title>RewriteLog</title>
<p>Those familiar with earlier versions of
<module>mod_rewrite</module> will no doubt be looking for the
<code>RewriteLog</code> and <code>RewriteLogLevel</code>
- 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 <directive module="core">LogLevel</directive>.
</p>
<p>To get just the <module>mod_rewrite</module>-specific log
messages, pipe the log file through grep:</p>
- <example>
- tail -f error_log|fgrep '[rewrite:'
- </example>
+
+ <example>
+ <highlight language="sh">
+tail -f error_log|fgrep '[rewrite:'
+ </highlight>
+ </example>
</note>
</section>