On Sep 25, 7:38 am, Ross Dakin <[EMAIL PROTECTED]> wrote: > Graham, > > I am using Apache andmod_wsgi, and I have experienced that issue > before (500 errors for 404, et al.). > > I fixed it with some tinkering, but don't remember how. Would you > mind explaining this problem a little?
Consider that you have Django mounted at root and static media at a sub URL. If someone tries to access a file in static media directory and it doesn't exist, then Apache generates a 404 error. In Apache default configuration, this would result in an internally generated generic 404 error response page being returned to client. If however you have used in Apache configuration the ErrorDocument directive for 404 at some point, possibly by enabling multi language custom error documents, then when the 404 occurs, rather than returning an internally generated generic 404 error response, Apache, based on the value of the ErrorDocument directive may trigger a sub request to a handler to generate the custom error document. For example, if you had: ErrorDocument 404 /404.html it will trigger a sub request against URL /404.html. Problem is that you have Django mounted at root and see such a request gets routed into Django where they most like is now no handler for that URL. What happens is that Django itself returns a 404 error response. Apache, seeing the 404 for the sub request thinks something nasty must have gone wrong as it would expect it to work, and so returns a generic 500 error response for the original request instead since it now can't generate a valid error response page for the original 404. A quite nasty variation of this is where the ErrorDocument was for a 401 error response in relation to failed Basic authentication. This is because the client would then never see the 401 response and always get a 500 error response instead. This may not explain your situation, but is a problem that can occur and it isn't really obvious what is happening. Graham > Thanks, > Ross > > On Sep 23, 5:08 pm, Graham Dumpleton <[EMAIL PROTECTED]> > wrote: > > > How are you hosting Django? It would help to know if you are using > > builtin development server or whether you are hosting under Apache > > using mod_python ormod_wsgi. If under Apache then use of certain > > Apache configuration settings can cause 500 errors to be returned > > instead of 404 errors. No point explaining though if not using Apache. > > > Graham > > > On Sep 24, 2:14 am, Huuuze <[EMAIL PROTECTED]> wrote: > > > > There are no tracebacks in this instance. I can see the non-descript > > > 500 errors appearing in my terminal window. > > > > On Sep 23, 12:06 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > > > > > On Tue, Sep 23, 2008 at 11:53 AM, Huuuze <[EMAIL PROTECTED]> wrote: > > > > > > I'm preparing to deploy my Django app and I noticed that when I change > > > > > the "DEBUG" setting to False, all references to static files (i.e., > > > > > JavaScript, CSS, etc..) result in HTTP 500 errors. > > > > > > Any idea what's causing that issue (and how to fix it)? > > > > > No. An idea for getting enough information to figure it out, though, is > > > > to > > > > configure things in settings.py (ADMINS, the various EMAIL_HOST, > > > > EMAIL_HOST_USER, etc. settings) so that you get the tracebacks for these > > > > errors mailed to you. > > > > > Karen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
