Hello,
On Sat, Apr 14, 2018 at 09:37:53PM +0100, Ian wrote:
* Before (Jessie):
[…]
<Files "wp-login.php">
AuthName "Message that Firefox shows but Chromium no longer does!"
AuthType Basic
AuthUserFile /home/exampleuser/.htpasswd
Require valid-user
</Files>
[…]
* After (Stretch):
Because of the changes between the two, Apache now calls php-fpm via the
proxy-fcgi module in /etc/apache2/sites-available/example.com.conf -
ProxyPassMatch ^/(.*\.php(/.*)?)$
unix:/run/php/php7.0-fpm_exampleuser.sock|fcgi://localhost/home/exampleuser/public_html/
and with the same .htaccess file, it *doesn't* trigger on access to
wp-login.php because it's a .php file, ProxyPass gets there first and just
runs it without checking anywhere else if it should.
What happens if you put the wp-login stuff in a
<Location></Location> instead? And do it without .htaccess at first
until you get it working…
The basic point here I think is that if you are proxying everything
then it's no longer a file so <Files> is never going to match.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting