• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Block user-agent and stop logging

Azurel

Silver Pleskian
Server operating system version
AlmaLinux 8.10
Plesk version and microupdate number
Plesk Obsidian 18.0.74#2
I have a non-standard User-Agent (app/scrapper) that sends thousands of requests in few seconds, which severely bloats my access_ssl_log in different domains. Is here a way to prevent/block this in Plesk? The block must target the application agent, not the originating user IP. The user IP as website visitor is welcome.

I use this rule in a global Apache config file (/etc/httpd/conf.d/block_useragents.conf) to immediately stop the requests with a non-error status and set a variable:
<Directory "/var/www/vhosts/">
RewriteEngine On
RewriteOptions inherit

RewriteCond %{HTTP_USER_AGENT} ^botname [NC]
RewriteRule .* - [R=204,L,E=nolog:1]
</Directory>

How I can instruct Plesk to skip all logging in "access_ssl_log" when the custom variable nolog is present?
 
Back
Top