Re: [users@httpd] ProxyPass ordering

Thanks for the answers. Testing proved that putting the proxypass directives inside location blocks caused a problem with ordering On Mon, Oct 23, 2017 at 6:57 AM Daniel wrote: > Indeed. > > ProxyPass goes most specific first. > Example of sorting: > ProxyPass /something

Re: [users@httpd] ProxyPass ordering

Indeed. ProxyPass goes most specific first. Example of sorting: ProxyPass /something ... ProxyPass / While Location should go more global first. Example or sorting: Location / Location /something As a general rule of thumb, when directive itself specifies url-path don't use location, in this

Re: [users@httpd] ProxyPass ordering

My recollection is that the ordering is NOT handled similarly when in Location. Each directive will replace the last. On Wed, Oct 4, 2017 at 8:04 AM, Victor Engle wrote: > I have a site where multiple locations are mapped to different Proxy > balancers named balancer1,

[users@httpd] ProxyPass ordering

I have a site where multiple locations are mapped to different Proxy balancers named balancer1, balancer2, balancer3 etc. One of the locations mapped is root, "/", and according to the documentation, if that ProxyPass mapping comes last in the config, it should work as expected. Instead, with