From 00818b79791fd7dbbbc49f6ddbb73b07a7e85597 Mon Sep 17 00:00:00 2001 From: Yann Ylavic Date: Mon, 13 Dec 2021 15:07:45 +0000 Subject: [PATCH] Improve docs for ProxyPass mapping= parameter. [skip ci] git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1895895 13f79535-47bb-0310-9956-ffa450edef68 --- docs/manual/mod/mod_proxy.xml | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/docs/manual/mod/mod_proxy.xml b/docs/manual/mod/mod_proxy.xml index 8b77ad8310a..2d720cc012b 100644 --- a/docs/manual/mod/mod_proxy.xml +++ b/docs/manual/mod/mod_proxy.xml @@ -1285,9 +1285,20 @@ ProxyPass "/example" "http://backend.example.com" max=20 ttl=120 retry=300 mapping - -

Mapping to process the url 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.

+

Type of mapping between the path and the url. + This determines the normalization and/or (non-)decoding that mod_proxy will + apply to the request's uri-path to match the path. If/when the mapping + matches, the request uri-path is committed such that <Location + and other directory contexts using a path will match according to the same mapping.

+

The encoded mapping avoids the %-decoding of the uri-path such that + one can match for instance /some%2furi%2fpath%2fwith%2fslash in a ProxyPass + or <Location context.

+

The servlet 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 uri-path like /some;foo/path is then mapped + as /some/path and thus matches <Location /some/path> or + ProxyPass "/some/path" "https://tomcat.example.com" regardless of the requested + path parameters.

-- 2.47.3