Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter Shora

    (@shora)

    Resolved. I have erased this command (ErrorDocument 403 /wp-content/plugins/bulletproof-security/403.php) in order to avoid internal redirects because mod_Security is interfering with it. I am in a shared hosting so I can’t do anything about the mod_Security.

    Thanks!

    Thread Starter Shora

    (@shora)

    Thank you very much for the information! I know banning one particular IP is usually a waste of time but, sometimes, certain IPs are very persistent (I remember one which tried to spam more than 40.000 times in a short period of time).

    Thread Starter Shora

    (@shora)

    I have been testing all the possibilities these days. Neither the theme nor the plugins are responsible for these internal redirects. I have changed the theme and deactivated the plugins and the internal redirects persisted.

    I have asked my web hosting if the server has mod_Security and they have confirmed me that the server has both mod_Security and Suhosin. Could One of these protection systems be causing the internal redirects?

    Thread Starter Shora

    (@shora)

    Nop, my website doesn’t use apostrophes or single qoutes. What I see in my Error log is something like that:

    [error] [client 207.241.229.207] Request exceeded the limit of 10 internal redirects due to probable configuration error.

    I have read the following discussion about that problem before:

    http://forum.ait-pro.com/forums/topic/request-exceeded-the-limit-of-10-internal-redirects/

    I have checked if by eliminating this command the error would persist or not: ErrorDocument 403 /wp-content/plugins/bulletproof-security/403.php When I erase this command the internal redirects disappear. So, it should be a problem about something else that is trying to handle 403 redirects, right?. But, you know what is the most strange thing of all this? This error mainly appears from IPS such as web.archive.org, Amazon or Opera Software Asa. Apart from that, all is fine. I have tried to access Loglevel Debug to get a backtrace but my Hosting doesn’t allow to activate it. So I am a little lost here.

    Ah, and the problem isn´t solved by using this:

    # .htaccess Fix for 403 Error Infinite Loops
    RewriteEngine On
    RewriteCond %{ENV:REDIRECT_STATUS} 403
    RewriteRule .* – [L]

    Thank you for your attention. I have been thinking about buying the BPS pro version and I have finally decided to do it 🙂

    Thread Starter Shora

    (@shora)

    Thanks for your response. I will try to find where is the problem in my htaccess, knowing that BPS is not responsible for that. However, I haven´t found anything yet which could block IP addresses from web.archive.org.

Viewing 5 replies - 1 through 5 (of 5 total)