Maybe it's that old bug:
http://blog.umlungu.co.uk/blog/2007/may/20/cookie-problem-django-admin/
Server Upgrade to Lenny is planned in the near future, I hope the problem
solves itself with the dist-upgrade.
greetz,
Florian
--~--~-~--~~~---~--~~
You received this
Now I'm able to login etc, but only with django-server, with apache also the
admin interface informs me that my browser doesn't allow cookies. So there's
a problem with apache and/or mod_python. :-/
I'll test this after the planned upgrade to lenny again.
Thanks for your patience, I created a new project with only a login-page and
a small 'debug' page, seems to work at this stage. Next I will test my own
auth_backend, if this problem appears again (I hope not), I'll be able to
localise it a bit better.
greetings,
florian
2009/8/21 Russell
On Fri, Aug 21, 2009 at 9:10 PM, Florian
Schweikert wrote:
> In summary:
> * On the server (etch) session flushes by request.user.is_authenticated()
> (e.g session.user switched to anonymous without any findable reason) after a
> while equal if session still marked
Tried to use sqlite, to test if it's a db problem, but django aren't able to
open a sqlite databasefile which has the right permissions. Trying postgres
next.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django
I tried it on my notebook with the django server, the cookie wasn't touched,
but request.session.session_key changes every request.
Using the db session backend avoid login, cached_db and cache works
temporally.
In summary:
* On the server (etch) session flushes by
I wrote a tiny page which just shows the session_key.
I can refresh this site and the key is the same, but if I open one of the
other pages the request.user.is_authenticated() method opens a new session.
:(
Nevertheless thanks for your ideas.
greets,
florian
2009/8/21 Russell Keith-Magee
>
> On Fri, Aug 21, 2009 at 12:17 AM, Kelvan
> wrote:
> >
> > I've a big problem with user authentification, my application get an
> > username and a hashkey to verify if the user is logged in. I wrote a
> >
On Fri, Aug 21, 2009 at 12:17 AM, Kelvan wrote:
>
> I've a big problem with user authentification, my application get an
> username and a hashkey to verify if the user is logged in. I wrote a
> function that check this, it worked fine to log in the user with:
>
>
I've a big problem with user authentification, my application get an
username and a hashkey to verify if the user is logged in. I wrote a
function that check this, it worked fine to log in the user with:
user.backend = 'django.contrib.auth.backends.ModelBackend'
login( request, user )
Login
10 matches
Mail list logo