[users@httpd] Re: enabling httpd v2.4's mod_proxy_fcgi + "ProxyPassMatch" breaks 'Index' display ?

2012-06-12 Thread k5876
With this, RewriteCond %{REQUEST_URI} !index\.php$ RewriteCond %{REQUEST_URI} \.php RewriteRule ^/test(/.*)$ fcgi://127.0.0.1:9000/srv/www/text/$1 [P] I see both the directory index @ http://myhost.com/, and all http://myhost.com/...php... exec correctly. Everything !php bypasses the proxy. It'

[users@httpd] Re: enabling httpd v2.4's mod_proxy_fcgi + "ProxyPassMatch" breaks 'Index' display ?

2012-06-12 Thread k5876
can't convince myself of anything with ProxyPassMatch, and can't figure out how to adequately log. switching to rewrite. my vhost config now contains, DirectoryIndex index.html #ProxyErrorOverride on RewriteEngine On LogLevel info rewrite:trace5 #ProxyPa

[users@httpd] Re: enabling httpd v2.4's mod_proxy_fcgi + "ProxyPassMatch" breaks 'Index' display ?

2012-06-12 Thread k5876
Per chat in #irc, trying to narrow down on regex/wildcard problems, I'm seeing confusing behavior -- note the cases (3) & (4), below, _switch_ what works & what doesn't. THere are more iterations to try, but it seems to be an issue with wildcard usage in the Match -- of some sort. (1) ProxyPassM

[users@httpd] enabling httpd v2.4's mod_proxy_fcgi + "ProxyPassMatch" breaks 'Index' display ?

2012-06-12 Thread k5876
I run apache 2.4.3-dev with mod_proxy_fcgi + php-fpm. My apache vhost config includes DirectoryIndex index.php index.html #ProxyPassMatch ^/(.*\.php(/.*)?)$ fcgi://127.0.0.1:9000/srv/www/testhost/$1 Require all granted

[users@httpd] Using 'SetEnvIf' IP address matches in IPv6 space - do I match on 'short' or 'expanded' address?

2012-06-07 Thread k5876
In my httpd conf, I set a var for use in matching conditions. In IPv4 space this is clear. SetEnvIf X-FORWARDED-FOR "^192\.168\.1\.(.*)" okOFFICE=$1 SetEnvIf X-FORWARDED-FOR "^127\.0\.0\.1(.*)" okLOCALHOST=$1 I want to add the analogue for IPv6 addresses. Which do I match aga