• 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.

Question How to overrde "Security of the wp-content folder" with .htaccess

Laurence@

Regular Pleskian
What are the .htaccess directives to override this function. Say a user wants to secure /wp-content but allow 2 scripts to execute. Anyone know?
 
What are the .htaccess directives to override this function. Say a user wants to secure /wp-content but allow 2 scripts to execute. Anyone know?
I don't use .htaccess. However, you can turn off the wp-content security in the WordPress settings and re-enable it manually in your "Additional nginx directives" settings for each domain. Do something like this, enabling the PHP access for specific files then disabling it for all others:

Code:
# Allow PHP for specific files while stopping all other PHP in wp-content (this is only for https content)
location ~* "^/wp-content/.*myspecialfile.php" {
   proxy_pass   https://myserveripaddress:7081;
   proxy_set_header Host   $host;
   proxy_set_header X-Real-IP   $remote_addr;
   proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
}
location ~* "^/wp-content/.*\\.php" { deny all; }
 
Back
Top