Re: [Django] #1758: When logged in admin I got a 'user tampered with session cookie' exception.

[Django]

#1758: When logged in admin I got a 'user tampered with session cookie' 
exception.
--+-
Reporter:  [EMAIL PROTECTED]  |Owner:  adrian
Type:  defect|   Status:  closed
Priority:  normal|Milestone:
Component:  Admin interface   |  Version:  SVN   
Severity:  normal|   Resolution:  worksforme
Keywords:|  
--+-

Comment (by anonymous):

I can get this message by logging into the admin system '''then'''
modifying the SECRET_KEY setting in settings.py.

Clearing the cookie definitely works in this case (using Firefox 2.0.0.1)

--
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups "Django 
updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

Re: [Django] #1758: When logged in admin I got a 'user tampered with session cookie' exception.

[Django]

#1758: When logged in admin I got a 'user tampered with session cookie' 
exception.
--+-
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian  
 Type:  defect|   Status:  reopened
 Priority:  normal|Milestone:  
Component:  Admin interface   |  Version:  0.91
 Severity:  normal|   Resolution:  
 Keywords:|  
--+-
Comment (by Malcolm Tredinnick <[EMAIL PROTECTED]>):

 In response to the last comment: did this happen repeatedly after the
 Apache upgrade? Even after clearing cookies in your browser? If so, that
 is a problem.
 
 But if it just happened the once and then clearing cookies fixed it, that
 isn't a Django problem. It just means that something major like upgrading
 Apache might require logging in again. That isn't a common occurrence and
 not really worth working around (or even possible to do so).

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

Re: [Django] #1758: When logged in admin I got a 'user tampered with session cookie' exception.

[Django]

#1758: When logged in admin I got a 'user tampered with session cookie' 
exception.
--+-
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian  
 Type:  defect|   Status:  reopened
 Priority:  normal|Milestone:  
Component:  Admin interface   |  Version:  0.91
 Severity:  normal|   Resolution:  
 Keywords:|  
--+-
Changes (by anonymous):

  * resolution:  invalid =>
  * status:  closed => reopened
  * version:  magic-removal => 0.91

Comment:

 I got this when my sysadmin updated apache. Same thing happened on the
 admin page. The only change was apache. I had to fix it by getting rid of
 the checks in django, which is very very bad. I do not know what else to
 do.

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---

Re: [Django] #1758: When logged in admin I got a 'user tampered with session cookie' exception.

[Django]

#1758: When logged in admin I got a 'user tampered with session cookie' 
exception.
--+-
 Reporter:  [EMAIL PROTECTED]  |Owner:  adrian   
 Type:  defect|   Status:  closed   
 Priority:  normal|Milestone:   
Component:  Admin interface   |  Version:  magic-removal
 Severity:  normal|   Resolution:  invalid  
 Keywords:|  
--+-
Changes (by jacob):

  * resolution:  => invalid
  * status:  new => closed

Comment:

 Without more details I can't reproduce this; there's quite a bit of stuff
 (proxies, IP changes, changes to your code...) that could have triggered
 the message.

-- 
Ticket URL: 
Django 
The web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates
-~--~~~~--~~--~--~---