| Author |
|
kevsy
Joined: 13 Jul 2010
Posts: 7
Location: UK/France
|
 Posted: Thu 09 Aug '12 11:52 Post subject: Request exceeded the limit of 10 internal redirects |
 |
|
I am following a tutorial and I've hit a bad patch.
The tutorial has a page that includes setting up a 'Vanity URL' with an .htaccess file.
On activating, it returns a '500 Internal Server Error'.
The Apache_error_log shows:
[Thu Aug 09 09:53:25 2012] [error] [client 127.0.0.1]
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.,
referer: http://localhost/lr/index_1.php
Could you please unlock the mystery.
I am using WAMP and the server is Apache/2.2.11 (Win32) PHP/5.3.0 configured.
One more small request. My Apache_error_log takes ages to load, is there anyway of deleting the contents or speeding up the loading??
Admin note:
Changed subject more meaningful. |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
| Posted: Thu 09 Aug '12 19:35 Post subject: |
|
|
Looks like you have an incorrect rewrite rule.
To clear your log file(s): stop apache and delete.
Steffen |
|
| Back to top |
|
kevsy
Joined: 13 Jul 2010
Posts: 7
Location: UK/France
|
| Posted: Fri 10 Aug '12 10:16 Post subject: |
|
|
Steffen I am at the bottom of the food chain when it comes to knowing what I need to know about Apache. I would be grateful if you could expand on how I locate and check/correct the rewrite rule, also when you say 'stop Apache' do you mean put offline and where are the log files, or can the log files be located via Windows Explorer..??
Thank you...kev |
|
| Back to top |
|
Steffen
Moderator
Joined: 15 Oct 2005
Posts: 3092
Location: Hilversum, NL, EU
|
| Posted: Fri 10 Aug '12 11:20 Post subject: |
|
|
Bare minimum you have to know, is where Apache is installed. Default the log are located in .../apache/logs.
The rewrite rule is in the .htaccess, best is to go back to the author of your .htaccess rules.
Steffen |
|
| Back to top |
|
kevsy
Joined: 13 Jul 2010
Posts: 7
Location: UK/France
|
| Posted: Fri 10 Aug '12 11:27 Post subject: |
|
|
I managed a bit on my own, I located and deleted the error_logs just before reading you reply, congratulated myself and moved up one step in the food chain. Now for htaccess.
Be back later... kev |
|
| Back to top |
|
kevsy
Joined: 13 Jul 2010
Posts: 7
Location: UK/France
|
| Posted: Fri 10 Aug '12 12:39 Post subject: |
|
|
| kevsy wrote: | I managed a bit on my own, I located and deleted the error_logs just before reading you reply, congratulated myself and moved up one step in the food chain. Now for htaccess.
Be back later... kev |
Back again Steffen.
I found the 'rewrite module' and it's on.
I can't find a way of dealing with:
[Fri Aug 10 11:12:39 2012] [error] [client 127.0.0.1] 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., referer: http://localhost/lr/index_1.php
I have 1 function:
function logged_in_redirect() {
if (logged_in() === true) {
header('Location: index_1.php');
exit();
}
}
This function is only active when in use in any one of 3 files.
kev |
|
| Back to top |
|
James Blond
Moderator
Joined: 19 Jan 2006
Posts: 7371
Location: Germany, Next to Hamburg
|
| Posted: Fri 10 Aug '12 13:56 Post subject: |
|
|
| kevsy wrote: | [error] [client 127.0.0.1] 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., referer: http://localhost/lr/index_1.php
header('Location: index_1.php');
exit();
|
That header is the problem! It redirects to itself with stopping. You built a nice loop.  |
|
| Back to top |
|
kevsy
Joined: 13 Jul 2010
Posts: 7
Location: UK/France
|
| Posted: Sat 11 Aug '12 0:22 Post subject: SOLVED Video_31,32,33. Profile Page |
|
|
Bit further up the food chain today..long process.
The error_log was a bit misleading and in the end the actual error lay with an .htaccess file and '/'
Never mind, thanks all. |
|
| Back to top |
|
