While using mod_proxy_fcgi like: RewriteRule ^/(.*\.(php|php3|php4|php5|phps|phtml|inc)(/.*)?)$ fcgi://172.16.0.11:1007/DOCROOT/$1 [P] directives in .htaccess like -deny from xxx <Files file.php> deny fromxxx </Files> etc. would not work - file will be processed by backend and returned to browser without further .htaccess check. We should be able to run "auth phase 'check access (with Satisfy All)'" with mod_proxy_fcgi like with mod_fcgid.
What Directories would be searched for htaccess in this case if the URL isn't mapped to the filesystem?
I belive /DOCROOT/ ? Is it at all possible to proceed with other (htaccess) rules after backend returned result?
Maybe it's possible to run VH Rewrite to proxy after all the .htaccess rewrites are done?
Have you tried putting RewriteRule to <Directory> context?
Proxied content doesn't match filesystem containers <files> or <Directory>, this is working as designed. Workaround in comment #4 might help, as it causes files to be mapped to the filesystem first then proxied in a later phase on a new internal redirect.
Unfortunatelly workaround from comment #4 is not working. There is no internal redirect back to proxy (wrapped in <Directory>) from .htaccess.
This is invalid as a bug, the configuration does not map anythin to disk. For configuration advice or support, try users@httpd.apache.org or serverfault. We can only entertain bugs against httpd here.