Yann, On 12/17/15 3:51 AM, Yann Ylavic wrote: > On Thu, Dec 17, 2015 at 8:14 AM, Marat Khalili <mkh@xxxxxx> wrote: >> Crude, but what about: >> >> ProxyPassMatch "^/foo/(.+)$" "http://localhost:8009/foo/$1"; > > or (along the lines): > ProxyPassMatch ^/foo/((?!index\.html$).+)$ http://localhost:8009/foo/$1 I was able to solve the problem in this way, which is basically the same thing you have above: ProxyPassMatch ^/foo/index.html$ ! ProxyPassMatch ^/foo(/)?$ ! RedirectMatch ^/foo/index.html$ /foo/someplace_specific.html RedirectMatch ^/foo/$ /foo/someplace_specific.html It's pretty clear that I should probably combine each of these pairs of directives into single ones, since they will likely perform better. I'm not sure if PCRE is smart enough to understand that ^whatever$ can be optimized to straight-equals to avoid the overhead of the whole regular expression engine. If anyone knows the answer to that, it would be nice to know. In the meantime, regular expressions have come to the rescue. -chris --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|