On Wed, 2006-09-20 at 12:47 -0700, Jaanus wrote:
> one more strange thing... this is what the Django server tells me about
> these requests. Note the 500 error code, not 404...
> 
> [20/Sep/2006 22:33:34] "GET /admin/auth/user/3/ HTTP/1.1" 404 1688
> [20/Sep/2006 22:35:00] "GET /admin/auth/user/add/ HTTP/1.1" 500 90930
> [20/Sep/2006 22:35:01] "GET /admin/auth/user/add/ HTTP/1.1" 500 90930
> [20/Sep/2006 22:35:03] "GET /admin/auth/user/add/ HTTP/1.1" 500 90930
> [20/Sep/2006 22:35:04] "GET /admin/auth/user/add/ HTTP/1.1" 500 90930
> [20/Sep/2006 22:35:05] "GET /admin/auth/user/add/ HTTP/1.1" 500 90930
> [20/Sep/2006 22:35:07] "GET /admin/auth/user/add/ HTTP/1.1" 500 90930

That's not really surprising. If Django is showing you a traceback error
screen, something has certainly gone wrong inside, so "internal server
error" (status code 500) is the right error to be returning here. Don't
worry about that; it's doing the right thing.

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 [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users
-~----------~----~----~----~------~----~------~--~---

Reply via email to