Can I serve 403 instead of 503?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter lukascech

    (@lukascech)

    same goes for wp-login.php – everything that’s blocked by the rule “immediately block non-existing usernames”

    Plugin Support wfpeter

    (@wfpeter)

    Hi @lukascech, thanks for your message!

    We do have a development case open for migrating HTTP 503 response codes to 429 for temporary blocking/rate limiting, and 403 for permanent blocks. This is on our radar and I’ve logged this topic, as each request for a feature strengthens its case for being included.

    Unfortunately I can’t comment here on the forums how long this may take or provide continuous updates on delivery of a feature. Please keep an eye on release notes for its inclusion in a future plugin version.

    Thanks,

    Peter.

    Thread Starter lukascech

    (@lukascech)

    ok, thanks for the info. the sooner, the better! Until then, I’ll look around for other firewalls and test what response they send in manual rules.

    I would also like to change the response code to 403. There’s a new bot that started crawling my home page this weekend. 50 requests for my home page in a 10 minute period. The 503 response isn’t stopping it.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Can I serve 403 instead of 503?’ is closed to new replies.