URLs on the fly</td></tr>
<tr><th><a href="module-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="module-dict.html#ModuleIdentifier">Module Identifier:</a></th><td>rewrite_module</td></tr>
-<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_rewrite.c</td></tr>
-<tr><th><a href="module-dict.html#Compatibility">Compatibility:</a></th><td>Available in Apache 1.3 and later</td></tr></table>
+<tr><th><a href="module-dict.html#SourceFile">Source File:</a></th><td>mod_rewrite.c</td></tr></table>
<h3>Summary</h3>
<p>The <code class="module"><a href="../mod/mod_rewrite.html">mod_rewrite</a></code> module uses a rule-based rewriting
<p>These variables all
correspond to the similarly named HTTP
- MIME-headers, C variables of the Apache server or
+ MIME-headers, C variables of the Apache HTTP Server or
<code>struct tm</code> fields of the Unix system.
Most are documented elsewhere in the Manual or in
the CGI specification. Those that are special to
<dt><code>API_VERSION</code></dt>
- <dd>This is the version of the Apache module API
+ <dd>This is the version of the Apache httpd module API
(the internal interface between server and
module) in the current httpd build, as defined in
include/ap_mmn.h. The module API version
- corresponds to the version of Apache in use (in
- the release version of Apache 1.3.14, for
+ corresponds to the version of Apache httpd in use (in
+ the release version of Apache httpd 1.3.14, for
instance, it is 19990320:10), but is mainly of
interest to module authors.</dd>
<p>The variables SCRIPT_FILENAME and REQUEST_FILENAME
contain the same value - the value of the
<code>filename</code> field of the internal
- <code>request_rec</code> structure of the Apache server.
+ <code>request_rec</code> structure of the Apache HTTP Server.
The first name is the commonly known CGI variable name
while the second is the appropriate counterpart of
REQUEST_URI (which contains the value of the
<code>%{ENV:variable}</code>, where <em>variable</em> can be
any environment variable, is also available.
This is looked-up via internal
- Apache structures and (if not found there) via
- <code>getenv()</code> from the Apache server process.</li>
+ Apache httpd structures and (if not found there) via
+ <code>getenv()</code> from the Apache httpd server process.</li>
<li>
<code>%{SSL:variable}</code>, where <em>variable</em> is the
<div class="note"><h3>Security</h3>
-See the <a href="../misc/security_tips.html">Apache Security Tips</a>
+See the <a href="../misc/security_tips.html">Apache HTTP Server Security Tips</a>
document for details on how your security could be compromised if the
directory where logfiles are stored is writable by anyone other than
the user that starts the server.
logs.</p>
<div class="note"> Using a high value for
- <em>Level</em> will slow down your Apache server
+ <em>Level</em> will slow down your Apache HTTP Server
dramatically! Use the rewriting logfile at a
<em>Level</em> greater than 2 only for debugging!
</div>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_rewrite</td></tr>
<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>The choice of different dbm types is available in
-Apache 2.0.41 and later</td></tr>
+Apache HTTP Server 2.0.41 and later</td></tr>
</table>
<p>The <code class="directive">RewriteMap</code> directive defines a
<em>Rewriting Map</em> which can be used inside rule
<li>
<strong>Internal Function</strong><br />
- MapType: <code>int</code>, MapSource: Internal Apache
+ MapType: <code>int</code>, MapSource: Internal Apache httpd
function
- <p>Here, the source is an internal Apache function.
+ <p>Here, the source is an internal Apache httpd function.
Currently you cannot create your own, but the following
functions already exist:</p>
'<code>#!/path/to/interpreter</code>' as the first
line).</p>
- <p>This program is started once, when the Apache server
+ <p>This program is started once, when the Apache httpd server
is started, and then communicates with the rewriting engine
via its <code>stdin</code> and <code>stdout</code>
file-handles. For each map-function lookup it will
<ol>
<li>``<em>Keep it simple, stupid</em>'' (KISS).
- If this program hangs, it will cause Apache to hang
+ If this program hangs, it will cause Apache httpd to hang
when trying to use the relevant rewrite rule.</li>
<li>A common mistake is to use buffered I/O on
<p>When the RewriteRule appears in per-directory (htaccess) context, the
<em>Pattern</em> is matched against what remains of the URL after removing
- the prefix that lead Apache to the current rules (see the
+ the prefix that lead Apache httpd to the current rules (see the
<code class="directive"><a href="#rewritebase">RewriteBase</a></code>). The removed prefix
always ends with a slash, meaning the matching occurs against a string which
never has a leading slash. A <em>Pattern</em> with <code>^/</code> never
<status>Extension</status>
<sourcefile>mod_rewrite.c</sourcefile>
<identifier>rewrite_module</identifier>
-<compatibility>Available in Apache 1.3 and later</compatibility>
<summary>
<p>The <module>mod_rewrite</module> module uses a rule-based rewriting
<note type="securitywarning"><title>Security</title>
-See the <a href="../misc/security_tips.html">Apache Security Tips</a>
+See the <a href="../misc/security_tips.html">Apache HTTP Server Security Tips</a>
document for details on how your security could be compromised if the
directory where logfiles are stored is writable by anyone other than
the user that starts the server.
logs.</p>
<note> Using a high value for
- <em>Level</em> will slow down your Apache server
+ <em>Level</em> will slow down your Apache HTTP Server
dramatically! Use the rewriting logfile at a
<em>Level</em> greater than 2 only for debugging!
</note>
<contextlist><context>server config</context><context>virtual host</context>
</contextlist>
<compatibility>The choice of different dbm types is available in
-Apache 2.0.41 and later</compatibility>
+Apache HTTP Server 2.0.41 and later</compatibility>
<usage>
<p>The <directive>RewriteMap</directive> directive defines a
<li>
<strong>Internal Function</strong><br />
- MapType: <code>int</code>, MapSource: Internal Apache
+ MapType: <code>int</code>, MapSource: Internal Apache httpd
function
- <p>Here, the source is an internal Apache function.
+ <p>Here, the source is an internal Apache httpd function.
Currently you cannot create your own, but the following
functions already exist:</p>
'<code>#!/path/to/interpreter</code>' as the first
line).</p>
- <p>This program is started once, when the Apache server
+ <p>This program is started once, when the Apache httpd server
is started, and then communicates with the rewriting engine
via its <code>stdin</code> and <code>stdout</code>
file-handles. For each map-function lookup it will
<ol>
<li>``<em>Keep it simple, stupid</em>'' (KISS).
- If this program hangs, it will cause Apache to hang
+ If this program hangs, it will cause Apache httpd to hang
when trying to use the relevant rewrite rule.</li>
<li>A common mistake is to use buffered I/O on
<p>These variables all
correspond to the similarly named HTTP
- MIME-headers, C variables of the Apache server or
+ MIME-headers, C variables of the Apache HTTP Server or
<code>struct tm</code> fields of the Unix system.
Most are documented elsewhere in the Manual or in
the CGI specification. Those that are special to
<dt><code>API_VERSION</code></dt>
- <dd>This is the version of the Apache module API
+ <dd>This is the version of the Apache httpd module API
(the internal interface between server and
module) in the current httpd build, as defined in
include/ap_mmn.h. The module API version
- corresponds to the version of Apache in use (in
- the release version of Apache 1.3.14, for
+ corresponds to the version of Apache httpd in use (in
+ the release version of Apache httpd 1.3.14, for
instance, it is 19990320:10), but is mainly of
interest to module authors.</dd>
<p>The variables SCRIPT_FILENAME and REQUEST_FILENAME
contain the same value - the value of the
<code>filename</code> field of the internal
- <code>request_rec</code> structure of the Apache server.
+ <code>request_rec</code> structure of the Apache HTTP Server.
The first name is the commonly known CGI variable name
while the second is the appropriate counterpart of
REQUEST_URI (which contains the value of the
<code>%{ENV:variable}</code>, where <em>variable</em> can be
any environment variable, is also available.
This is looked-up via internal
- Apache structures and (if not found there) via
- <code>getenv()</code> from the Apache server process.</li>
+ Apache httpd structures and (if not found there) via
+ <code>getenv()</code> from the Apache httpd server process.</li>
<li>
<code>%{SSL:variable}</code>, where <em>variable</em> is the
<p>When the RewriteRule appears in per-directory (htaccess) context, the
<em>Pattern</em> is matched against what remains of the URL after removing
- the prefix that lead Apache to the current rules (see the
+ the prefix that lead Apache httpd to the current rules (see the
<directive module="mod_rewrite">RewriteBase</directive>). The removed prefix
always ends with a slash, meaning the matching occurs against a string which
never has a leading slash. A <em>Pattern</em> with <code>^/</code> never
</ul>
<h3>See also</h3>
<ul class="seealso">
-<li><a href="../env.html">Environment Variables in Apache</a></li>
+<li><a href="../env.html">Environment Variables in Apache HTTP Server</a></li>
</ul></div>
<div class="top"><a href="#page-header"><img alt="top" src="../images/up.gif" /></a></div>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_setenvif</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Apache 1.2 and
- above (in Apache 1.2 this directive was found in the
- now-obsolete mod_browser module)</td></tr>
</table>
<p>The <code class="directive">BrowserMatchNoCase</code> directive is
<p>In the first form, the value will be set to "1". The second
will remove the given variable if already defined, and the
third will set the variable to the literal value given by
- <code><em>value</em></code>. Since version 2.0.51 Apache will
+ <code><em>value</em></code>. Since version 2.0.51, Apache httpd will
recognize occurrences of <code>$1</code>..<code>$9</code> within
<var>value</var> and replace them by parenthesized subexpressions
of <var>regex</var>.</p>
<h3>See also</h3>
<ul>
-<li><a href="../env.html">Environment Variables in Apache</a>,
+<li><a href="../env.html">Environment Variables in Apache HTTP Server</a>,
for additional examples.
</li>
</ul>
<tr><th><a href="directive-dict.html#Override">Override:</a></th><td>FileInfo</td></tr>
<tr><th><a href="directive-dict.html#Status">Status:</a></th><td>Base</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_setenvif</td></tr>
-<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Apache 1.3 and above</td></tr>
</table>
<p>The <code class="directive">SetEnvIfNoCase</code> is semantically identical to
</example>
</summary>
-<seealso><a href="../env.html">Environment Variables in Apache</a></seealso>
+<seealso><a href="../env.html">Environment Variables in Apache HTTP Server</a></seealso>
<directivesynopsis>
<name>BrowserMatch</name>
<context>virtual host</context><context>directory</context>
<context>.htaccess</context></contextlist>
<override>FileInfo</override>
-<compatibility>Apache 1.2 and
- above (in Apache 1.2 this directive was found in the
- now-obsolete mod_browser module)</compatibility>
<usage>
<p>In the first form, the value will be set to "1". The second
will remove the given variable if already defined, and the
third will set the variable to the literal value given by
- <code><em>value</em></code>. Since version 2.0.51 Apache will
+ <code><em>value</em></code>. Since version 2.0.51, Apache httpd will
recognize occurrences of <code>$1</code>..<code>$9</code> within
<var>value</var> and replace them by parenthesized subexpressions
of <var>regex</var>.</p>
set [a-z].</p>
</usage>
-<seealso><a href="../env.html">Environment Variables in Apache</a>,
+<seealso><a href="../env.html">Environment Variables in Apache HTTP Server</a>,
for additional examples.
</seealso>
</directivesynopsis>
<context>virtual host</context><context>directory</context>
<context>.htaccess</context></contextlist>
<override>FileInfo</override>
-<compatibility>Apache 1.3 and above</compatibility>
<usage>
<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ja.xsl"?>
-<!-- English Revision: 420990 -->
+<!-- English Revision: 420990:926413 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<?xml version="1.0" encoding="EUC-KR" ?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.ko.xsl"?>
-<!-- English Revision: 420990 -->
+<!-- English Revision: 420990:926413 (outdated) -->
<!--
Licensed to the Apache Software Foundation (ASF) under one or more
<variants>
<variant>en</variant>
<variant>fr</variant>
- <variant>ja</variant>
- <variant>ko</variant>
- <variant>tr</variant>
+ <variant outdated="yes">ja</variant>
+ <variant outdated="yes">ko</variant>
+ <variant outdated="yes">tr</variant>
</variants>
</metafile>
<?xml version="1.0"?>
<!DOCTYPE modulesynopsis SYSTEM "../style/modulesynopsis.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.tr.xsl"?>
-<!-- English Revision: 420990 -->
+<!-- English Revision: 420990:926413 (outdated) -->
<!-- =====================================================
Translated by: Nilgün Belma Bugüner <nilgun belgeler.org>
Reviewed by: Orhan Berent <berent belgeler.org>
projects / apache / commitdiff