Re: Internal Redirects Limit

2008-07-01 Thread Gorm Lai



On Mon, 2008-06-30 at 19:26 +1000, Malcolm Tredinnick wrote:
> 
> 
> On Mon, 2008-06-30 at 10:03 +0200, Gorm Lai wrote:
> > Hey,
> > 
> > I now have our django project set up both locally and on our own remote
> > server. Everything works fine.
> > 
> > However, I still have trouble getting it up and running on the client's
> > site. It is a big broad casting company, so they won't let me mess with
> > their apache setup directly. They will change it, when I request it, but
> > the turnaround cycle is rather long, so I want to be sure I request the
> > right changes.
> > 
> > I know get this error in the apache logs, 
> > 
> > [Fri Jun 27 16:17:53 2008] [error] [client 130.226.238.69] 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.
> > 
> > Please note that I do not have the power to set a LogLevel debug. Can
> > django indirectly cause an apache error like this?
> 
> >From memory, what this usually means is that something like Apache
> Rewrite rules have gotten mixed up and are doing internal calls to
> themselves. Note that this is an *internal* redirect, so it doesn't have
> anything to do with HTTP redirects. It also cannot be caused solely by
> Django. Rather, it's a problem in the Apache configuration and the
> result your are returning (or perhaps the resource that is being
> requested) is triggering the problem.
> 
> Without you (or your sysadmins) being able to turn on the debug-level
> logging for this, it's going to be fairly hard to resolve the problem.
> But it's certainly an Apache configuration problem, rather than
> something on the Django side (well, at least, the Apache configuration
> is contributing to it).
> 
> Regards,
> Malcolm
> 

Ok, so I now got the LogLevel debug output.

It says

[Tue Jul 01 07:39:08 2008] [debug] core.c(3027): [client 130.226.238.69]
r->uri = /php/drmu/sommerspil/login/
[Tue Jul 01 07:39:08 2008] [debug] core.c(3033): [client 130.226.238.69]
redirected from r->uri = /php/drmu/sommerspil/login/
[Tue Jul 01 07:39:08 2008] [debug] core.c(3033): [client 130.226.238.69]
redirected from r->uri = /php/drmu/sommerspil/login/

and so forth..

when I hit my url directly at http://77.66.32.232/php/drmu/sommerspil/ ,
I get the expected behaviour of no listing allowed, and I can also
directly access files in that directory that I know exists. So the
redirection is correct.

However, as soon as I try to hitting one of my methods, e.g. 
http://77.66.32.232/php/drmu/sommerspil/login/ then I got the
LimitInternalRecursion error. Please note, that I already tried setting
the limit higher, just in the unlikely case that I wasn't dealing with
infinite recursion.

The relevant section in my apache setup looks like

 
SetHandler python-program
PythonPath "sys.path +
['/home/dradmin/wwwroot/php/drmu']"
PythonHandler django.core.handlers.modpython
SetEnv DJANGO_SETTINGS_MODULE sommerspil.settings
PythonDebug On
 

And my urls file look like

from django.conf.urls.defaults import *
from sommerspil.spil.views import *

urlpatterns = patterns('',

(r'^/php/drmu/sommerspil/',include('normal.root.urls')),
   (r'^register/','sommerspil.spil.views.register'),

   (r'^setupdatabase/',
'sommerspil.spil.views.setupDatabase'),

   (r'^/php/drmu/sommerspil/login/', 
'sommerspil.spil.views.loginUser'),

   (r'^setroute/$',  
'sommerspil.spil.views.setRoute'),

   (r'^updatetonextday/$',  
'sommerspil.spil.views.updateToNextDay'),

   (r'^(?P.*)$', 'django.views.static.serve',
{'document_root': '/home/dradmin/wwwroot/'}),
   )

I really hope some one can help, as I seem to be running out leads.

- 
Cheers,
Gorm

Tel: (+45) 31 12 78 44
Co-Founder of 3 Lives Left
Blog: http://www.lai.as/index.php



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---



Re: Internal Redirects Limit

2008-06-30 Thread Malcolm Tredinnick


On Mon, 2008-06-30 at 10:03 +0200, Gorm Lai wrote:
> Hey,
> 
> I now have our django project set up both locally and on our own remote
> server. Everything works fine.
> 
> However, I still have trouble getting it up and running on the client's
> site. It is a big broad casting company, so they won't let me mess with
> their apache setup directly. They will change it, when I request it, but
> the turnaround cycle is rather long, so I want to be sure I request the
> right changes.
> 
> I know get this error in the apache logs, 
> 
> [Fri Jun 27 16:17:53 2008] [error] [client 130.226.238.69] 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.
> 
> Please note that I do not have the power to set a LogLevel debug. Can
> django indirectly cause an apache error like this?

>From memory, what this usually means is that something like Apache
Rewrite rules have gotten mixed up and are doing internal calls to
themselves. Note that this is an *internal* redirect, so it doesn't have
anything to do with HTTP redirects. It also cannot be caused solely by
Django. Rather, it's a problem in the Apache configuration and the
result your are returning (or perhaps the resource that is being
requested) is triggering the problem.

Without you (or your sysadmins) being able to turn on the debug-level
logging for this, it's going to be fairly hard to resolve the problem.
But it's certainly an Apache configuration problem, rather than
something on the Django side (well, at least, the Apache configuration
is contributing to it).

Regards,
Malcolm



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---