User tampered with session cookie

2007-01-16 Thread Gregor Kling
Hello, Maybe there is someone having an idea about this: There seems to be a couple of unsolved ? problems in combination with 'User tampered with session cookie' I have already used successfully the save/restore-session possibilty, with no problem. I do things like req.session['uid'] = uid

Re: SuspiciousOperation: User tampered with session cookie

2006-08-14 Thread Tom Davis
Although old, I'd like to point out that at least in my case this wasn't a Dapper + PHP5 issue, it was a Deb + PHP5 issue, so the problem seems to lie with the PHP5/Django pairing. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the

Re: SuspiciousOperation: User tampered with session cookie

2006-07-26 Thread tone77
Patrick J. Anderson wrote: > On Tue, 27 Jun 2006 23:30:56 -0500, Patrick .J. Anderson wrote: > > > Malcolm Tredinnick wrote: > >> [quoted text muted] > > > > Hi, Malcolm > > > > Yes, I noticed that too. Perhaps it would be good if I tested this > > behaviour on another distro, but I don't want to

Re: SuspiciousOperation: User tampered with session cookie

2006-06-28 Thread Patrick J. Anderson
On Tue, 27 Jun 2006 23:30:56 -0500, Patrick .J. Anderson wrote: > Malcolm Tredinnick wrote: >> [quoted text muted] > > Hi, Malcolm > > Yes, I noticed that too. Perhaps it would be good if I tested this > behaviour on another distro, but I don't want to resetup my development > machine again.

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Patrick .J. Anderson
Malcolm Tredinnick wrote: > On Tue, 2006-06-27 at 23:09 -0500, Patrick .J. Anderson wrote: >> Jacob Kaplan-Moss wrote: >>> Hi Patrick -- >>> >>> What happens when you clear out your sessions table? >>> >>> FYI, there's nothing about Ubuntu versus mod_python that would/could >>> cause this (I

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Malcolm Tredinnick
On Tue, 2006-06-27 at 23:09 -0500, Patrick .J. Anderson wrote: > Jacob Kaplan-Moss wrote: > > Hi Patrick -- > > > > What happens when you clear out your sessions table? > > > > FYI, there's nothing about Ubuntu versus mod_python that would/could > > cause this (I use both). > > > > Jacob > >

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Patrick .J. Anderson
Jacob Kaplan-Moss wrote: > Hi Patrick -- > > What happens when you clear out your sessions table? > > FYI, there's nothing about Ubuntu versus mod_python that would/could > cause this (I use both). > > Jacob > > > > I cleared the session table and tried to login using my apache/mod_python

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Patrick .J. Anderson
Nikolaus Schlemm wrote: >> I've heard that the problem might be related to md5 hashing (someone >> just recently posted it here in the groups with the same error >> message). I looked at the django code and that where that error message >> is thrown and it seemed to confirm that, but I don't know

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Jacob Kaplan-Moss
Hi Patrick -- What happens when you clear out your sessions table? FYI, there's nothing about Ubuntu versus mod_python that would/could cause this (I use both). Jacob --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Patrick .J. Anderson
Patrick .J. Anderson wrote: > [EMAIL PROTECTED] wrote: >> Clear the cookies in your browser and the problem will go away. >> >> > clearing the cookies doesn't help (I guess you answered that one). > > hmm, i don't know exactly what to do here, as I haven't tampered with > anything. I'll try to

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Patrick .J. Anderson
[EMAIL PROTECTED] wrote: > Clear the cookies in your browser and the problem will go away. > > > > > clearing the cookies doesn't help (I guess you answered that one). hmm, i don't know exactly what to do here, as I haven't tampered with anything. I'll try to recreate the project (extra

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Nikolaus Schlemm
Am Dienstag, 27. Juni 2006 19:25 schrieb [EMAIL PROTECTED]: > Clear the cookies in your browser and the problem will go away. unfortunately that won't solve this problem - possibly another one ;) -- cheers, Nikl --~--~-~--~~~---~--~~ You received this

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread [EMAIL PROTECTED]
Clear the cookies in your browser and the problem will go away. --~--~-~--~~~---~--~~ 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

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Nikolaus Schlemm
> I've heard that the problem might be related to md5 hashing (someone > just recently posted it here in the groups with the same error > message). I looked at the django code and that where that error message > is thrown and it seemed to confirm that, but I don't know why this > happens. simply

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Joseph Kocherhans
On 6/27/06, Patrick J. Anderson <[EMAIL PROTECTED]> wrote: > > I've heard that the problem might be related to md5 hashing (someone > just recently posted it here in the groups with the same error > message). I suspect that it is. I've run into the same problem when I inadvertently changed the

Re: SuspiciousOperation: User tampered with session cookie

2006-06-27 Thread Patrick J. Anderson
Hmm, I haven't changed domains. I simply took my previous setup on Fedora Core 5 with apache+mod_python and put it on Ubuntu Dapper with apache+mod_python. I've heard that the problem might be related to md5 hashing (someone just recently posted it here in the groups with the same error

Re: SuspiciousOperation: User tampered with session cookie

2006-06-26 Thread [EMAIL PROTECTED]
Did your domain change? I have seen this error when I was working on myDomainOne and then started the same app under myDomainTwo. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to