diff options
| author | Yann Ylavic <ylavic@apache.org> | 2021-12-16 16:07:43 +0100 |
|---|---|---|
| committer | Yann Ylavic <ylavic@apache.org> | 2021-12-16 16:07:43 +0100 |
| commit | e9fa9ce6d013e396231e991ee2b5a67183e782ce (patch) | |
| tree | bbc1a8e8bf1d5507cf54020ea5e5da926f9e8307 /docs/manual/mod/mod_proxy.html.en.utf8 | |
| parent | Improve ProxyPass mapping= docs. [skip ci] (diff) | |
| download | apache2-e9fa9ce6d013e396231e991ee2b5a67183e782ce.tar.xz apache2-e9fa9ce6d013e396231e991ee2b5a67183e782ce.zip | |
Sync docs [skip ci].
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1896063 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'docs/manual/mod/mod_proxy.html.en.utf8')
| -rw-r--r-- | docs/manual/mod/mod_proxy.html.en.utf8 | 37 |
1 files changed, 23 insertions, 14 deletions
diff --git a/docs/manual/mod/mod_proxy.html.en.utf8 b/docs/manual/mod/mod_proxy.html.en.utf8 index ee3cea5b1a..3dee332270 100644 --- a/docs/manual/mod/mod_proxy.html.en.utf8 +++ b/docs/manual/mod/mod_proxy.html.en.utf8 @@ -1444,23 +1444,32 @@ ProxyPass "/mirror/foo" "http://backend.example.com"</pre> contexts that use a path (like <code><Location></code>) will be matched using the same mapping.</p> <p><code>mapping=encoded</code> prevents the %-decoding of the <var>uri-path</var> so - that one can match for instance <code>/some%2furi%2fpath%2fwith%2fslash</code> in a - <code>ProxyPass</code> or in a <code><Location></code> context.</p> + that one can use for instance configurations like:</p> + <pre class="prettyprint lang-config">ProxyPass "/special%3Fsegment" "https://example.com/special%3Fsegment" mapping=encoded</pre> + + <pre class="prettyprint lang-config"><Location "/special%3Fsegment"> + Require ip 172.17.2.0/24 +</Location></pre> + <p><code>mapping=servlet</code> refers to the normalization defined by the Servlet specification, which is for instance applied by Apache Tomcat for servlet containers (notably the path parameters are ignored for the mapping). An <var>uri-path</var> like - <code>/some;foo/path</code> is then mapped as <code>/some/path</code> hence matches:</p> - <p><code> <Location /some/path></code> or:</p> - <p><code> ProxyPass "/some/path" "https://tomcat.example.com/some/path"</code></p> - <p>regardless of the requested path parameters.</p> - <div class="note"><h3>Note</h3> - <p>It is recommended to use the same mapping on the Apache httpd side than the one - used on the backend side. For instance when configuring authorizations in - <code><Location></code> blocks for paths that are mapped by <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> - to some servlet containers (like applications running on Apache Tomcat), one should - use the <code>mapping=servlet</code> setting to prevent path parameters and alike from - interfering with the authorizations that are to be enforced in by the Apache httpd.</p> - </div> + <code>/some;foo/path</code> is then mapped as <code>/some/path</code> hence matches any + of the below regardless of the requested path parameters:</p> + <pre class="prettyprint lang-config">ProxyPass "/some/path" "https://servlet.example.com/some/path" mapping=servlet</pre> + + <pre class="prettyprint lang-config"><Location "/some/path"> + Require valid-user +</Location></pre> + + <div class="note"><h3>Note</h3> + <p>It is recommended to use the same mapping on the Apache httpd side than the one + used on the backend side. For instance when configuring authorizations in + <code><Location></code> blocks for paths that are mapped by <code class="module"><a href="../mod/mod_proxy.html">mod_proxy</a></code> + to some servlet containers (like applications running on Apache Tomcat), one should + use the <code>mapping=servlet</code> setting to prevent path parameters and alike from + interfering with the authorizations that are to be enforced in by the Apache httpd.</p> + </div> </td></tr> </table> |