Firewall before htaccess?

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author nintechnet

    (@nintechnet)

    7 years, 11 months ago

    Hi,

    Normally, your .htaccess should catch it first.
    Note that you are using the ‘deny’ directive which is deprecated since Apache 2.4, so maybe make sure that you are running Apache < 2.4, otherwise replace it as per Apache documentation.

    Another possibility would be that your host does not support (or disabled) .htaccess files.

    Okoth1

    (@okoth1)

    7 years, 11 months ago

    I just checked deny with my own ip address and I blocked myself.

    Really no clue why 178.137. can get through till your plugin blocked it on something else.

    Plugin Author nintechnet

    (@nintechnet)

    7 years, 11 months ago

    Maybe this IP is not REMOTE_ADDR but another IP header such as HTTP_X_FORWARDED_FOR or HTTP_CLIENT_IP etc?

    Thread Starter Wendihihihi

    (@wendihihihi)

    7 years, 11 months ago

    Yes, that could be true. I’m going to find out.

    I also blocked myself when I deny my IP, but Okoth1 and I are on the same server 😉

    Going to close this topic for now. If I find out I’ll let you know.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Firewall before htaccess?’ is closed to new replies.