[Resolved] Litespeed Status Code 444

[MOtorHead]

Can you tell me an alternative to this nginx bit for me to use with Litespeed?

if ($http_user_agent ~ WordPress) { return 444; }

 

[NiteWave]

https://httpstatuses.com/444

444 CONNECTION CLOSED WITHOUT RESPONSE
A non-standard status code used to instruct nginx to close the connection without sending a response to the client, most commonly used to deny malicious or malformed requests.
This status code is not seen by the client, it only appears in nginx log files.

so it's not a standard status code and from nginx only.
fortunately, there is a similar one in litespeed:

RewriteCond %{HTTP_USER_AGENT} wordpress [NC]
RewriteRule .* - [E=blockbot:1]

to perform a test, we change the rewrite rule a bit to:
RewriteRule a.html - [E=blockbot:1]

#curl -Iv 127.0.0.1/a.html
* About to connect() to 127.0.0.1 port 80 (#0)
*   Trying 127.0.0.1...
* Connected to 127.0.0.1 (127.0.0.1) port 80 (#0)
> HEAD /a.html HTTP/1.1
> User-Agent: curl/7.29.0
> Host: 127.0.0.1
> Accept: */*
>
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

 

[MOtorHead]

Thankyou @NiteWave
XMLRPC pingback attacks no more.
( Note: Included wat nitewave mentioned in the root .htaccess and had to restart litespeed to make it work )