Improve docs for ProxyPass mapping= parameter. [skip ci]
@@ -1285,9 +1285,20 @@ ProxyPass "/example" "http://backend.example.com" max=20 ttl=120 retry=300
</td></tr>
<tr><td>mapping</td>
<td>-</td>
- <td><p>Mapping to process the <var>url</var> before choosing a Worker/Balancer.
- 'servlet' maps like a servlet container (like jk_servlet_normalize), use with Apache Tomcat for example.
- 'encoded' maps it encoded.</p>
+ <td><p>Type of mapping between the <var>path</var> and the <var>url</var>.
+ This determines the normalization and/or (non-)decoding that <module>mod_proxy</module> will
+ apply to the request's <var>uri-path</var> to match the <var>path</var>. If/when the mapping
+ matches, the request <var>uri-path</var> is committed such that <code>&lt;Location</code>
+ and other directory contexts using a path will match according to the same mapping.</p>
+ <p>The <code>encoded</code> mapping avoids the %-decoding of the <var>uri-path</var> such that
+ one can match for instance <code>/some%2furi%2fpath%2fwith%2fslash</code> in a <code>ProxyPass</code>
+ or <code>&lt;Location</code> context.</p>
+ <p>The <code>servlet</code> mapping refers to the one 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> and thus matches <code>&lt;Location /some/path&gt;</code> or
+ <code>ProxyPass "/some/path" "https://tomcat.example.com"</code> regardless of the requested
+ path parameters.</p>
</td></tr>
</table>
