1
0
mirror of https://github.com/apache/httpd.git synced 2026-01-06 09:01:14 +03:00
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1743790 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Christophe Jaillet
2016-05-14 07:17:33 +00:00
parent 7a4888abc1
commit 211e449adf

View File

@@ -72,11 +72,11 @@
Using the <code>n</code> flag forces the pattern to be treated
as a fixed string.</dd>
<dt><code>f</code></dt>
<dd>The <code>f</code> flag causes mod_substitute to flatten the
<dd>The <code>f</code> flag causes <code>mod_substitute</code> to flatten the
result of a substitution allowing for later substitutions to
take place on the boundary of this one. This is the default.</dd>
<dt><code>q</code></dt>
<dd>The <code>q</code> flag causes mod_substitute to not
<dd>The <code>q</code> flag causes <code>mod_substitute</code> to not
flatten the buckets after each substitution. This can
result in much faster response and a decrease in memory
utilization, but should only be used if there is no possibility
@@ -86,7 +86,7 @@
<div class="example"><h3>Example</h3><pre class="prettyprint lang-config">&lt;Location "/"&gt;
AddOutputFilterByType SUBSTITUTE text/html
Substitute s/foo/bar/ni
Substitute "s/foo/bar/ni"
&lt;/Location&gt;</pre>
</div>
@@ -114,7 +114,7 @@
to the back-end server. These URLs don't work for the end-user,
since the back-end server is unreachable.</p>
<p>In this case, <code>mod_substutite</code> can be used to rewrite
<p>In this case, <code>mod_substitute</code> can be used to rewrite
those URLs into something that will work from the front end:</p>
<div class="example"><h3>Rewriting URLs embedded in proxied content</h3><pre class="prettyprint lang-config">ProxyPass "/blog/" "http://internal.blog.example.com"
@@ -126,7 +126,7 @@ Substitute "s|http://internal.blog.example.com/|http://www.example.com/blog/|i"<
<p><code class="directive"><a href="../mod/mod_proxy.html#proxypassreverse">ProxyPassReverse</a></code>
modifies any <code>Location</code> (redirect) headers that are sent
by the back-end server, and, in this example,
<code>Substitute</code> takes care of the rest of the problem by
<code class="directive">Substitute</code> takes care of the rest of the problem by
fixing up the HTML response as well.</p>
@@ -141,7 +141,7 @@ Substitute "s|http://internal.blog.example.com/|http://www.example.com/blog/|i"<
<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>Extension</td></tr>
<tr><th><a href="directive-dict.html#Module">Module:</a></th><td>mod_substitute</td></tr>
<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in httpd 2.5 and later</td></tr>
<tr><th><a href="directive-dict.html#Compatibility">Compatibility:</a></th><td>Available in httpd 2.4.17 and later</td></tr>
</table>
<p>Whether to apply the inherited <code class="directive">Substitute</code>
patterns first (<code>on</code>), or after the ones of the current
@@ -179,7 +179,7 @@ Substitute "s|http://internal.blog.example.com/|http://www.example.com/blog/|i"<
<div class="example"><h3>Example</h3><pre class="prettyprint lang-config">&lt;Location "/"&gt;
AddOutputFilterByType SUBSTITUTE text/html
SubstituteMaxLineLength 10m
Substitute s/foo/bar/ni
Substitute "s/foo/bar/ni"
&lt;/Location&gt;</pre>
</div>