Welcome to WebmasterWorld Guest from 35.171.183.163

Forum Moderators: coopster & jatar k

Message Too Old, No Replies

Database error in php website

     
6:31 pm on Jul 24, 2018 (gmt 0)

New User

joined:July 24, 2018
posts: 1
votes: 0


Have you ever come across this error?
[error] [client x. y. z. m] Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace
6:50 pm on July 24, 2018 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member lucy24 is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:Apr 9, 2011
posts:15704
votes: 811


Have you ever come across this error?
Yes, it's not actually a php error but a server error. If you have access to your site's raw error logs--which it sounds as if you’re quoting--you should see the cascade of successive requests. Once you know what's getting requested you can figure out what to fix in the php.
10:17 am on July 26, 2018 (gmt 0)

Senior Member

WebmasterWorld Senior Member Top Contributors Of The Month

joined:Nov 13, 2016
posts:1009
votes: 241


Too may rewrites (or redirects). Your sever conf is rewriting or redirecting an URI to another URI, which itself is redirecting to another URI, and so on, ... may be it 's a loop
5:15 pm on July 26, 2018 (gmt 0)

Senior Member from US 

WebmasterWorld Senior Member lucy24 is a WebmasterWorld Top Contributor of All Time 5+ Year Member Top Contributors Of The Month

joined:Apr 9, 2011
posts:15704
votes: 811


The quoted message said “internal redirects”, which is Apache-speak for what we generally call a rewrite. If they were external redirects, nothing would show up in the error log--but the access log would show a series of requests, each receiving a 300-class response, ending abruptly when the user's browser (or the robot's script) figures out that this is going nowhere fast.