• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Input what does this fix: PPP-19965 (actually fix?)

larryk

Regular Pleskian
Rewrite rules from the .htaccess file do not work when PHP support is enabled with PHP-FPM handler. (PPP-19965)

what does that mean?

thanks
 
There were following steps to reproduce this bug:

1. Disable url cache in your browser. For Firefox: go to about:config and switch off 'network.http.use-cache' option.
2. Create domain with web hosting and enable php support with php-fpm module on apache.
3. add .htaccess on domain with the follow strings:

RewriteEngine On
RewriteBase /
RewriteRule ^(.*)\.php$ http://google.com [L,R=301]

4. Create some index.php on domain. E.g. with phpinfo();
5. try to open web page http://<youdomain>/index.php

Actual result - this rule doesn't work.

The problem was in fact that ProxyPassMatch directive redirects all REQUEST_URI before the .htaccess rules was used.

Now this behaviour is fixed.
 
Back
Top