that. The URLs appears as 404 in the access logs.
We are actually using fast_cgi per our system administrator and
wondered if switching to mod_wsgi might help solve the problem, but it
looks like you had the issue with mod_wsgi!
Did recompiling apache solve the problem for you with your Django app
running mod_wsgi?
Thanks for the fast response. Let me know any other information that
my be helpful.
On Jul 1, 9:00 am, "euan.godd...@googlemail.com"
<euan.godd...@gmail.com> wrote:
> When you say "an apache 404 error" do you mean a non-Django styled
> one? If so, I think there's something wrong with your apache
> configuration and not your Django app. What mechanism are you using to
> serve the application? I have seen issues like with this mod_wsgi when
> the reload mechanism isn't triggered correctly and you have to restart
> apache to get it work correctly. I think in that case it was because
> I'd compiled apache slightly incorrectly. I never got to the bottom of
> the problem.
>
> On Jul 1, 2:54 pm, vjimw <im.a.machobea...@gmail.com> wrote:
>
>
>
> > We are having an issue where valid model objects are returning an
> > apache 404 error. Often times, if you hit refresh in the browser a few
> > times, the object is returned with the same URL.
>
> > We are using Django 1.2.1
--
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 django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment