On Thu, Mar 3, 2022 at 12:24 PM Yann Ylavic <ylavic....@gmail.com> wrote: > > Hi Hendrik; > > > > > after reading your commit comment in https://svn.apache.org/r1898509 I > > realised that one important test case is missing: > > What happens if mod_rewrite manipulates the URL of a target that is proxied > > with the option mapping=servlet? > > > > From my point of view this test case fails. :-( > > ProxyPass /beta http://server2.localnet:8080/beta mapping=servlet > > RewirteRule "^/alpha/gobeta" /beta [PT,L] > > Calling https://example.org/alpha/gobeta/test sends back a 404 instead > > the beta content. > > In this case mod_proxy could not map the requests to the beta backend. > > Given that "ProxyPass ... mapping=servlet" applies before the > RewriteRule, I don't see how you can have a RewriteRule [PT] that > either "cancels" the ProxyPass (like in your RewriteMap examples) > and/or that rewrites the uri but keeps proxying (like in the above > example). > > Isn't: > RewriteRule "^/alpha/gobeta/(.*)$" http://server2.localnet:8080/beta/$1 [P] > (or alike) what you are looking for in the above example?
Also, it seems to me that "/alpha/gobeta/.." is not matched by the "ProxyPass /beta ...", so it really boils down to the RewriteRule only. What do you expect here? > > Regards; > Yann. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
