On Sunday, October 6, 2013 8:24:20 PM UTC+2, Daniel Roseman wrote: > > Notice that this is the default Apache error message, not one for Django. > That strongly suggests that people are being redirected away from your > Django server to another, different one. Perhaps Django is running on a > non-standard port, and after saving they are being redirected to the > default port 80? >
Both the website and the admin interface run at standard port 80. I thought that perhaps the issue might be the other way around, that people are being redirected away from the standard port to a different one or to a differetn virtual host on the same server, but where would such a thing occur? Remember, this is only happening in the contrib admin module. I've looked through my models.py, views.py and admin.py scripts (not sure where to look in this case), but I don't seem to explicitly redirect people anywhere. The only redirection taking place are some raise Http404 calls in my views.py, but those are on the normal website part of the code - I don't see how those would get called from the admin module. I think that for this theory that only leaves the possibility that some other error is triggering an error page from Apache directly and that that error gets redirected to a location we don't have access to? I do have error pages for Http 404 and 500. I tested one of those raise Http404 cases on the website (not the admin module), and I get a "normal" Django Http 404 message (the site is in DEBUG mode atm). I've traced the request/response headers leading up to those 403 Forbidden errors, but nothing jumps out - everything seems to be going on inside of our domain. Now I'm wondering: What would happen if Django did get upgraded from 1.1 to 1.2, 1.3 and finally 1.4, but the admin contrib module didn't get upgraded all the way to 1.4? Would it work at all? Could that explain these errors? AFAIK, the site is being hosted on Debian Linux (I expect it's the latest stable version, whether they call that Lenny or Harry or Boogy I don't know). Are django and admin contrib packages "linked" in their repository, so that if the base package gets upgraded, so does the dependant package? (I'm not too familiar with Linux and their distro's, more of a BSD man myself) Thanks for the suggestions so far. -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at http://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/831e860a-478e-4f3d-b294-8143bd0f5c46%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
