Hi,
On 7/11/24 9:46 AM, Frank Gingras wrote:
On Thu, Jul 11, 2024 at 4:49 AM Marc <m...@f1-outsourcing.eu> wrote:
>
> RewriteCond %{HTTP_USER_AGENT} ^$
> [OR]
> RewriteCond %{HTTP_USER_AGENT} ^.*(<|>|'|%0A|%0D|%27|%3C|%3E|%00).*
> [NC,OR]
> RewriteCond %{HTTP_USER_AGENT}
> ^.*(HTTrack|clshttp|archiver|loader|email|nikto|miner|python).*
[NC,OR]
> RewriteCond %{HTTP_USER_AGENT} ^.*(winhttp|libwww\-
> perl|curl|wget|harvest|scan|grab|extract).* [NC,OR]
> RewriteCond %{HTTP_USER_AGENT}
> ^.*(Googlebot|SemrushBot|PetalBot|Bytespider|bingbot).* [NC]
> RewriteRule (.*) https://guardiandigital.com/$1 [L,R=301]
>
>
> SetEnvIf user-agent "(?i:GoogleBot)" googlebot=1
> SetEnvIf user-agent "(?i:SemrushBot)" googlebot=1
> SetEnvIf user-agent "(?i:PetalBot)" googlebot=1
> SetEnvIf user-agent "(?i:Bytespider)" googlebot=1
> SetEnvIf user-agent "(?i:bingbot)" googlebot=1
>
>
> <RequireAny>
> Require ip 1.2.3.4
> Require env googlebot
> </RequireAny>
>
I would think that mod_security is more efficient for this
SecRule REQUEST_HEADERS:User-Agent "xxxx"
"id:'13006',phase:2,log,deny,status:200"
This is very interesting and something I'll investigate.
The follow bit:
"has to appear in .htaccess because it's processed after the
virtualhost config and any requireall/requireany entries are
overridden that already appear there"
Makes no sense. You can just create your vhost properly to produce
the expected behaviour.
Can you explain more about what you mean here? Suggestions for how to
improve my vhost config?
