HTTP 503 vs. 403 response for blocked ranges

  • Resolved mishash

    (@mishash)


    7 years ago

    Hello,
    I permanently block some of AWS ranges using Wordfence firewall and, while analyzing access logs on my server, I was surprised to see that one of the blocked IPs received HTTP response 503 (service unavailable). There were over 100 attempts from this IP at different times and the response was always HTTP 503. All other blocked AWS IPs receive response 403 (forbidden). If this an intended functionality or a software bug? If it’s intended, then whet’s the logic behind 403 vs 503 choice?
    Thanks.

Viewing 1 replies (of 1 total)
  • wfalaa

    (@wfalaa)

    Hello,
    Was that IP getting locked out from the log-in page? Can you share a screenshot with that part of Live Traffic showing this IP getting locked out/blocked?

    Thanks.

Viewing 1 replies (of 1 total)
  • The topic ‘HTTP 503 vs. 403 response for blocked ranges’ is closed to new replies.