You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@httpd.apache.org by rb...@apache.org on 2012/03/15 12:23:16 UTC
svn commit: r1300919 - in /httpd/httpd/trunk/docs/manual/rewrite:
flags.html.en flags.xml.fr proxy.html.en remapping.html.en
Author: rbowen
Date: Thu Mar 15 11:23:16 2012
New Revision: 1300919
URL: http://svn.apache.org/viewvc?rev=1300919&view=rev
Log:
rebuild
Modified:
httpd/httpd/trunk/docs/manual/rewrite/flags.html.en
httpd/httpd/trunk/docs/manual/rewrite/flags.xml.fr
httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en
httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en
Modified: httpd/httpd/trunk/docs/manual/rewrite/flags.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/flags.html.en?rev=1300919&r1=1300918&r2=1300919&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/flags.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/flags.html.en Thu Mar 15 11:23:16 2012
@@ -283,7 +283,7 @@ redirects.</p>
<h2><a name="flag_f" id="flag_f">F|forbidden</a></h2>
<p>Using the [F] flag causes the server to return a 403 Forbidden status
code to the client. While the same behavior can be accomplished using
-the <code class="directive"><a href="../mod/mod_access.html#deny">Deny</a></code> directive, this
+the <code class="directive"><a href="../mod/mod_access_compat.html#deny">Deny</a></code> directive, this
allows more flexibility in assigning a Forbidden status.</p>
<p>The following rule will forbid <code>.exe</code> files from being
@@ -519,7 +519,7 @@ The target (or substitution string) in a
file path, by default. The use of the [PT] flag causes it to be treated
as a URI instead. That is to say, the
use of the [PT] flag causes the result of the <code class="directive"><a href="../mod/mod_rewrite.html#rewriterule">RewriteRule</a></code> to be passed back through
-URL mapping, so that location-based mappings, such as <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>, <code class="directive"><a href="../mod/core.html#redirect">Redirect</a></code>, or <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>, for example, might have a
+URL mapping, so that location-based mappings, such as <code class="directive"><a href="../mod/mod_alias.html#alias">Alias</a></code>, <code class="directive"><a href="../mod/mod_alias.html#redirect">Redirect</a></code>, or <code class="directive"><a href="../mod/mod_alias.html#scriptalias">ScriptAlias</a></code>, for example, might have a
chance to take effect.
</p>
Modified: httpd/httpd/trunk/docs/manual/rewrite/flags.xml.fr
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/flags.xml.fr?rev=1300919&r1=1300918&r2=1300919&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/flags.xml.fr (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/flags.xml.fr Thu Mar 15 11:23:16 2012
@@ -1,7 +1,7 @@
<?xml version="1.0" encoding="ISO-8859-1" ?>
<!DOCTYPE manualpage SYSTEM "../style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="../style/manual.fr.xsl"?>
-<!-- English Revision: 1179266:1300556 (outdated) -->
+<!-- English Revision: 1179266:1300917 (outdated) -->
<!-- French translation : Lucien GENTIS -->
<!-- Reviewed by : Vincent Deffontaines -->
Modified: httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en?rev=1300919&r1=1300918&r2=1300919&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/proxy.html.en Thu Mar 15 11:23:16 2012
@@ -79,7 +79,7 @@ ProxyPassReverse / http://old.example.co
that any redirects issued by the backend are correctly passed on to
the client.</p>
- <p>Consider using either <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> or <code class="directive"><a href="../mod/mod_rewrite.html#proxypassmatch">ProxyPassMatch</a></code> whenever possible in
+ <p>Consider using either <code class="directive"><a href="../mod/mod_proxy.html#proxypass">ProxyPass</a></code> or <code class="directive"><a href="../mod/mod_proxy.html#proxypassmatch">ProxyPassMatch</a></code> whenever possible in
preference to mod_rewrite.</p>
</dd>
</dl>
Modified: httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en
URL: http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en?rev=1300919&r1=1300918&r2=1300919&view=diff
==============================================================================
--- httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en (original)
+++ httpd/httpd/trunk/docs/manual/rewrite/remapping.html.en Thu Mar 15 11:23:16 2012
@@ -247,7 +247,7 @@ RewriteRule ^(.*).html$ $1.php<br />
<p>This ruleset is designed to use in a per-directory context (In a
<Directory> block or in a .htaccess file), so that the
<code>-f</code> checks are looking at the correct directory path.
- You may need to set a <code class="directive"><a href="../mod/mod_rewite.html#rewritebase">RewriteBase</a></code> directive to specify the
+ You may need to set a <code class="directive"><a href="../mod/mod_rewrite.html#rewritebase">RewriteBase</a></code> directive to specify the
directory base that you're working in.</p>
</dd>
</dl>
@@ -273,7 +273,7 @@ RewriteRule ^(.*).html$ $1.php<br />
<dd>
<p>The very best way to solve this doesn't involve mod_rewrite at all,
-but rather uses the <code class="directive"><a href="../mod/alias.html#redirect">Redirect</a></code>
+but rather uses the <code class="directive"><a href="../mod/mod_alias.html#redirect">Redirect</a></code>
directive placed in a virtual host for the non-canonical
hostname(s).</p>