On Jun 15, 2:48 am, Chris Seberino <cseber...@gmail.com> wrote: > 1. Restarting Apache+mod_wsgi > 2. Clearing Firefox cache and > 3. Visiting Django app URL > > are all done often when debugging/developing a DJango app under Apache > +mod_wsgi. > > I've noticed with mod_wsgi, I will *SOMETIMES* get an error after this > triad. > > Reloading the Django URL makes it go away so it only appears on the > first visit to Django app. > > I will see sometimes like "400 Bad Request" page in Firefox... > > """ > Bad Request > > Your browser sent a request that this server could not understand. > Request header field is missing ':' separator. > > er.com/set_up > """ > > The DJango URL (I'm using Django auth) > ishttps://seoconquer.com/sign_in?next=/set_up > > Any help greatly appreciated.
Use WSGI script described in: http://blog.dscpl.com.au/2010/03/improved-wsgi-script-for-use-with.html Please let us know if this solves issue or not as still waiting for confirmation that this helps solve that problem. Graham -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
